Custody of the largest allocations is a governance question before it is a technical one. This post is about the two multisig-controlled allocations in EmpoorioChain's genesis and their real state.
The founder multisig — 300 M DMS (30 %)
- Control: a single multisig account.
- Vesting: 12-month cliff, then linear release to the end of year four (
pallet-vesting, runtime index 20). - Staking: the canonical tokenomics states the founder tranche cannot earn staking rewards. This is a stated rule, and it is also listed as a pending decision (D0.8): either the exclusion is enforced in code, or a claim elsewhere — that the team dilutes to 8.57 % over time — is withdrawn. The two cannot both stand: with a fixed emission pool, a tranche that stakes concentrates rather than dilutes.
- Status: multisig account defined in the mainnet chain spec; no mainnet exists, so it holds nothing.
The liquidity multisig — 100 M DMS (10 %)
- Purpose: seed markets for DMS — first a DMS/USDC pool on the native DEX (≥ 500 K DMS is the mainnet gate's recommended seed).
- Control: a multisig to be constituted. The genesis chain spec contains a placeholder without a key. Signers and threshold (3-of-5 or otherwise) have not been chosen.
- Status: reserved on paper, unspendable in practice, and stated as such rather than described as a committee.
Why multisigs
pallet-multisig (index 41) executes a call only when a threshold of pre-declared signers approve it, on chain, with the approvals visible. No single key can move the tranche; no off-chain agreement is needed to prove control. The mainnet gate additionally requires the genesis hash itself to be signed by at least three founding members.
The governance layer above
The governance design places six iron rules beyond ordinary votes — including that sale allocations are irrevocable and that no entity holds more than 10 % of effective voting power. A founder tranche of 30 % of tokens is compatible with that only because voting power is not token-proportional in the design (vote-escrowed DMS, a technical committee with a blocking minority, a guardian with a three-item veto). All of that is designed; veDMS is not implemented.
What this page does not claim
That any custodian holds these tranches, that they exist on a live network, or that the liquidity multisig has members. The previous version of this page announced institutional custody support from a named firm. Nothing of the kind exists for DMS. What exists is a chain spec with one multisig account and one placeholder, a vesting schedule, a stated staking exclusion awaiting code, and a test that the five allocations sum to a billion.
Based on TOKENOMICS_CANONICO.md §2 and §6 (D0.8), TOKENOMICS.json (genesis), MAINNET_GATE.md Gate 5–6 and the governance design.