Skip to content

The three pillars

Blazpay is easiest to reason about as three products that share one backend, one wallet session and one liquidity engine.

PillarWhat it isPrimary surfaceStatus
BlazAIA conversational agent that turns plain English (or voice) into executable DeFi transactionsai.blazpay.comLive
Blazpay DEXA conventional trading app — swap, bridge, fiat on/off-ramp, perpetuals, limit orders, automation, portfoliodefi.blazpay.comLive
Blaz RewardsThe retention economy — NFT staking, GameFi, marketplace, quests, DAO, creator payoutsrewards.blazpay.comLive

They are not independent apps. All three call the same bz-backend monolith, resolve the same wallet identity, and — for anything that touches liquidity — go through the same swap-sdk aggregation layer.

Pillar 1 — BlazAI

The pitch: you do not pick network → token → slippage → approve → confirm. You type or speak what you want, and BlazAI classifies the intent, extracts the parameters, routes to the best provider, and hands back a one-click confirmation card. Replies stream token-by-token over SSE, so it reads like a messaging app rather than a form.

What it can actually do. 27 distinct intents, grouped roughly as:

  • Trading and wallet — swap, bridge, send (to an address or a name.blazpay username), buy with fiat, buy BLAZ, DCA, limit order, switch chain, check balance, portfolio, transaction history, decode a transaction, price alert.
  • Safety — contract audit, token rug check, wallet reputation card, approval revocation.
  • Automation — set up and manage an Autopilot agent.
  • Discovery and build — NFT lookup, market intelligence, create a dApp, modify a dApp, go on-chain, deploy contracts, show the dApp.
  • CompositionWORKFLOW (chained steps: "bridge then swap then send") and BATCH (same action, many recipients).
  • Conversation and fallback — general Q&A, with a vector-search knowledge base behind the fallback path.

The full list with descriptions and payload shapes is in the intent catalogue.

How it is built. bz-agent is a LangGraph state machine. An entry node picks the intent from a prompt that injects every intent's description; a conditional edge routes to one node per intent; each node is a small LLM call whose output is validated by a Zod schema. Nodes never touch a chain — they only produce { intent, data, text }. Execution happens in bz-backend. See agent graph.

Why the agent has no chain access

Keeping bz-agent execution-free is a deliberate blast-radius decision. A prompt injection can at worst produce a wrong intent object; it cannot produce a transaction. Everything that spends money is re-validated server-side against real chain and token data before a signable payload exists. See security model.

Proof points (all-time snapshot, source: PROOF_POINTS in defi-dex/src/data/chainSeo.mjs, last refreshed 2026-06-10):

MetricValue
AI chat messages processed136,000+
AI chat sessions10,000+
AI intent accuracy (non-fallback rate)99.9%+
Live liquidity providers behind it21

An earlier March 2026 snapshot recorded 36,229 messages, 10,513 sessions, 1,417 unique wallets, and token sends (7,591) as the most-used action.

Pillar 2 — Blazpay DEX

The trading app for users who want controls rather than a conversation. Nine product surfaces:

ProductRouteWhat it does
Swap/defi/swapSame-chain swap, quoted against every live provider
Bridge/defi/bridgeCross-chain transfer with side-by-side route comparison
Buy / Sell/defi/buy-sellFiat on- and off-ramp across 5 providers, 20+ currencies
CSIP/defi/csipRecurring on-chain buys from a user-owned vault
Autopilot/defi/autopilotRule-based autonomous trading inside on-chain limits
Perpetuals/defi/perpetualLeveraged perps via Orderly Network
Limit orders/defi/limitTarget-price orders
Liquidity/defi/liquidityLP positions in Blazpay pools — in progress
Portfolio/defi/overviewBalances, distribution, and per-product history

Settlement for swap and bridge always goes through BlazpayRelayer, an upgradeable meta-transaction contract deployed per chain, which deducts the flat platform fee and forwards to the chosen aggregator's router.

Wallets. EVM via Web3Modal (100+ wallets), Solana via Phantom, TRON via TronLink or WalletConnect. Each family disconnects the others — there is one active wallet at a time.

Pillar 3 — Blaz Rewards

The most under-documented part of the platform, and the largest by module count. It shares bz-backend with the trading core but has its own contracts, its own crons and its own frontend at rewards.blazpay.com.

  • NFT stakingBlazRocket (stake Rocket NFTs for daily BlazPoints, upgrade bonuses, streak multipliers up to 2.8×, lucky drops 3–6×) and BlazBob (11 mintable tiers, deployed on Arbitrum and Hemi).
  • GameFiprediction markets, on-chain poker, and a Mines mini-game.
  • Commerce — an NFT marketplace with hybrid on-chain + BlazPoints settlement, plus a presale module with whitelisting.
  • Growth — the Clippers creator-rewards program, referrals, daily tasks and quests, and Light Link bridge-usage campaigns.
  • CommunityDAO proposals and voting, a blog, threads, chat, support tickets and notifications.
  • Identity — Blazpay usernames, so a send can target alice.blazpay instead of 42 hex characters.

How the pillars interlock

The practical consequence: a change to swap-sdk affects the chat, the trading app, CSIP and Autopilot simultaneously. Version bumps are therefore a coordinated release — see swap-sdk releases.

Internal + developer documentation. Usage figures are point-in-time snapshots — re-verify before publishing them.