Documentation
Launch & safety · Bankr
Bankr / Doppler creator fees
How Basis accounts for Bankr / Doppler creator trading fees. The swap fee and creator/protocol split are source-backed Bankr protocol facts — they describe the protocol, not Basis economics, and Basis's own beneficiary share is read from the launch output, never guessed. These fees are a flow separate from inference payments. $BASIS is LIVE on Base with a Doppler / Uniswap V4 pool; accrued creator-fee amounts stay pending until a verified production read — every amount here is honest-pending until then.
The model (read this first)
A Bankr launch on Base creates a Doppler / Uniswap V4 pool with a swap fee. The Bankr / Doppler protocol splits that fee into a protocol cut and a creator portion. The Bankr / Doppler protocol keeps its cut; Basis receives only its beneficiary share of the creator portion.
Bankr is the launch rail — not the backend
Bankr launches $BASIS on Base and, after launch, lets Basis observe creator fees through read-only APIs. Bankr does not serve inference, pay workers, settle receipts, route payments, manage credits, or burn/distribute Basis fees, and it is not in the inference hot path. Bankr creator fees are read and claimed independently of inference charges, receipts, and settlement batches — they are not Basis inference revenue, and Bankr does not auto-burn or auto-distribute Basis fees.
The 95% is the creator share — not “95% to Basis”
Do not describe Bankr fees as simply 95% creator / 5% Doppler as if that describes Basis economics. The swap fee and the 95/5 creator/protocol split are source-backed Bankr protocol facts; the 95% is the creator portion, not a guaranteed Basis share. Basis's own take is the beneficiary share, read at launch — it is null until then, never guessed or hardcoded. The "57%" figure seen in Bankr's docs is an example payload, not a default.
Source-backed Bankr facts
Each protocol value below is a source-backed fact from Bankr's published docs, traced to docs/BANKR_SOURCE_NOTES.md (which cites docs.bankr.bot/token-launching). The values are encoded as defaults and remain env-overridable; an override re-tags the source as env. The one genuinely-unknown value — Basis's own beneficiary share — is null until read from the launch output, never a fact and never guessed.
Default launch chain
Base (chainId 8453)
source: docs.bankr.bot/token-launching
Launch protocol
Doppler (Whetstone Research) — a Uniswap-V4 hook
source: docs.bankr.bot/token-launching
Pool type
Uniswap V4 pool (Doppler hook, keyed by poolId)
source: docs.bankr.bot/token-launching
Token supply
100,000,000,000 (100B) — fixed, not mintable
source: docs.bankr.bot/token-launching
Paired / quote asset
WETH (token0) — not raw ETH, not USDC
source: docs.bankr.bot/token-launching
Swap fee
0.70% (70 bps), fixed/static
source: docs.bankr.bot/token-launching
Creator share of the fee
95% (9500 bps) — the Bankr creator portion
source: docs.bankr.bot/token-launching
Protocol (Doppler) share of the fee
5% (500 bps) — kept by Bankr / Doppler
source: docs.bankr.bot/token-launching
Fee accrual
WETH (token0) and the launched token (token1), tracked separately
source: docs.bankr.bot/token-launching
Read API base
https://api.bankr.bot — unauthenticated
source: docs.bankr.bot/token-launching
Basis beneficiary share
read from launch output / fee API — null, never guessed
source: from launch read
WETH-side vs $BASIS-side separation
Creator fees accrue on both sides of the V4 pool — WETH = token0, $BASIS = token1 — and Basis accounts each side separately. They are never summed into a single treasury number; claimable and claimed are tracked separately per side.
WETH-side (token0)
An external liquid reserve — an 18-decimal wei balance. Intended to fund real opex: the inference backend, infrastructure, security, and liquidity ops. WETH may fund market buys of $BASIS only if explicitly operator-approved; no automatic buyback is promised. No burn or staker split applies.
$BASIS-side (token1)
Native inventory — an 18-decimal base-unit balance. As $BASIS-side fee generation, it is subject to the $BASIS-side split (50% burn / 50% staker rewards), realized on every claim: 50% burned on-chain to the dead address (the burned supply read live from Base) and 50% funded to the staking vault via fundRewards, vesting over 7 days into staked value. The continuous, automatic feed is not yet wired. See Treasury.
Read vs claim
Bankr separates reading accrued fees (no key) from claiming them (signed).
Reads — unauthenticated
awaiting beneficiary recipientBasis polls the public read endpoints once a beneficiary recipient is configured; the launched-token requirement is met, but until a beneficiary recipient is set the read functions return pending and nulls without making any network call. In every response, token0 = WETH side and token1 = $BASIS side, reported separately. The address is a path param on every read.
GET {base}/public/doppler/token-fees/{token}?days=30
GET {base}/public/doppler/claimable-fees/{token}?beneficiary={recipient}
GET {base}/public/doppler/creator-fees/{address}?days=30 # address = PATH paramBankr returns amounts as formatted decimal strings (e.g. "0.0042") — not 18-decimal wei — so the parse path scales by 10^decimals to reach integer base units, using BigInt only. Basis parses each side independently, accepts only a clean non-negative parse, never fabricates an amount, and never blends the two sides.
Claim — operator/keeper-signed, never server-side
The no-custody claim path is POST https://api.bankr.bot/public/doppler/build-claim — the signing wallet's key is the authorization; it returns unsigned transactions the beneficiary signs and broadcasts. Both sides are received together in one claim. The separate custodial path (where Bankr signs server-side) is not used by Basis.
Basis never claims fees server-side
Claiming is an explicit operator/keeper action performed with a signed wallet, outside the app and outside any hosted runtime. No Basis route issues this POST, custodies funds, or signs. The fee beneficiary defaults to the deployer wallet and is redirectable; only the current beneficiary may claim.
Where Bankr fees sit in the fee streams
WETH-side and $BASIS-side are accounted separately throughout. The Bankr creator fee is one source that expands to two streams because it accrues on both sides.
- $BASIS
Per-job burn (earmarked)
pending
- $BASIS
Payment-router fee
none beyond slippage
- $BASIS
Settlement fee
none
- WETH
Bankr creator fee — WETH side (token0)
pending (separate)
- $BASIS
Bankr creator fee — $BASIS side (token1)
pending (separate)
Safe assumptions Basis encodes
- —Reads are unauthenticated and read-only. Basis may poll the public read endpoints once configured; it never sends an API key for reads.
- —Claiming is operator/keeper-signed and never server-side. No Basis route claims, custodies, or signs.
- —No fabricated amounts. Until a verified production read of the live pool, every accrued figure is null. The Basis beneficiary share is null until read.
- —Separate accounting. WETH-side (token0) and $BASIS-side (token1) are never blended; claimable and claimed are tracked separately per side.
- —Source-backed protocol facts. The swap / protocol / creator bps describe the Bankr protocol split, not Basis economics; the 95% is the creator share, not “95% to Basis”.
- —No financial promises. No yield, no APY, no guaranteed buyback, no passive income; staker rewards are not guaranteed. WETH→$BASIS market buys require explicit operator approval.
Source of truth
The protocol facts on this page trace to docs/BANKR_SOURCE_NOTES.md, which cites docs.bankr.bot/token-launching. No Bankr fact is stated anywhere in Basis without tracing to that file. The fee model and the read endpoints are also recorded in the repository at docs/bankr-fees.md and docs/treasury-policy.md.
Status
Pending verification
Token: live on Base. Bankr beneficiary recipient: pending. Basis beneficiary share: null — read from launch/API, never guessed. WETH-side and $BASIS-side claimable/claimed: pending.
Until a verified production read of the live pool succeeds, the per-pool accrued amounts stay null; treat every accrued figure here as honest-pending. This page asserts no accrued-fee amount and no specific Basis beneficiary share. Separately, the realized $BASIS-side claims to date have been split 50% burned on-chain + 50% funded to the staking vault (vesting over 7 days), read live from Base; the continuous, automatic feed is not yet wired.