BankrDex Whitepaper

Bankr launches tokens continuously; on Base alone more than a million launches name Bankr as their Doppler integrator. General-purpose DEX screeners list them next to look-alikes from other launchpads that reuse the same pools, show data that can lag the chain, and leave swapping to other tools. BankrDex puts verified Bankr launches, on-chain market data, safety checks, best-price swaps and a social layer in one interface, while the trader's wallet stays the only thing that can move funds.

• Authenticity. Doppler's integrator field is set by whoever creates the launch, and Bankr's ba3 address suffix can be mined by anyone. Tens of thousands of launches imitate Bankr's.
• Fragmented data. Launch metadata, creator fees, market data and trades live in different APIs, each with its own delays and rate limits.
• Execution. New tokens move fast, liquidity is thin, and the best route differs per token and per chain.
• Trust. Traders should not have to hand funds or keys to a third party to get speed or convenience.

1. Non-custodial. BankrDex never holds funds or keys. Every swap, approval, claim and sign-in is signed by the user's wallet.
2. Verify, don't assume. A token is listed only after it is shown to be a Bankr launch.
3. Read the chain. Where it matters (launches, swaps, prices for social performance), data comes from the chain rather than from a third party.
4. Secrets stay on the server. Aggregator keys and database credentials never reach the browser; the browser talks to allowlisted server proxies.
5. Honest numbers. Fees are disclosed and enforced in code; features that are not backed by real data are hidden or marked Soon.

• Catalog. Bankr's public API returns only the most recent launches, so the catalog accumulates: each refresh merges new launches and the most active GeckoTerminal Bankr pools into the previous copy, stored in the database. A bundled snapshot covers cold starts and outages.
• Market data. GeckoTerminal (pools, candles, trades, holders) and Binance Web3 (prices, candles) with a shared per-minute upstream budget and a database cache with stale fallback.
• Recent buys. Decoded from Uniswap V4 PoolManager Swap logs on Base, filtered to catalog pools, with one shared block cursor.
• Launch registry. Every Bankr launch on Base, read from Doppler Airlock Create events and kept current by scanning new blocks. Names and symbols are read from the token contracts the first time a row is shown.
• Creator fees. From Bankr's API; claims are built by Bankr and signed by the fee recipient's wallet.

Every token is checked before it is served. A token is accepted as a Bankr launch by Bankr's own launch record, by the on-chain registry, or by an on-chain check of its launch setup; it is rejected when another Doppler integrator launched it, when it names Bankr without Bankr's launch setup, or when its address lacks the ba3 suffix.

The on-chain launch check requires Bankr's setup, not just Bankr's name: multicurve launches must name Bankr as integrator and pay Bankr's fee wallet as a fee beneficiary; hook launches must use one of Bankr's Doppler hooks with the dynamic fee and tick spacing 200.

Validated against Bankr's own answers on 1,243 tokens (every Bankr launch passes; 0.17% of the rest do), and a hold-out sample agreed with Bankr's bankrDeployed flag on 200 of 200 tokens. Flagged launches are kept so re-imports do not bring them back, and their pools and swaps are not indexed.

For Base, BankrDex maintains its own index of every swap in a Bankr pool (kept 14 days), the pool map from Uniswap V4 pool ids to tokens, and USD prices of the quote assets (WETH, BNKR) read from on-chain pools. From it the server computes prices, 5m / 1h / 24h changes, volume, buys and sells, traders, candles, sniper and bundle signals, the trader leaderboard, and Pulse.

Dust swaps (for example 1 wei for 2 wei) produce meaningless prices through integer rounding; their volume is kept but their price is ignored. The interface shows how far the index is behind the chain and warns when it falls more than 10 minutes behind.

Protections applied on every route:

• Exact approvals for the amount being swapped, never unlimited.
• Quote expiry of 25 seconds; expired quotes cannot be confirmed.
• Slippage warnings above 5% (maximum 50%), and an explicit acknowledgement for price impact of 10% or more.
• Chain switching: the wallet is moved to the token's chain before signing.

BankrDex charges a platform fee of 0.1% (10 basis points) of the input amount, paid inside the same swap transaction to a fixed fee wallet. It is the same on every route and is enforced, not just requested:

• The server proxy rejects aggregator swap requests that do not carry exactly the 0.1% fee and the configured fee wallet.
• Binance Web3 quotes are accepted only when the returned fee amount, fee token and net swap amount match exactly.
• OKX swaps are cancelled before the wallet is asked to sign if the router calldata does not include the fee wallet.
• Direct pool swaps take the fee in the same Universal Router transaction.

The Bankr pool fee (about 1.75% on new Doppler launches, shared by the creator, liquidity, Bankr and a BNKR buyback), router fees, token taxes and gas are separate and are not paid to BankrDex.

• No custody. No server-side signer and no order executor holding user funds. A compromised server cannot move user funds; the worst case is a bad transaction proposal, which the wallet shows before signing.
• Server-side secrets. Aggregator credentials and the database service key exist only on the server. Proxies rebuild every upstream query from an allowlist and schema rather than forwarding user input.
• Rate limiting on every API route per client (optionally shared across instances).
• Database isolation. Row-level security on every table; anonymous and authenticated database roles have no access.
• Wallet sign-in. Sign-In with Ethereum (EIP-4361) with single-use nonces that expire in 10 minutes, smart-wallet signatures (ERC-1271 / ERC-6492) verified on-chain, an httpOnly HMAC-signed session cookie, origin checks and per-wallet write limits.
• Uploads. Profile images are checked by their bytes on the server (PNG, JPEG, WebP only; no SVG) and size-capped.
• Privacy-minded monitoring. Error reporting is opt-in and records only provider, direction and stage of failed swaps, not wallet addresses or request bodies.
• Local lock. An optional passkey / PIN lock for the interface (salted PBKDF2, five-attempt lockout).

Traders can create a wallet-signed profile, post theses (bullish or bearish, with entry, target, stop and timeframe), follow wallets, and compare results on a leaderboard. Integrity rules:

• Theses can only be posted on Bankr tokens BankrDex knows, and the price at posting is taken from the on-chain index, so performance and Target hit / Stopped out badges cannot be backdated.
• Leaderboard results are estimated from indexed on-chain swaps, not self-reported.
• Any wallet can be followed, with or without a profile.

Items marked Soon are built and tested but switched off until the data behind them is live. Timelines are not guaranteed.

• Newly launched tokens are highly volatile and can lose most or all of their value. Liquidity can be thin and price impact large.
• Verification shows that a token is a Bankr launch; it says nothing about the project's quality or intentions. Safety checks reduce but do not remove risk.
• Third-party services (aggregators, data providers, RPCs, Bankr's API) can be delayed, wrong or unavailable; smart contracts can have bugs.
• Browser-run orders only execute while a BankrDex tab is open and the user confirms the swap.
• BankrDex is an interface, not a broker, exchange or adviser. Use of BankrDex is subject to the Terms of Service and the Privacy Policy.