CurveJail
The yard
Mechanism

The transfer hook and the DBC curve

Meteora DBC accepts a Token-2022 base mint whose transfer hook is set by the config (createConfigWithTransferHook, createPoolWithTransferHook). Every swap goes through swap2_with_transfer_hook, and Token-2022 calls the hook on each transfer of the coin.

What Meteora gives

The hook is called on every transfer while the curve trades. When the curve completes, DBC revokes the hook program id and authority from the mint, then migrates the liquidity to DAMM v2 with a plain Token-2022 mint. Nothing in DBC can stop one wallet from selling; that part is ours.

What the hook adds

The cooldown logic. The hook tells a buy from a sell by the owner of the token accounts: DBC's pool authority (FhVo3mqL8PW5pH5U2CN4XE33DokiyZnUwuGpH2hmHLuM) owns every curve vault, and the hook reads that authority from the mint's transfer-hook extension when the coin is created.

One swap, step by step

  1. The site builds swap2WithTransferHook with the DBC SDK and puts init_record in front of it.
  2. DBC moves SOL into the quote vault and calls Token-2022 to move the coin out of the base vault.
  3. Token-2022 resolves the hook's extra accounts (the coin's config and both wallets' records) and calls execute.
  4. The hook writes your release time. If it returns an error, the whole swap fails.

Jupiter routing of transfer-hook pools is not assumed: the coin page trades through the DBC SDK directly.