Start with an intent

Authenticate with Authorization: Bearer $BITBANK_KEY.

curl -X POST https://bitbank.nz/api/v1/launchpad/intents \
  -H "Authorization: Bearer $BITBANK_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: project-launch-001" \
  --data '{
    "name": "My project", "symbol": "BUILD",
    "description": "A community for builders",
    "image_uri": "ipfs://YOUR_PINNED_IMAGE_CID",
    "website": "https://example.com", "chain_id": 4663,
    "fee_bps": 100,
    "recipients": [{
      "provider": "wallet", "handle": "",
      "wallet": "0x1111111111111111111111111111111111111111",
      "share_bps": 10000
    }]
  }'

201 returns a draft. Reuse the same idempotency key and payload to retrieve it; a changed payload returns 409. No transaction is sent.

Upload artwork with POST /images (multipart file) for an IPFS URI or CDN URL.

Trading FAQ

Try the API

Run a request against this server.

Send a request to see the response.

0.10% to Bitbank. The rest to collaborators.

The default pool fee is 1.00% of trading volume: 0.10% protocol share plus 0.90% for creator-selected recipients. A draft may choose fee_bps of 100, 50, 30 or 10. Bitbank keeps 0.10% at every tier; the collaborator share is the remainder, so 10 basis points leaves nothing for collaborators and needs no recipients.

The deployed contracts currently enforce the 1.00% tier. Drafts at other tiers are stored and validated but cannot be launched until the locker supports them. Recipient share_bps values divide the collaborator portion and must total 10,000. Gas, launch charges, price impact and slippage are separate. The existing Pons token retains its original policy.

Deployed contracts (Robinhood Chain, chain id 4663)

Runtime code hashes are pinned in the server manifest and re-verified on every transaction request. Contract source: bitbanknz/bitbankcontracts ↗.

API v1

For a native launch, deploy a splitter with /splits/transactions, wait for its receipt, then pass its address to /launch/transactions. Trade amounts are integer base units; buys spend native ETH and sells receive native ETH. A sell needs one unlimited router approval per token; swaps and staged claims each require a separate signature and successful receipt.

All paths use /api/v1/launchpad. Errors have {"error":{"code":"…","message":"…"}}. Respect HTTP status codes; retry 503 responses with backoff, never blindly resubmit signed transactions.