Sealed launch: commitment, reveal, custody
Bots follow known deployer wallets and announced launch times. A sealed launch gives them neither. A single-use house key creates the mint and the pool, so no wallet with a history appears on the launch, and the time is known only to the house until the pool exists.
Commitment and reveal
- Before: the vault posts SHA-256 of mint | launch slot | salt in a Memo. The salt is 32 random bytes.
- After: when the pool is live, the vault posts the mint, the slot and the salt.
- Check: anyone hashes the three values and compares. The verify page does it in the browser.
ftax1 commit id=<12 hex> hash=<64 hex>
ftax1 reveal id=<12 hex> mint=<base58> slot=<n> salt=<64 hex>What stays public
The pool, its fee schedule from the first slot, and every trade are public, as on any pool. A fee schedule cannot be hidden: DLMM Pro writes the fee parameters into the pool account at creation and a bot reads them in that same slot. Sealing protects who launches and when.
Custody
In sealed mode you send the house account the SOL the launch costs. The house holds that SOL for the minutes the launch takes, then the single-use key does the launch and the position NFT goes to the vault like any other. This step is custodial, and only this step.