Owner console
Deploy the contracts
Four transactions from your own wallet: registry, launcher, the mined hook, then one wiring call. The site never sees a key. Anyone can open this page, but only the addresses committed to the site's config are used by it.
Before you start
- Connect the wallet that should be recorded as deployer. The same wallet must send steps 2 and 4.
- Every step is a normal transaction you sign. Nothing here holds a key; progress is saved in this browser so a reload does not lose it.
- The contracts are unaudited. There is no owner, no upgrade path and no admin function after step 4.
- Next
Step 1
Deploy BlueprintRegistry
Holds published blueprints and fixes the treasury and protocol share for good.
- Waiting
Step 2
Deploy RuleCraftLauncher
Creates tokens, opens their pools, holds founding liquidity and routes swaps. Points at the Uniswap v4 PoolManager 0x8366…0951.
- Waiting
Step 3
Mine and deploy RuleCraftHook
The hook's address must end in its permission bits (0x20c4). This browser searches for a CREATE2 salt (about 16,000 tries on average), then deploys through the deterministic deployer 0x4e59…956C.
- Waiting
Step 4
Wire the launcher to the hook
One call, allowed exactly once and only from the deployer wallet. After it, nothing in the system has an owner.