Contribute
Open for contribution
Bugs and rough edges that developers building on Freedom reported, plus community proposals. Each one is scoped so someone outside the core team can pick it up.
On this page
Last updated 6 November 2026 · 16 issues
Many of these came from developers building on Freedom's APIs; others from our own docs audit. Security-sensitive findings stay on GitHub only. We review the list regularly: closed issues drop off, and new feedback that fits is added with a short summary.
Picking one up#
- Read the issue and its comments on GitHub; the summary here is only a pointer.
- Comment that you want to take it, with a sentence on your approach. For anything larger than a bug fix, wait for a maintainer to agree on scope.
- Set up the browser with the Setup guide and follow the workflow.
- Stuck? Ask in Telegram or on the forum. We offer mentorship.
Badges: Bug is a defect, Developer experience an improvement to docs, errors or tooling, Feature request a new capability. Community marks issues opened from outside the core team, Good first issue a small, well-understood change, and Proposal · not on the roadmap an idea we have not committed to.
Swarm provider (window.swarm)#
-
Bug
After unlock, Freedom restarts its node to inject the identity, and every window.swarm call fails with node-stopped until it is back. Suggests queueing page calls during a planned restart, or exposing readiness to pages.
-
Developer experience
Without an index the call returns the referenced content; with an index it returns the raw entry. Asks for one documented shape, with an option to resolve the reference.
-
Feature request
Private communities need group and member-to-member keys without pages holding long-term secrets. Asks either for ACT with grantee management, or for key agreement with the page's identity key.
-
Feature request
Feed owners are app-scoped per origin, so the same person is a different member in every community. Asks for a freedom-manifest.json field, with its own consent wording, that lets a site use the wallet identity for feeds (with #949 in mind).
-
Feature request
Today every user needs their own postage batch before their first write. Asks that publishChunk, writeSingleOwnerChunk and writeFeedEntry accept an optional stamp a sponsor signed.
Radicle provider and rad: URLs#
-
Bug Good first issue
radicle_unseed always shows a consent prompt, but the window.radicle shim gives it the 60 s timeout instead of the 300 s budget other prompting methods get. The issue names the one list that needs the method added, plus a test.
Publishing and node setup#
-
Bug
The swap succeeded, then the batch step failed on a transient RPC error and the user saw "failed". Suggests retrying the batch step automatically and saying the funds are safe.
-
Bug
Uploads in freedom://publish jump from 0% to 100% with no progress in between. This worked with Bee and stopped after the switch to Ant.
-
Developer experience Community
Feedback on the publish setup flow. A maintainer status pass lists three points still open: link fund.ethswarm.org, hint how little xDAI is needed, and allow manual batch configuration.
Docs and developer experience#
-
Developer experience
The Radicle mirror of the source was about four months (2714 commits) behind GitHub main on 2026-11-05. Suggests a CI job that pushes on every main push and tag.
-
Developer experience
Notes from driving Freedom over CDP: an undocumented ant.apiGet allowlist, identity helpers that return objects instead of booleans, and a fixed node port that stops two profiles running at once.
Dapp compatibility#
-
Bug Community
A Swarm-hosted wiki loads its search form in Freedom but gets stuck there, while it works through a Bee node's local gateway. A second user reported the same.
-
Developer experience Community
swarmlite reads SQLite pages over HTTP Range requests. Asks the team to confirm single-range bzz:// support as a kept contract, and offers a test page.
Community proposals#
Feature ideas from developers outside the core team. They are open for discussion, design and prototypes, but a proposal is not a commitment: items marked Proposal · not on the roadmap are not on the roadmap. Comment on the issue before you start building.
-
Feature request Community Proposal · not on the roadmap
Proposal for a way for pages to open ACT content shared with the user's node, with consent per publisher. Today bzz:// drops the Swarm-Act headers and window.swarm has no ACT method.
-
Feature request Community Proposal · not on the roadmap
Proposal for a method that lets a page publish a single-owner chunk signed with a key the page holds, stamped by the node. This lets apps keep one Swarm identity across Freedom, Bee-based browsers and other clients.
-
Feature request Community
Request for full web3:// support. A maintainer has since extended it into a plan for the ERC-6860 family; Freedom currently resolves web3:// through ERC-8244 html().
Do not see your issue? Anything in the tracker is fair to ask about; this page highlights the ones closest to the developer APIs.