BCH BLAZEDeck ↗Code ↗
Build

Security and privacy

What protects the page, what leaves your browser and to whom, and what Hashi keeps: only your own swaps, in your own browser.

Headers

HeaderValue
Content-Security-Policydefault-src 'self'; scripts from Hashi itself plus inline scripts ('unsafe-inline', needed by Next.js's bootstrap) and WebAssembly for the Bitcoin Cash library; images from any https origin; connections to any https or wss origin (the providers are called directly); frames only for WalletConnect's verify page; frame-ancestors 'none', object-src 'none'
X-Frame-OptionsDENY
X-Content-Type-Optionsnosniff
Referrer-Policystrict-origin-when-cross-origin

What leaves your browser

ToWhat
NEAR Intentstokens, amount, slippage, deadline; your addresses once wallets are connected (placeholder addresses before); your deposit transaction
THORChaintokens, amount, slippage, your destination once connected; your deposit transaction
Cauldron Routerthe trade, and for a build your own coins and addresses
Electrum serversyour wallet's addresses, and the transactions you sign
WizardConnect relaysthe connection and sign requests between Hashi and your wallet
Reownwallet sessions; Solana balance reads
Chain RPCs (AppKit's default transports)your EVM address, for balances on 7 chains every 30 s; gas prices
Hashi's relayera gasless USDC authorisation, only when you use it

AppKit's analytics are off. The landing page asks the providers from the server with placeholder addresses: no visitor data.

What Hashi keeps

WhereWhat
your browser's IndexedDByour swaps (hashi-swap:…), with their addresses and the bridge's signed quote
your browser's localStorageyour slippage, your theme, the WizardConnect session, and Reown AppKit's and wagmi's own connection keys
the servera rate-limit counter for the relayer, in memory

No accounts, no database, no analytics of Hashi's own.

On this page