Skip to main content
Burst uses a protocol-issued execution wallet model. When a user creates an account, Burst generates a wallet for execution. That wallet is non-custodial. Burst does not have access to private keys or user funds. This wallet becomes the user’s execution wallet for trading.

​
Core rule

All trading on Burst must originate from the assigned execution wallet. External wallets like Phantom or Backpack are not part of execution. They are used only to:
  • fund the execution wallet,
  • and withdraw funds from it.
Burst separates ownership from execution.User-controlled wallets handle funding.Burst-issued wallets handle trading.

​
Why this exists

Early token markets break down when one actor can split behavior across many wallets. Burst treats wallet enforcement as a market integrity rule. The goal is not perfect identity proof. The goal is one enforceable execution path per account.

​
Control layer

Account-bound execution

Each account has one active execution wallet.That wallet is the only wallet allowed to trade Burst tokens.

Protocol-level checks

Trades are validated before execution.Unauthorized wallets are rejected upstream.

​
Enforcement model

Burst maintains an allowlist of registered execution wallets at the protocol layer. For any buy or trade involving Burst tokens:
  • the transaction must be signed by a Burst-issued execution wallet,
  • that wallet must map to a valid Burst account,
  • and that wallet must be the user’s active wallet.
If any of those checks fail, the trade is rejected before execution. This ensures:
  • one active trading wallet per account,
  • no wallet splitting inside Burst execution,
  • and consistent enforcement across Burst and partner surfaces.

​
Technical breakdown

1

Bind the wallet

Each Burst account is mapped 1:1 to an execution wallet.
2

Validate the signer

Burst checks that the signer is authorized and active before trade execution.
3

Execute only from the assigned wallet

If validation passes, trading proceeds from the execution wallet only.
4

Extend enforcement to partners

Partner routes can enforce the same wallet eligibility rules.

​
Execution wallet binding

The account-to-wallet mapping acts as the source of truth for trading authorization.
burst-account.ts
type BurstAccount = {
  userId: string
  executionWallet: PublicKey
  status: "ACTIVE" | "LOCKED"
  createdAt: number
}
This mapping is maintained off-chain. It determines which wallet can access Burst trading flows.

​
Trade validation

Before any trade executes, Burst validates the signer.
validateBurstExecution.ts
async function validateBurstExecution({ signer }: { signer: PublicKey }) {
  const account = await burstRegistry.getByExecutionWallet(signer)

  if (!account) throw new Error("unauthorized_wallet")
  if (account.status !== "ACTIVE") throw new Error("wallet_inactive")

  return true
}
This validation can apply across:
  • Burst-native execution,
  • routing logic,
  • and partner integrations such as Axiom.

​
Funding model

Users move funds from an external wallet into the execution wallet. Once funds are deposited, all Burst trading happens from the Burst-issued wallet. The external wallet is no longer part of trade execution.

Ownership layer

User-controlled wallets fund and withdraw.

Execution layer

The assigned Burst wallet handles all trading.

​
Partner support

Burst can provide partners with an allowlist of valid execution wallets. Partners can then restrict Burst token trading paths to those wallets only. Burst remains the source of truth for wallet eligibility.

​
Rotation and recovery

Execution wallets are tied to account identity. They are not meant to be freely swapped. If rotation is needed:
  • account-level verification is required,
  • the previous wallet is revoked before the new one goes active,
  • and cooldowns can be applied to prevent rapid switching.

​
Anti-abuse layer

One execution wallet per account does not fully eliminate multi-account behavior. Burst supplements wallet enforcement with additional anti-abuse signals. That can include:
  • device and session fingerprinting,
  • funding source correlation,
  • and behavioral clustering.
This reduces the effectiveness of:
  • multi-account farming,
  • and hidden wallet splitting.

​
Key properties

  • Non-custodial: Burst does not control private keys or user funds.
  • Single execution path: all trades originate from the assigned wallet.
  • Protocol-level enforcement: checks happen before execution, not only in the UI.
  • Account-bound identity: one execution wallet per account.
  • Partner-aligned enforcement: outside surfaces can apply the same wallet rules.

​
Market effect

This keeps account behavior more legible. It makes wallet splitting harder inside Burst-native execution. It also gives partner routes a consistent enforcement standard.

​
Important clarification

Burst does not claim to prove that one human equals one wallet. Burst enforces one execution wallet per account. It then layers in anti-abuse systems to reduce multi-account behavior around that rule.