Multi-chain

One SDK. Every chain your token lives on.

BurnKit started Solana-native. The same burn, split, and receipt flow now runs on EVM chains too - including Robinhood Chain - from a single, unshared line of code.

Architecture

One core. Thin adapters per chain.

Pricing, intent validation, split math, and receipts live in a dependency-free core. Each chain plugs in as a small adapter - so the API you learn once works everywhere.

Your app
@burnkit/sdk core
Pricing
USD → token amount with the same BigInt math on every chain.
Intent
One burn/split/pay intent shape, validated identically.
Receipts
Ed25519-signed receipts, chain-tagged (solana / evm:<id>).
Solana adapter
@burnkit/sdk/web3
SOLSolana
SPL burn instruction
EVM adapter
@burnkit/sdk/evm
RHRobinhood Chain
EVMArbitrum · Base · …
ERC20Burnable / dead address
Same intent, one API

Switch chains by changing config, not code.

The burn/split/verify flow is identical. Moving to Robinhood Chain is a config change - chain: "evm" and a chain id - not a rewrite.

SOLSolana
solana.ts
import { createBurnkitClient } from "@burnkit/sdk"; // Solana: burn 30% of a payment, split the rest to treasury.const client = createBurnkitClient({  network: "mainnet-beta",  rpcUrl: process.env.SOLANA_RPC!,}); const plan = client.planTransaction({  network: "mainnet-beta",  payer: wallet.publicKey,  token: BKIT_MINT,  usdAmount: 5,  burnBps: 3000,          // burn 30%  treasury: TREASURY,     // rest routed here});
RHRobinhood Chain (EVM)
evm.ts
import { createBurnkitClient } from "@burnkit/sdk"; // Robinhood Chain (EVM): same intent, one config change.const client = createBurnkitClient({  chain: "evm",           // <- the only real difference  chainId: 42161,  rpcUrl: process.env.EVM_RPC!,}); const plan = client.planTransaction({  payer: account,  token: BKIT_ERC20,  usdAmount: 5,  burnBps: 3000,          // burn 30%  treasury: TREASURY,     // rest routed here});
Burn mechanics

Real burns on every chain.

BurnKit uses each chain's native burn path so supply actually goes down - and falls back safely when a token has no burn entrypoint.

SOL

Solana

SPL Token / Token-2022
  • SPL Token burn instruction
  • Token-2022 aware
  • Receipt anchored via Memo program
EVM

Robinhood Chain & EVM

ERC-20 / ERC20Burnable
  • burn(uint256) - selector 0x42966c68
  • Fallback: transfer to 0x…dEaD
  • Real decimals read on-chain
Feature parity

What you get on each chain.

CapabilitySOL EVM
Token payments
Programmable burns
Treasury splits
Signed receipts
On-chain receipt anchoringMemo programRoadmap
Live pricing providersJupiter, DexScreenerPluggable oracle / DEX
Wallet supportWallet adapterInjected (EIP-1193)

Swipe the table horizontally to see both chains.

Supported chains

Live today.

SOLLive

Solana

SVM

The original BurnKit runtime. Jupiter + DexScreener pricing, on-chain Memo-anchored receipts.

Tokens
SPL Token / Token-2022
Burn
Native SPL burn instruction
RHLive

Robinhood Chain

EVM L2

Robinhood's EVM chain. Burn ERC-20s directly, or route to the dead address when a token has no burn entrypoint.

Tokens
ERC-20 / ERC20Burnable
Burn
burn(uint256) or transfer-to-dead
EVMLive

Other EVM L2s

EVM

Arbitrum, Base, and any EVM chain - point the client at an RPC and chain id.

Tokens
ERC-20 / ERC20Burnable
Burn
burn(uint256) or transfer-to-dead

One install. Every chain your token lives on.

The multi-chain core is live on npm today. Ship on Solana, Robinhood Chain, or both.