What a dip ticket does
A dip ticket is an order that says "buy this asset with USDC if it falls N % from now". When you issue it, your USDC goes into the program's vault and you pick the drop (−3 / −5 / −8 / −12 / −20 %) and how long it lives (24 hours / 3 days / 7 days).
The base price is the on-chain price at the moment of issue. Net price = base × (1 − drop). When the price comes down to the net price or below, the tickets on that net fill.
Every ticket burns $0.50 of the platform coin. Pay in the coin and it burns on the spot; pay in USDC and it goes to the burn treasury, which buys the coin back and burns it every hour.
How a fill works
- Bought in one batch
- The keeper checks prices every 2 seconds and buys every triggered ticket of the same asset in one swap, up to 16 tickets and $25,000 per asset. Anything beyond goes in the next block's batch.
- Split by what you put in
- The asset bought is split by each ticket's round size (rounded down). The tiny remainder stays in the asset vault.
- 1 % oracle guard
- After the swap the program measures what actually arrived. If it is less than 99 % of the amount at the oracle price, the whole fill reverts. Nobody can push a fill through at a bad price by faking the oracle.
- Fill fee
- 0.3 % of the filled amount, in USDC, to the burn treasury; every 60 minutes it buys the coin back and burns it.
- Cancel any time
- Before a fill you can cancel whenever you like and your USDC comes straight back. Pauses and stages never block cancel or claim.
- Delivered right away
- Right after a fill the keeper calls claim, which sends the asset to the owner's wallet. Anyone may call claim, but the asset only ever goes to the owner.
The 24-hour stages
In the first 24 hours after launch the gate opens four times. A stage opens when cumulative burns reach its threshold or its deadline passes, whichever comes first. Thresholds, deadlines and deposit caps are constants compiled into the program; no admin can change them.
| Stage | Burned | Or after launch | Total deposit cap | What opens |
|---|---|---|---|---|
| 1 | at launch | at launch | $50,000 | tickets (6 assets)fill feedcancel and claim |
| 2 | $1,000 | 4 h | $50,000 | dip mapflags |
| 3 | $5,000 | 10 h | $150,000 | ladder tickets |
| 4 | $20,000 | 18 h | $500,000 | auto reload10 assets |
Gates use the higher of the recorded stage and the stage the current conditions give, so a stage is open the moment its condition holds, even if nobody calls advance_stage.
Drops calendar
Drops are features already built and tested before launch. Each is locked behind an on-chain flag that the operations multisig can only switch on (there is no off; pause is for bug response). From day 2 the candidates open one a day.
| When | Drop | What it does | Lock |
|---|---|---|---|
| T+1 h | Fill proof card CARD | A share image of your fill ("picked up SOL at -5%") with an invite link. Issuing one burns $0.10 | on-chain flag |
| T+2 h | Live fill bot LIVE_BOT | Telegram channel posts every fill as it happens, plus an hourly summary | on-chain flag (service-side feature) |
| T+3 h | Dip map preview MAP_PREVIEW | If stage 2 is still locked, the dip map opens for a 15-minute preview | on-chain flag (service-side feature) |
| T+6 h | Plain-language orders AI_ORDER | Type "buy $100 of SOL if it drops 5%" and get a ticket ready to sign (web and bot). Your wallet always signs | on-chain flag (service-side feature) |
| T+8 h | New listings NEW_ASSETS | Two recently listed xStocks join, with a first-24-hour ticket ranking | on-chain flag |
| T+12 h | Hall of fame HALL_OF_FAME | On-chain badges for the 20 wallets that filled closest to the bottom in the first 12 hours. Minting one burns $0.25 | on-chain flag |
| T+16 h | Gift a ticket GIFT | Put a dip ticket in a friend's wallet. You pay the USDC; if it is cancelled, the USDC goes to your friend | on-chain flag |
| T+20 h | Midnight tickets NIGHT | Night tickets that only fill between midnight and 5 a.m. Korea time, while the US market is open | on-chain flag |
| T+24 h | Day 1 report DAY1_REPORT | An auto-generated image: total burned, fills, best pick-up, and tomorrow's drop | on-chain flag (service-side feature) |
| on condition | Siren sale SIREN | Opens the moment BTC falls 3% in an hour or 5% in four. For two hours, siren tickets at -2% / -4% · 2 h window | on-chain flag |
| on condition | Event tickets EVENT_TICKET | Tickets that live only for the 6 hours after CPI, FOMC, jobs data or a big earnings release (schedule in config/events.toml) · 6 h window | on-chain flag |
| from day 2 | Gold and oil GOLD_OIL | Gold and oil tokens join the ticket list | on-chain flag |
| from day 2 | Listing-day tickets IPO_DAY | Tickets for a tokenized IPO's first day | on-chain flag |
| from day 2 | Seasonal tickets SEASONAL | Limited tickets for Halloween (10/31), Pepero Day (11/11) and Black Friday (11/27) | on-chain flag |
| from day 2 | Faster fills ALPENGLOW | Shorter fill cycles after Solana Alpenglow (scheduled 10/21) | on-chain flag (service-side feature) |
| from day 2 | Yield while waiting YIELD | Only after an external audit: yield on waiting USDC | on-chain flag |
| from day 2 | Korean stock tokens KR_STOCKS | Added when an exchange lists Korean stock tokens | on-chain flag |
| from day 2 | Weekly hall of fame WEEKLY_HOF | Badges for the week's closest-to-the-bottom fills | on-chain flag |
Token
- Supply
- 1,000,000,000, fixed. The program has no instruction that mints more.
- Mint and freeze authority
- Mint authority revoked in the launch transaction; no freeze authority.
- Dev share
- The dev buy inside the launch transaction is at most 2 % and is locked at once in Jupiter Lock, vesting linearly over 6 months (not cancellable, recipient fixed). That is the only team share.
- Emissions
- None. No staking rewards, no airdrop allocation, no hidden wallets.
- Jupiter Lock account
- published after launch
Read from the chain now
Not launched, so there is no CA yet. After launch this box shows supply and authorities read live from the chain.
Where the money goes
Project revenue reaches the coin two ways: the fill fee and the ticket burn. Both end with the coin bought and burned. Nothing piles up in a treasury.
Coin tradingThe coin's own trading fee (the DBC creator fee) is also 100 % bought back and burned, but it is not counted as project revenue. The site shows the two apart.
Only what actually burned counts toward the unlock counter. A burn paid in USDC counts with the USDC the buyback actually spent.
Limits
| Item | Value |
|---|---|
| Minimum per round | $10 |
| Per wallet (waiting + filled but undelivered USDC) | $2,000 |
| Total deposit cap (stage 1 · 2 · 3 · 4) | $50,000 · $50,000 · $150,000 · $500,000 |
| Tickets per batch | 16 |
| Per asset, per fill | $25,000 (AAPLx and HOODx: $10,000) |
| Lifetime | 24 h · 72 h · 168 h |
| Drops | −3 % · −5 % · −8 % · −12 % · −20 % |
| Auto reload | up to 6 rounds (from stage 4) |
| Burn sizes | ticket $0.50 · flag $0.25 · card $0.10 · badge $0.25 |
What admins can and cannot do
Two multisigs with the same three signers. The upgrade multisig (2/3, 24-hour timelock) holds only the program upgrade authority. The operations multisig (2/3, no timelock) is the program's admin.
What the operations multisig can do
- switch a drop on (irreversible)
- pause new tickets or a drop's use (bug response; never touches funds)
- add assets, stop new tickets for an asset
- replace the keepers and the price authority
- lower the fill fee (never raise it)
What it cannot do (the program has no such instruction)
- withdraw user deposits
- mint more coin
- change unlock thresholds, deadlines or deposit caps
- raise the fee
- switch a drop off
- block cancel, claim or expired refunds
Remaining risk: if the operations multisig swapped the keeper and price authority to route fills through its own pool, each fill could land up to 1 % (the slippage bound) worse than the oracle. Anything beyond that the program reverts.
Risks
- Issuer controls
xStocks (Backed) and cbBTC (Coinbase) issuers can freeze accounts, pause transfers or move tokens with a permanent delegate. Once you hold the asset, the issuer's policy applies.
- US persons
The xStocks terms forbid delivery to US persons. US persons may not issue xStock tickets; the app asks you to confirm before issuing one.
- Korean law
The legal status of this service in Korea has not been verified.
- Oracle and keeper
The keeper pushes prices to on-chain price accounts. The program checks change size, staleness and confidence, and a fill only lands if the real market gives at least the oracle −1 %. If the keeper stops, fills can be late; cancel and refunds always work.
- Smart contract
The program has not had an external audit yet. It may have bugs. Only put in what you can afford to lose.
- Market
Fills happen at the market price of that moment. The price may keep falling after it touches your net.
Cancel without this site
If this site disappeared, your ticket would still be on chain and you could cancel it yourself at any time. All you need is your wallet and any Solana tool.
- Find the ticket address: open your issue transaction in an explorer; the TicketIssued event in the program logs names the ticket. Or list them with getProgramAccounts(program id, dataSize 240, memcmp offset 8 = your wallet). The address is the PDA ["ticket", owner, ticket_id (u64 LE)].
- Instruction: cancel_ticket (no arguments). The only signer is the ticket owner. It checks no price, no stage and no pause.
- Accounts: in the order below. If your USDC or asset token account does not exist, the instruction creates it (you pay its rent).
- Result: the remaining USDC and unused burn reserve go to your USDC account, any undelivered asset to your asset account, and the ticket account closes, returning its rent.
cancel_ticket accounts (in order)
| 0 | owner | signer · writable |
| 1 | Config PDA ["config"] | writable |
| 2 | AssetPool PDA ["asset", asset mint] | writable |
| 3 | asset mint | read-only |
| 4 | USDC mint | read-only |
| 5 | Ticket PDA | writable |
| 6 | UserState PDA ["user", owner] | writable |
| 7 | AssetPool USDC account (ATA) | writable |
| 8 | AssetPool asset account (ATA) | writable |
| 9 | owner USDC account (ATA) | writable |
| 10 | owner asset account (ATA) | writable |
| 11 | USDC token program | read-only |
| 12 | asset token program | read-only |
| 13 | Associated Token program | read-only |
| 14 | System program | read-only |
Expired tickets can be refunded by anyone with refund_expired (the money only goes to the owner). The keeper calls it every minute.
Addresses
- Network
- Solana
- Program (dip_pool)
- not deployed yet
- Config
- not deployed yet
- DropFlags
- not deployed yet
- USDC mint
- not deployed yet
- Coin (CA)
- Not launched. The official CA is posted only here and on X.
- Burn treasury (USDC)
- not deployed yet
- Burn treasury (coin)
- not deployed yet
FAQ
The price touched my net. Why didn't it buy at once?
The keeper checks every 2 seconds. If the batch swap cannot get at least the oracle −1 % in the real market, the program reverts the fill and the keeper tries again next cycle.
Can the fill price differ from the net price?
Yes. Fills happen at the market price of that moment, allowed only within 1 % of the oracle. You may also buy below your net price.
Do I get the $0.50 burn back when I cancel?
No. The issue burn already burned when you issued. Any burn reserve you prepaid for reloads comes back for the rounds not used.
What happens when a ticket expires?
An unfilled ticket is refunded with refund_expired after expiry; the USDC goes to the owner. The keeper does it every minute and anyone can call it.
Where do I buy the coin?
The official CA is posted only on this site and the project's X account. Do not trust an address from anywhere else.
Why is everything red?
Red is neither up nor down here. On this site red means "something just happened": a fill, a burn, fire. Price direction always carries a sign and ▲/▼.