The take
30%, 38%, or 98% — depending on the period.
Reading “30 / 8” straight off the split table gets it wrong, and the row that rising difficulty drives toward is the one where the project takes 98%.
Nothing is deployed. No address exists on any chain.
There is no factory address, no vault address and no mine address, on mainnet or on any testnet. No transaction has been broadcast. What exists is source, a test suite, the measurements on these pages — and a deploy script that has not been run.
30% is one of three numbers. Printing it alone would mislead.
The vault’s share of the tax splits on fixed constants with no setter: 60% wages, 30% project, 8% referrers, 2% to whoever calls settle. But the project address collects on three different paths, so its take is a range.
A miner with no referrer sends that 8% — and the integer remainder — to the same project address, which makes 38% the ordinary figure during a cold start when nobody has a referrer yet.
A period nobody cut has no wage and no referral to pay, so its whole bucket less the 2% bounty goes to the project: 98%. Because difficulty only rises, empty periods become more common over time, not less. The 98% row is the steady state; the 30% row is the early one.
WAGE 6000 · PROJECT 3000 · REFERRAL 800 · BOUNTY 200 bps, and no function changes them. What varies is which slices have a payee: an unreferred miner’s 8% and the integer remainder fall to the same project address, and a period nobody cut has neither a wage nor a referral to pay. Rising difficulty makes that last state more common over time, not less.
| Case | Project share | Of volume | Why |
|---|---|---|---|
| Blocks cut, everyone referred | 30% | 0.540% | the PROJECT constant alone |
| Blocks cut, nobody referred | 38% | 0.684% | an unreferred miner’s 8% falls to the same address |
| Nobody cut a block | 98% | 1.764% | no wage and no referral to pay; only the 2% bounty leaves |
| Miners’ wages, for comparison | 60% | 1.080% | divided among the blocks cut in that period |
Of volume: the 2% tax we would set at launch × the measured 9,000 bps reaching the vault × the share. Derived, not observed — nothing has traded. Constants from FACTORY.md.
30%, 38%, or 98% — depending on the period.
Reading “30 / 8” straight off the split table gets it wrong. A miner with no referrer sends that 8%, along with the rounding remainder, to the same project address. So a period in which nobody was referred pays the project 38%, and a cold start has essentially no referrers — which makes 38% the opening figure, not an edge case.
A period nobody cut has no wage and no referral to pay at all. Settlement takes its empty branch and sends that period’s whole bucket, less the 2% bounty, to the funding-time project: 98%.
Rising difficulty makes empty periods more common over time rather than less. The steady state is the 98% row, not the 30% row — the project address is the party that benefits from difficulty, and that is the economic fact worth reading twice.
The reading that matters for anyone approving this: the party that benefits from rising difficulty is the project address, not the miners. Every increment of difficulty moves the mine closer to the row where the project takes 98%.
We are not printing 30% on its own anywhere, because on its own it is the least representative of the three.
| Case | Project share | Of volume |
|---|---|---|
| Blocks cut, everyone referred | 30% | 0.540% |
| Blocks cut, nobody referred | 38% | 0.684% |
| Nobody cut a block | 98% | 1.764% |
| Miners’ wages, for comparison | 60% | 1.080% |
Derivation, not extrapolation — no volume is assumed here: the 2% tax we would set at launch × the measured 9,000 bps reaching the vault × the split constants, which have no setter. Nothing has traded, so no share of turnover has ever been collected.
Each bar is 2% tax × the measured 9,000 bps reaching the vault × that case’s split — the same arithmetic as the table above, drawn on one axis so the three can be compared rather than listed. The reference line is the entire wage bill at 1.080%. The 98% bar crosses it: in the state rising difficulty makes more common, the project’s share of turnover exceeds everything the miners are paid. Nothing has traded, so no share of turnover has ever been collected.
This table assumes a volume. Nothing has traded.
The percentages above follow from constants. The dollar figures below do not: they multiply those percentages by a hypothetical daily trading volume. Nothing is deployed, no token exists, and no volume has ever been observed. Read every cell as arithmetic on an assumption.
The assumption in each row is that the whole of the stated volume is taxed at 2%, and that the period in question falls into the named case for the whole day.
| Daily volume | 30% case | 38% case | 98% case |
|---|---|---|---|
| $10,000 | $54 | $68 | $176 |
| $50,000 | $270 | $342 | $882 |
| $200,000 | $1,080 | $1,368 | $3,528 |
| $1,000,000 | $5,400 | $6,840 | $17,640 |
| $5,000,000 | $27,000 | $34,200 | $88,200 |
EXTRAPOLATION. Assumed volume × the derived rate. No token has traded; no address exists. Source: FACTORY.md