Token

BASIS — the inference token on Base

Basis is a Base-native inference network, and $BASIS is its asset. Users and agents pay for inference in $BASIS; workers earn $BASIS for the jobs they serve; receipts and settlement are denominated in it. Its utility is usage — paying for compute and rewarding the GPUs that serve it — not a claim on revenue and not a return.

Utility

• 01

  Inference payment asset

  Users and agents pay for inference in $BASIS. Usage is metered deterministically per token in integer base units; the rate locks at reservation into a hashed snapshot the receipt preserves, and is versioned per pricing epoch.

• 02

  Route ETH, WETH, or USDC

  Hold ETH, WETH, or USDC on Base? The payment router quotes a swap into $BASIS at payment time, applies slippage limits, and prepares a transaction for your wallet to sign. Basis never signs, custodies, or executes swaps.

• 03

  Worker rewards

  Contributor GPUs earn $BASIS for completed, verified jobs — settled on Base in keeper-driven reward batches. A valid EVM reward address is required to earn; failed jobs earn nothing.

• 04

  Settlement accounting

  Receipts and settlement batches are denominated in $BASIS and reconcile on Base. A batch settles once (idempotent); failed settlements stay recoverable; no job pays twice.

• 05

  Router output token

  $BASIS is the output token of every payment route. ETH, WETH, and USDC are inputs the router converts; $BASIS is what the network meters, charges, and rewards in.

• 06

  Network coordination

  $BASIS coordinates inference demand and worker supply across the network. Its utility is usage — paying for compute and rewarding the GPUs that serve it — not a claim on revenue.

Tokenomics — the fee loop

$BASIS is a unit of account, not a financial product. Inference is paid in $BASIS; if you hold ETH, WETH, or USDC on Base, the payment router quotes a swap into the required $BASIS at payment time. The network has, at most, the fee streams below, and WETH-side and $BASIS-side amounts are accounted separately, never blended.

• Per-job burn

  $BASIS

  The protocol's per-job share of each inference charge (v0.1 design: 10% — the complement of the 90% worker reward), earmarked for burn. A separate draft flow (burned-to-date 0); it is not fed into the Bankr $BASIS-side 50/50.

• Bankr creator fee (WETH)

  WETH

  WETH side of the Bankr/Doppler trading fee in the Uniswap V4 pool. A liquid external reserve for operations, the inference backend, liquidity, and security — separate, with no burn or staker split.

• Bankr creator fee ($BASIS)

  $BASIS

  $BASIS side of the same trading fee. Native inventory; each claim is split 50% burned on-chain (dead address) and 50% funded to the staking vault (streaming over 7 days), both read live from Base. Tracked separately from the WETH side. The continuous, automatic feed is still being wired.

• Payment-router fee

  none

  None beyond market slippage. The router prepares user-signed swaps and takes no protocol rake.

• Settlement fee

  none

  None. Settlement is keeper-driven and charges no separate fee.

Each completed, verified job splits into a worker reward and a per-job burn share — a v0.1 reference design of 90% / 10%. That 10% is earmarked for burn (a separate draft flow; burned-to-date 0) and is its own flow — it is not fed into the Bankr creator-fee $BASIS-side split. The $BASIS side of Bankr fees is accounted separately; WETH-side fees stay separate and fund real operating costs, with no burn or staker split. This governs fee inflows — not the fixed 100B supply, which is a separate decision.

What $BASIS is not

Launch on Base through Bankr

$BASIS launches through Bankr on Base. The launch path — a Bankr/Doppler pool with paired WETH and $BASIS fee sides — is part of the token's design: it is how liquidity forms and how the two fee streams stay separable from day one. The Base launch path is described on the Bankr page.