dust
111111111111111HEADCOUNTTWELVE PRESSES · TWELVE EQUAL SHARES · THE POT DOES NOT GROWSHARE PER BROOM1/1215
The headcountThe same light on every one

03  /  Where a period goes

The pot is divided, never multiplied.

Four constants with no setter. What varies is only which of them has a payee.

Status

Nothing is deployed. No factory, vault or ledger address exists on any chain, no transaction has been broadcast, and the repository carries no git remote. ./submission/check asserts all three.

05  /  Where a period goes

Sixty per cent is the wage bill. The rest is named here.

Flap takes 1000 bps of the trading tax, so 90 units of every 100 would reach the vault. That is the pot the four constants below divide — and there is no setter for any of them.

Split equally across everyone who pressed — the wage bill60%
The project address, snapshotted when the period was first funded30%
Each sweeper’s referrer — and the funding-time project when there is none8%
Whoever calls settle, paid on the spot2%

So the project’s take is a range rather than a number. 30% ordinarily; 38% when a participant pressed without a referrer, because that slice and the rounding remainder fall through to the same address; and 98%, less the settlement bounty, for a period nobody pressed in. At a cold start almost nobody has been referred, so a launch would begin at 38% rather than arrive there.

That share is ten times what Flap’s rule 001 recommends, and it is submitted for Flap to accept or reject rather than netted out. The whole split, in basis points and in dollars.

Ledger  /  worked example

Constructed here from the four constants and the same integer division settleEpoch performs. No chain holds these rows: nothing is deployed.

Period 4118  /  every address that pressed

0x7a1c…4e029,140,2200.0370600.004941
0x0bd3…91af12,0000.0370600.004941
0x4f88…c1301,806,9400.0370600.004941
0xd21e…7ba5318,4000.0370600.004941
0x93a0…0e7712,0000.0370600.004941
0x6cf4…22d941,0060.0370600.004941
0x1e57…8a44602,3180.0370600.004941
0xab90…3f6112,0000.0370600.004941
0x2d43…be08157,7420.0370600.004941
0xf018…5cc212,0000.0370600.004941
0x58bc…d7a32,470,9000.0370600.004941
0x0c96…14fe28,5300.0370600.004941
Pot0.7412
Wage bill 6000 bps0.444720
Project 3000 bps + dust0.222360
Settlement bounty 200 bps0.014824
Integer dust4 wei
Referral / address0.004941
Fee burned144,000
The held column moves by three orders of magnitude and the wage column does not move at all. That repetition is the mechanism, not a rendering choice: wageRate = wagePool / epochSweeps[e] is computed once for the whole period and the same number is owed to every address in it. Burned figures are fee × N as charged; totalBurned counts what actually landed at 0x…dEaD, which is smaller by the transfer tax — and that difference funds this same pot.

03  /  Where a period goes

Four constants, no setter.

Split equally across everyone who pressed60%
The project address snapshotted when the period was first funded30%
Each sweeper’s referrer — and the funding-time project when there is none8%
Whoever calls settle, paid on the spot2%
Integer remainderfunding-time project

The ledger  /  four periods, every address inside them

Every row is one address that pressed. The wage column repeats because that is what the contract does — wageRate is computed once for the whole period and the same number is owed to every address in it. Schematic: pots and addresses are a worked example; the wage is 6000 bps of each pot divided by that period’s headcount, and the fee is the same flat number on every line.

Period 411812 pressedpot 0.7412 BNBburned 144,000 DUST
0x7a1c…4e020.03706012,000
0x0bd3…91af0.03706012,000
0x4f88…c1300.03706012,000
0xd21e…7ba50.03706012,000
0x93a0…0e770.03706012,000
0x6cf4…22d90.03706012,000
0x1e57…8a440.03706012,000
0xab90…3f610.03706012,000
0x2d43…be080.03706012,000
0xf018…5cc20.03706012,000
0x58bc…d7a30.03706012,000
0x0c96…14fe0.03706012,000
Period 41179 pressedpot 0.5140 BNBburned 108,000 DUST
0x7a1c…4e020.03426612,000
0x0bd3…91af0.03426612,000
0x4f88…c1300.03426612,000
0xd21e…7ba50.03426612,000
0x93a0…0e770.03426612,000
0x6cf4…22d90.03426612,000
0x1e57…8a440.03426612,000
0xab90…3f610.03426612,000
0x2d43…be080.03426612,000
Period 4116nobody pressedpot 0.3081 BNBburned 0 DUST

No wage rate exists for this period: there is no headcount to divide by. Its bucket cannot move to a later period, so it settles to the project address snapshotted when the period was first funded — 0.301938 BNB, the pot less the 0.006162 BNB settlement bounty.

Period 411514 pressedpot 0.9026 BNBburned 168,000 DUST
0x7a1c…4e020.03868212,000
0x0bd3…91af0.03868212,000
0x4f88…c1300.03868212,000
0xd21e…7ba50.03868212,000
0x93a0…0e770.03868212,000
0x6cf4…22d90.03868212,000
0x1e57…8a440.03868212,000
0xab90…3f610.03868212,000
0x2d43…be080.03868212,000
0xf018…5cc20.03868212,000
0x58bc…d7a30.03868212,000
0x0c96…14fe0.03868212,000
0x84e2…9b070.03868212,000
0x3fd1…60020.03868212,000
Read the middle column down, not across. It changes once per period and never inside one, because the only thing that can move it is how many addresses pressed. The right-hand column never changes at all: one press costs one flat fee, whoever presses. And totalBurned counts what actually landed at 0x…dEaD rather than what was charged — the gap between the two is drawn on the economics page.

Because an unreferred sweeper sends their slice of the 8% to the same funding-time address, 30% is the project’s floor and not its take. A period in which nobody was referred pays 38%; a period nobody pressed in pays 98%, less the settlement bounty. Without that last path, a launch that never found a participant would lock its whole take with no function able to move it.

No payday would wait on us: settlement is a permissionless public call that pays its caller. The revenue this split would produce, in full.