V2 FederalMinter
Contract
0xc15c5F699Daf5e1135732139f05D2c05b3ef4354· deployed block 22362690 (2025-01-04) by Maria #1[chain]. Source recovered:federalminter.sol— deployed selector sets are exact against the source on both the minter head and the child template[src]. The largest generation: 1,560 census children[chain].
V2 is the pivot of the whole design: one week after V1’s lock-forever parity model, redemption appears — collateral becomes recoverable through claim keys, and being a key becomes a publishable property of the token. Everything later (V3’s gates, V4’s self-redeem) is a variation on the problem V2 created.
Minter head [src]
| Function | Behavior |
|---|---|
New(string,string,uint256,address) |
WMContract.transferFrom(msg.sender, this, InitialMint) — creation is paid in MV (WMContract = MV 0xA1BEe1daE9Af77dAC73aA0459eD63b4D93fC6d29, as in every generation) — then new TT(Name, Symbol, InitialMint, this, Parent); TreasuryTokens[child] = tx.origin. Onchain confirmation: the minter holds 82.91M MV it never moved (1,603 payments ≈ the 1,560 children) [chain] |
Transfer(address,address) / TreasuryTokens(address) |
registry re-assignment (tx.origin-checked) / read |
GetTreasuryTokenOwner(address) |
cross-minter registry fallback (see registry model) |
V1Minter() / FED() / FDIC() |
constants; the constructor registers the genesis child FDIC (parent FED 0x1D177CB9EfEEa49A8B97ab1C72785a3A37ABc9Ff) to tx.origin |
The parent of a V2 child is FED or any creator-held TT — the era’s “bond” metaphor: children are backed by the reserve (or by other children).
Child template — 26 functions [src]
ERC20 + Burnable + Parent() + Creator() + Debenture() + the _hu
ladder + ho/TTDATA +:
mint(uint256)— flat 1:1:Parent.transferFrom(msg.sender, this, amount)→_mint(msg.sender, amount). No multiplier.Claim(address Contract, uint256 Amount)— the open sibling claim: surrenderAmountof any registered sibling tokenContract(one whoseDebenture()is still true) and receiveAmountof this token’s locked parent. The sibling is the claim key;thisis the payout source.publish()—_hu[tx.origin] >= 100; setsDebenture = false. A published token can no longer serve as a claim key, and its owner becomes eligible towithdraw().withdraw(address token, uint256)— gated on!Debenture; moves a held child-token’s balance out.
See claim & publish semantics for the system-level consequences (publish ≠ protection).
Observed usage [chain]
- 1,560 children; the top creator minted 417; the deepest hand-built spine reaches depth 66 under the “timer” hub.
- Publish adoption: 511 children were ever published (event-study scan
[chain]; current counts in the generated panel below); the rest remain permanent claim keys by design. - FDIC — the genesis child — became the root of the bureau-ancestry spine that was claim-farmed for ~20 months and was still active in 2026-09 (its entity page carries the live warning banner).
generated census statistics (rule: every child of the factory in the census — no selection)
- children
- 1,561 — every row RPC-verified, entity-paged under /tokens
- era mix
- v2 544 · long-tail 527 · post-crisis 413 · v3-bureau 75 · v4 2
- top creators
- 0x6E8e8007… ×417 · 0x765414e3… ×200 · 0xB46bd3b3… ×116 · 0x18F62166… ×65 · 0xB0F0aec1… ×51 · 0xCe28607B… ×50 · 0x582805B4… ×45 · 0x73a495a7… ×44rule: top 8 EOAs by direct children created through this factory [chain]
- MV revenue
- 82.91M MV over 1,603 payments (blocks 22,362,949–27,041,537)
- publish adoption
- 511 of 1,559 census-era V2 children ever published (32.8%); first publish block 22,363,363
claims touching this entity (11)
- CLAIM-0007 [src]+[chain] minter-mechanicsV2 FederalMinter at 0xc15c5F699Daf5e1135732139f05D2c05b3EF4354 was deployed by Maria #1 at block 22362690 (2025-01-04) [chain]; its parent rule is: FED or creator-owned TT [src]
- CLAIM-0008 [src] minter-mechanicsV2 FederalMinter mint pricing: 1:1 parent parity + MV charge
- CLAIM-0009 [src] minter-mechanicsV2 FederalMinter redemption model: open sibling Claim + publish
- CLAIM-0010 [src] minter-mechanicsV2 FederalMinter carries zero admin/upgrade/selfdestruct selectors and no reachable selfdestruct/delegatecall (apparent hits were ipfs-metadata bytes)
- CLAIM-0011 [src]+[chain] minter-mechanicsV2 FederalMinter embeds exactly one TT child template for its whole era (minter creation-code ipfs metadata hash == every child's runtime metadata hash)
- CLAIM-0012 [chain] censusV2 FederalMinter has 1561 census children (dual-method registry, RPC-verified)
- CLAIM-0049 [chain] censusThe minter-child census holds 3141 rows; every row RPC-verified (eth_getCode + getters + zero-mint Transfer); union of blockscout internal-create index and per-tx receipt pass
- CLAIM-0050 [src] minter-mechanicsChild-token ownership is keyed by tx.origin with a fallback chain V4 -> V3 -> V2 -> V1
- CLAIM-0055 [chain] minter-mechanicsV2 publish adoption: 511 of the 1,559 census-era V2 children were ever published; unpublished tokens remain permanent claim keys by design
- CLAIM-0056 [chain] ledger-mvMV -> minters revenue reconciles exactly: 3209 payments totalling 165,725,342.80 MV, unswept (minters have no MV outflow)
- CLAIM-0058 [chain] ledger-mvV2 accrued 82,914,997.03 MV over 1603 payments (blocks 22362949..27041537); snapshot balance delta vs events = 0
statements inline for convenience — the full registry with proof refs + artifacts lives on /claims