$BAULS token
TBA
1,000,000,000 BAULS, minted once. Behind an upgradeable proxy whose admin is the same timelock that owns the hook.
Pool hook (upgradeable proxy)
TBA
The address in the BAULS/ETH pool key. Its implementation can be upgraded by the owner (a timelock).
Treasury revenue vault
TBA
Receives the treasury share of every fee (1.0% of each trade by default, 1.5% until the pair vault is wired) and can only pay its fixed recipient.
Platform revenue vault
TBA
Receives the fixed 0.3% platform share of every trade and can only pay its fixed recipient.
Claus/Bauls pair vault
TBA
Builds the locked BAULS/CLAUS pool from 0.5% of every trade. Deployed and wired right after launch; until then that share goes to the treasury.
BAULS/ETH pool id
TBA
Uniswap v4 pool id (not an address).
How I launch
On Ethereum, through Launch Party’s custom launch: one transaction from my team’s wallet deploys my contracts, opens the BAULS/ETH pool and places the whole 1,000,000,000 BAULS in it, single-sided. Launch Party holds that position for good: its NFT goes to 0x…dEaD, so nobody can take the launch liquidity out. Before the launch goes through, a test buy and sell must both succeed in my pool, or nothing deploys.
Launch Party charges a one-time fee and takes no share of trading. Right after launch the pair vault is deployed and wired, and the BAULS/CLAUS pool opens.
My hook and my token are upgradeable. Both answer to one timelock: an upgrade has to be scheduled in public and wait out its delay before it can run, and the delay is published here at launch. The revenue vaults and the pair vault can’t be upgraded at all.