How It Works

A strategy is three things: a rule for which cards to buy, a coin on Flap, and a vault on BNB Smart Chain that receives the coin's creator fees and can only spend them on cards from Collector Crypt. Everything below is a program call, an API response or a transaction you can open on BscScan.

The cycle

Flap trading fees flow into the strategy vault

You deployrules + coin
Coin tradesFlap · fair launch
Creator feesgenerated on Flap
Strategy vaultcaps · ledger · custody
Buys a cardCollector Crypt

every minute: collect fees → scan listings → rank by the rules → release → buy → into the vault → raffle or keep

1 · Deploy. You describe the card: Pokémon, grader, grade range, language, years, sets, price, how far under fair value, keywords, exclusions and buy order. The worker canonicalizes the rules and returns their keccak256 hash. You pick what happens to bought cards, who can win, whether winners can sell back, and name the coin.

2 · Launch. One wallet prompt launches the coin on Flap with a fair launch, creates its fee sharing and locks it to the strategy vault.

3 · Fees. Flap routes each coin's creator fees from trading to its strategy vault. For a strategy coin that fee belongs to its vault.

4 · Scan. Every minute the worker reads live Collector Crypt listings on BNB Smart Chain, normalizes numeric grades, languages, sets, USD prices and insured value, then ranks those that fit each strategy's rules.

5 · Buy. When the vault covers the top match, the buying wallet swaps BNB for USDT, buys the card on Collector Crypt and moves it into the vault. The purchase fixes its draw round.

6 · Cards come out. Each card is raffled to one holder, drawn with a scheduled drop, put in a pack pool or kept forever. Every draw is verified on-chain and sent from the vault to the winner.

Fee flow

Trading activity on Flap generates creator fees for the strategy.

Flap launch

The strategy coin enters the market.

trading creates creator fees

Strategy vault

Fees fund matching card purchases.

fees become the card budget

After a card is bought

1Card boughtmoved into vault
2Wait N hourstickets accrue
3Snapshottime-weighted
4Beacondrand round
5Ticketsha256 mod W
6Program checksproof + range
7Winnercard sent

Raffle. The deployer picks a delay from 1 hour to 30 days. At draw time, balances held across the entire window become ticket ranges, committed with a Merkle root and checked against drand's independently produced randomness.