Name: BLAZE Wallet
Author: BLAZE Wallet

Question 1

What is the difference between BLAZE Wallet and BLAZE Token?

Accepted Answer

BLAZE Wallet is the core crypto wallet product. BLAZE Token ($BLAZE) is the utility token used inside the BLAZE Wallet ecosystem for cashback, staking, governance, fee discounts, premium benefits, and other token-powered features.

Question 2

What is BLAZE Wallet?

Accepted Answer

BLAZE is an AI-powered, non-custodial crypto wallet focused on everyday payments. It supports 18+ blockchain networks and includes features such as QuickPay, scam protection, and natural-language wallet actions.

Question 3

How does QuickPay work?

Accepted Answer

QuickPay lets you scan a QR code, confirm the amount, and send a crypto payment in seconds. Settlement time depends on the selected blockchain and network conditions.

Question 4

Is BLAZE Wallet safe?

Accepted Answer

BLAZE is non-custodial, which means you control your keys. The product includes authentication and transaction safety checks, and security updates are published on the updates page.

Question 5

What blockchain networks are supported?

Accepted Answer

BLAZE supports 18+ networks including Ethereum, BSC, Polygon, Arbitrum, Base, Avalanche, Optimism, Fantom, and Cronos.

Question 6

How does the BLAZE presale flow work?

Accepted Answer

The presale is for BLAZE Token ($BLAZE), the utility token inside BLAZE Wallet. The intent flow starts at $0.008333 per token (58% off the $0.02 launch price). You can register intent between $100 and $10,000, and participants get a 48-hour early-access window when presale opens.

Wallet release updates & sync log

fix(market): no-store on all remaining market API routes

fix(market): bypass CDN edge cache so data is always KV-fresh

feat(market): replace cron prewarm with client-side SWR pattern

fix: lowercase 'Get ready for launch' heading

chore: trigger fresh Vercel deployment

feat: populate tier, tokens and country for wallet-originated commitments

feat: website Supabase as single source of truth for presale commitments

fix(migration): cast actor_id to uuid for presale_user_access backfill

fix(migration): correct metadata column migration based on verified schema

fix: graceful fallback when presale_user_access.metadata column missing

polish: parallel queries, dead-code removal, robust hasWebsiteEntry

feat: robust presale commitment lookup — 5 sources, dual-query, local mirror

Recommended reading