Contribute
Community and mentorship
Ask early, ask in public, and we will help you land your first change. We offer mentorship.
On this page
Where to talk#
| Channel | Use it for |
|---|---|
| Community forum | Longer discussions, ideas, showing what you built |
| Telegram: Freedom Browser | Quick questions, design discussion, new integrations |
| GitHub issues | Bugs, feature proposals, security reports, tracked work |
Never post credentials, seed phrases, private keys or sensitive logs in a public channel.
Mentorship#
We offer mentorship. If you want to build a dapp on Freedom's APIs or contribute to the browser and do not know where to start, tell us in Telegram or on the forum what you are interested in, and we will help you get started.
Good starting points:
- Open for contribution: issues we would like help with, grouped by area.
- Quickstart if you want to build on the APIs first.
- Setup to get the browser running from source.
Reporting feedback#
Developer feedback on the APIs is valuable: a missing method, a confusing error, behaviour that differs from these docs. Open an issue with what you tried, what you expected and what happened, plus a minimal page that reproduces it if you can. Several entries on Open for contribution started this way.
Security#
File security findings publicly on the freedom-browser GitHub issues page, the same as other bugs and feature requests. Do not include credentials, seed phrases, private keys or raw exploit payloads that would put users at immediate risk; describe the issue clearly and link a minimal reproduction when you can.