GitHub
Source code, issues, pull requests, ADIPs. Public history; truth-by-commit.
§ Community · /community
No foundation,
but not no community.
Adamant has no on-chain governance and no admin keys. Protocol change happens by hard fork — and hard forks happen by social coordination. This page is the social-coordination surface.
§ 01 / Channels
Where the conversation happens.
X
Announcements and reach. Not a place for governance discussion.
Matrix
Federated chat for working-group discussion. Bridge-free; no Discord, no proprietary platform.
#adamant:matrix.org — pre-launch
RSS · commits
The journal lives in the commit log. Subscribe via atom.
§ 02 / ADIP
Adamant Improvement Proposal.
There's no on-chain vote. Adoption is the signal: operators run the new client at a coordinated height, and the change ships — or doesn't.
Draft
A proposal is published as a markdown document in the public repository. Anyone may submit.
Review
Open review window (≥30 days) on the repository. Discussion is logged in commit history; no voting.
Reference
A reference implementation is produced. Without code, the proposal cannot proceed.
Public testnet
The proposal is exercised on a public testnet for ≥90 days. Results are appended to the proposal.
Hard fork
Operators run the proposal's client at a coordinated block height. There is no on-chain vote. Adoption is the signal.
ADIPs live at adamant-protocol/adamant-improvements. Anyone may open a draft; no permission required.
§ 03 / Contributors
Who builds this.
Adamant was designed and bootstrapped by Ryan Geldart (WP §8.1.5, honest framing). Beyond that there is no team page, because there is no team in the foundation-with-equity sense. Contributors are visible in the commit log of each repository.
If you've written a non-trivial PR that landed, add yourself to the contributors file of that repo. If you've written non-code (audits, ADIPs, translations, documentation), add yourself there too.