Skip to main content
once BundleExecuted fires, your launch is in LAUNCHED state. one follow-up function (finalizeLaunch) wires the post-graduation V2 pair into the treasury contract. after that, the on-chain launch mechanics run without creator intervention, while agent activity remains delegated to the configured runtime and keys.

​
what the contracts do post-launch

  • LaunchVault holds presaler tokens. depositors call claim() to pull their pro-rata share, subject to vesting if enabled. you do not need to do anything.
  • BundleRouter is one-shot and done. executed = true forever. nobody can call executeBundle again on it.
  • TreasuryLP5 holds 10% of the token (100M). it deploys progressively as four single-sided PCS V3 LP positions as the token’s TWAP market cap rises through the tier targets configured for your launch tier. as the token trades through each tier’s range, the position sells token for BNB, and the BNB accumulates inside the position. an operator service (tier-cron) permissionlessly calls oraclePoke and checkAndAdvance to advance tiers.
  • AgentSafe is your token’s treasury multisig (Gnosis Safe v1.4.1). it is the only address that can call treasuryLp5.claim() to pull accumulated BNB out of the V3 positions. signers are whoever you configured at launch.
  • TaxSplitter splits the FLAP buy/sell tax stream 3-way between platform, patron, and your AgentSafe per the BPS you configured at launch.
  • FlapTaxTokenV3 runs on its own based on the tax config you set at launch time. the buy/sell tax bps decay according to taxDuration.

​
things you can do as the creator

  • engage with holders. the social side. the platform does not handle this.
  • answer questions. especially during the 24-hour vesting period when presalers are watching closely.
  • trade on PCS like anyone else. you have no special permissions on the token. if you want exposure, buy from the open market.
  • track metrics. the platform dashboard shows holder count, transfer volume, vault claim progress, treasury LP balance, all in real time via the indexer.

​
things you cannot do

  • mint more tokens (supply is fixed at FLAP’s mint)
  • change the tax structure (set at launch, decays per taxDuration)
  • pause transfers
  • recover BNB from any contract
  • recover tokens from the burn address, FLAP V2 LP, or TreasuryLP5 positions (the V3 LP NFTs are owned by TreasuryLP5 and only the contract can collect from them)
  • replay the bundle
  • modify metadata
this is the delegated autonomy model. the contracts enforce the launch rules, but the agent runtime and its keys are still operated by the configured agent stack and anyone you authorize to control it.

​
claiming BNB from TreasuryLP5

as the token’s price rises through tier targets, TreasuryLP5 deploys single-sided V3 LP positions that automatically sell token for BNB. that BNB accumulates inside the V3 positions until someone calls treasuryLp5.claim(), which:
  1. collects BNB from every deployed tier via npm.collect
  2. unwraps WBNB to native BNB
  3. splits the BNB 4-way:
    • 10% buyback. V2 swap of BNB for the token. tokens sent to the burn address.
    • 5% platform. sent to the platform receiver.
    • 20% patron. sent to the launch’s patron receiver.
    • 65% agent. sent to your AgentSafe. this is your share, plus any rounding dust.
  4. emits BnbClaimed and BuybackExecuted
only your AgentSafe can call claim(). anyone can call oraclePoke() and checkAndAdvance(), which is how the V3 ladder progresses without requiring you to do anything.

​
launch state queries

you can query the vault directly:
or use the REST API. see reference/api for endpoints.

​
supporting your presalers

the most common questions in the 24 hours after launch:
  • “when can i claim?” right now, if you are LAUNCHED. vesting is automatic in the math.
  • “where are my tokens?” they need to call claim() on the vault. the UI has a button.
  • “can i sell?” yes, on PCS. the sell tax applies per your config.
  • “why did i get fewer tokens than i expected?” the presaler share is a flat 200M tokens split pro-rata across all depositors. if more BNB was deposited than you expected (cap fill near max), your pro-rata fraction is smaller. the absolute pool is the same.
a calm 24 hours of answering these well is worth more than the launch itself.