How Value Flows to Contributors
The compensation protocol: why the founder salary is on-chain, how the treasury gate protects the ecosystem, and what it means that every contributor gets the same structure.
The Founder Is Not Exempt
The first salary in the protocol is mine.
Not because I am owed it. Because the rule has to start somewhere — and if it does not start with the founder, it means nothing.
My compensation is written in code, visible on-chain from the first day the treasury has sufficient reserves to activate it. 9,000 USD per month. No override. No special class. The contract does not ask who submitted the claim — it reads the address, checks the threshold, and executes. That is the whole mechanism.
This matters because every extraction scheme in crypto history began with one exception. A "founder carve-out." A "strategic reserve" that only certain wallets could access. A vesting schedule that applied to contributors but not to the team that wrote it. The first exception is the blueprint for all the ones that follow.
We wrote the rule into the machine. The machine needs no priest. The rule applies to everyone — including the person who wrote it.
The Treasury Threshold Gate
Salary does not activate until the treasury can sustain it.
This is not charity toward the protocol. It is design. A treasury that pays contributors before it has reserves is a treasury that runs dry. A dry treasury cannot pay anyone — and more importantly, it cannot fund what it was built to fund.
The gate works simply: the compensation contract checks the treasury balance against a defined minimum reserve before releasing any payment. If the threshold is not met, the claim reverts — no payment leaves the treasury. Contributors retry when the treasury recovers. There is no queue, no backlog, no deferred obligation. Either the treasury is healthy enough to pay right now, or it is not. When the balance crosses the threshold again, contributors claim on the normal monthly cadence.
The threshold is governance-adjustable. The community can vote to raise it as the ecosystem scales. It cannot be lowered below a floor without a supermajority — a protection against short-term extraction pressure overriding long-term protocol health.
What this does: it decouples the incentive to draw salary from the incentive to loot the protocol. A contributor who drains the treasury to hit threshold faster is destroying the asset that pays them. The mechanism makes self-interest and protocol health the same interest.
The 9,000 Cap and Why It Is Permanent
The cap is not a phase. It is the architecture.
9,000 USD per month is the maximum any single contributor — founder, early team member, council seat holder, or operator — can draw from the protocol treasury as a compensation payment. The cap does not scale with token price. It does not unlock with tenure. It does not have a governance exception for "critical roles."
The reasoning is plain: a protocol that compensates its builders at 9,000/month is a protocol that stays solvent while it serves its mission. A protocol that compensates its founders at 90,000/month is a protocol where the founders are the mission. These are different things. We chose the first one.
The cap also does the work of signal. Anyone who needs more than 9,000/month from this treasury should not be building this. The people who build this will build it because the work is real and the physics of what we are creating will compound — in equity, in governance weight, in what the ecosystem becomes. The salary is a livelihood, not a payday.
No Backroom Deals. The Contract Is the Deal.
Every contributor who joins after the protocol launches receives the same compensation structure. Not a similar structure. Not a structure "modeled on" this one. The same one.
There is no separate agreement. There is no off-chain understanding that supersedes what is on-chain. If a contribution type, rate, or cap does not appear in the deployed contracts, it does not exist. The chain is the record.
This rule eliminates a class of failure that has destroyed every organization that tried to work around it: the private deal that becomes a grievance, the informal promise that becomes litigation, the equity allocation that could not survive a clear-eyed audit. We do not have those. We cannot have them. The system does not have a mechanism for them.
Contributors know what they will earn before they contribute. The formula is public. The threshold is public. The cap is public. The governance process for changing any of it is public. There is no information asymmetry between the person who wrote the contract and the person who shows up to build a wall or ship a feature.
Capital Locks and Verified Contributor Flow
All investment capital — whether from token sale, grants, or direct investors — enters the treasury under lockup by default.
It does not flow to individuals at will. It does not flow at the discretion of any single address. It flows on a schedule, gated by the treasury threshold, and it flows exclusively to verified contributors — addresses that have earned compensation credit through attested contribution records.
The attestation requirement is load-bearing. An unverified address cannot receive treasury payments, no matter who controls it. Verification requires contribution evidence — work records, git commits, site attestations, community participation logs — reviewed through the multi-party attestation protocol. Fabrication requires corrupting multiple independent attesters simultaneously — a coordination cost that rises with network size.
This is what "capital locked by default" means in practice: investors who fund this protocol are not funding withdrawals. They are funding the system that pays people who build. The lock converts capital from extraction potential into contribution fuel.
What This Means for Trust
Every system that asks for trust eventually betrays it. The ask itself is the vulnerability — it means the system has a place where a human decision can override the mechanism.
We do not ask for trust. We offer proof.
The compensation mechanism is auditable by anyone. The treasury balance is visible. The threshold is readable. The cap is encoded. The contributor records are on-chain. A skeptic does not need to believe the founding team has good intentions — they can verify that the founding team cannot extract beyond what the code permits. Belief is not the instrument. Code is.
This is what decentralization actually means in governance: not that no one is in charge, but that no one can unilaterally change the rules for themselves. The founding team has the same access to the treasury as every contributor who comes after — shaped by the same mechanism, subject to the same threshold, capped at the same ceiling.
The river does not carve an exception for the source.
The compensation contracts — ContributorRegistry, TreasuryGate, and ContributorSalary — are published and verifiable on-chain. Threshold parameters, cap mechanics, and treasury address changes are protected by timelocks (48 hours for floor/period changes, 7 days for treasury migration). The 9,000 USDC cap is immutable in the contract code — no governance vote can change it.