How drops work

1. 01 · Drop

   A sponsor mints a token for a Twitter handle via the drop form or by tagging @TooLateBro on X. Token + Uniswap V4 pool go live on Base instantly, LP locked permanently.

2. 02 · Trade

   Every swap incurs an LP fee. The Launcher pre-routes a creator share straight into the recipient's vault — no manual collection, no per-trade transaction overhead.

3. 03 · Pull

   The recipient proves they own the handle with a Reclaim zkTLS proof and pulls the vault. Decay schedule below.

Decay starts the moment the vault first lands on chain. If the recipient never shows up, anyone can trigger a burn after day 21 and earn a 0.5% bounty.

Every TooLateBro token address ends in 42069. Before each drop the frontend brute-forces a CREATE2 salt across a pool of Web Workers (median ~5s on a modern laptop, capped at 8 cores), then hands that salt to Clanker so the deployed token lands on a predicted vanity address. Mining is fully local — no third party service can reorder or hold up your launch.

If a recipient never pulls, anyone can call triggerBuyback() after day 21 to clean up the vault. The caller earns 0.5% of the WETH inside; the rest goes to the burn sink and the leftover token is sent to 0x…dEaD.

Addresses populate after on-chain deploy. Until then read-only mode.

TooLateBroLauncher

via github

IdentityRegistry

—

VaultFactory

—

ClaimVault (implementation)

—

Clanker v4

0xE85A59c628F7d27878ACeB4bf3b35733630083a9

Reclaim Verifier

0x8CDc031d5B7F148ab0435028B16c682c469CEfC3

We bind Twitter numeric user ids (never the handle — handles change) to wallets via on-chain proofs generated by the Reclaim Protocol. The proof's context field must equal {"user_id":"<decimal id>"} for the registry to accept it. Identity bindings are sticky — once set, the wallet for a given Twitter id cannot be changed (v1).

• @TooLate_Bro on X
• Source on GitHub
• Underlying Clanker v4
• Reclaim Protocol docs