Daimon DAO
No owner. No mint. Floor 21B. — DAO on BNB Chain
📄 Protocol paper v0.3 (EN) · versione italiana · changelog · previous versions
🛡️ Zenith Audit Report (Aug 2026) — full report published: 37 findings, all resolved (29 fixed in code, 8 accepted with rationale). Audited reference frozen at tag audit-final.
Daimon is a BEP-20 token with reflection, vote-escrow staking, on-chain
governance and a public timelock, on BNB Chain / PancakeSwap. No owner, no
mint function, an immutable supply floor at 21 billion: everything is
verifiable on-chain, and the deployer renounces every role after deploy.
The Zenith security audit is complete — every finding fixed or accepted
with a written rationale, and the exact audited code range is frozen
forever at tag audit-final.
Key properties
- No owner, no mint. Control belongs to the DAO via the Timelock; the
deployer holds no role after deploy (verified on-chain and by the
invariants).
- Immutable 21B floor. The supply can only decrease (deflationary burn)
and never below
MIN_SUPPLY, enforced at the code level.
- Public 7-day timelock on every governance action — a reaction window
for the community, valid for the DAO itself too.
- Vote-escrow. Voting power derives only from tokens locked over time,
snapshotted at the proposal's creation (no flash-loan governance).
Contracts (src/)
| Contract | Role |
|---|
DaimonV2 | BEP-20 token: reflection, autonomous fees, buyback&burn, 21B floor (UUPS) |
DaimonStaking | Vote-escrow staking, checkpoint-based voting power, BNB rewards |
DaimonGovernor | Governance: propose → vote → queue → execute, snapshot-based quorum |
DaimonTimelock | Timelock hardcoded to 7 days on every execution |
DaimonMigration | 1:1 migration from the old token, post-deadline sweep to the treasury |
Status
Live on BNB Smart Chain mainnet since 2026-09-29. The audited code was
deployed unchanged (git diff audit-final -- src/ empty) and verified on
BscScan and Sourcify (exact match); the deployer renounced every role in the
same run, and the pool's LP tokens belong to the Timelock. Test suite (unit +
fuzz + invariant + adversarial) 203 tests green — the 180 of
audit-final plus 23 for the launch tooling — and Slither static analysis
performed. External audit by Zenith complete — the full report
is published and the audited code range is frozen at tag
audit-final.
The migration window is open until 2026-12-28 01:08:44 UTC
(migrationDeadline 1798420124): DMX holders swap 1:1 for DMN on
app.daimon.money. Every launch step — each
transaction, each read-back, the deviations and the incident during the
pause — is recorded in the
mainnet launch record.
Before mainnet the launch was rehearsed on BSC testnet — a full governance
cycle in real time, seven real days of timelock included
(CHAPEL_L2_RESULTS.md, 2026-08-28 to 2026-09-10),
then the launch configuration (docs/CHAPEL_2B_RESULTS.md)
— and on a local fork of BSC mainnet against the real DMX
(docs/MAINNET_FORK_RESULTS.md).
Mainnet addresses
BNB Smart Chain, chainId 56. Always verify an address on chain before
interacting; the deploy transactions and the implementation behind the DMN
proxy are in the launch record.
Status of decisions
The protocol paper is v0.3, the mainnet release of 2026-10-12 (v0.2 was
the post-audit release of 2026-09-11; the document was called the whitepaper
up to v0.1), and it incorporates the decisions below. The decision documents
remain the detailed record: where
the paper and a decision document differ, the decision document takes
precedence, and the deployed code takes precedence over all of them:
Documentation
- docs/MAINNET_LAUNCH_RECORD.md — the
mainnet launch journal: every step, every transaction, the deviations and
the incident, the migration window
- docs/SUPPLY.md — DMN total and circulating supply: the
formula, the excluded addresses, one command that recomputes both from
the chain
- docs/STAKING_STATS.md — DMN staked by lock
period: locks, amounts and voting power shares, checked against the
contract's counters, one script that recomputes them at any block
- docs/protocol-paper/ — the protocol paper (EN
primary, IT translation), with versioning policy, changelog and the PDF
build script
- THREAT_MODEL.md — threat model, actors, defenses, known
limits and design choices
- SECURITY.md — how to report vulnerabilities (responsible
disclosure)
- TESTNET_RESULTS.md — results of the end-to-end tests
on the live testnet
- AUDIT_BRIEF.md — orientation for the auditor (frozen scope
tag)
- DEPLOY.md — the testnet deploy procedure (BSC testnet, chain id 97);
the mainnet deployment of 2026-09-29 is recorded in
docs/MAINNET_LAUNCH_RECORD.md
- daimon-dapp/ — the official dApp (Next.js + wagmi), with its
own
Official channels
Additional official channels will be listed here as they go live. Any channel
not listed here is not official. The IPFS mirror is identified by its content
hash (the CID above): a different CID is a different site, whoever serves it.
No admin will ever DM you first. Nobody will ever ask for your seed phrase or
private key. Always verify contract addresses on-chain.
Security
Found a vulnerability? Do not open a public issue. Use the private channel
(GitHub → Security → Report a vulnerability) — details in
SECURITY.md.
Build & test
forge build
forge test
The project requires via_ir = true (the reflection math hits "stack too
deep" without it) and EVM shanghai for BSC. See foundry.toml.
Disclaimer
Daimon is experimental open-source software provided "as is", without
warranties. Nothing here is an offer, solicitation, or financial advice;
statements about future development are intent, not promises. No entity
operates the protocol and no one is obliged to maintain it; you interact
directly with immutable smart contracts on a public blockchain, at your
own risk. Digital assets can lose all value. Use of the software may be
restricted in your jurisdiction — you are solely responsible for
compliance with your local laws. Where this text and the deployed code
disagree, the code is the only authority.
