EightSaf Wallet

Non-custodial wallet for Safrochain - A Cosmos SDK Layer 1 blockchain

EightSaf Wallet is a non-custodial browser extension for Safrochain, a Cosmos SDK Layer 1 blockchain. Your keys stay on your device. You control your recovery phrase, your spending password, and every signature. The extension connects to Safrochain mainnet and testnet, talks to dApps through a standard provider API, and gives you send, receive, staking, SafHandle name management, and transaction history in one place. Built for Safrochain EightSaf is purpose-built for the Safrochain network. It is not a generic multi-chain wallet. It focuses on SAF, Safrochain-native assets, and the apps that run on Safrochain. You can switch between mainnet and testnet from the wallet header at any time. No reinstall or rebuild is required. Balances, activity, staking data, and SafHandle state refresh when you change networks. Wallet setup and security Create a new wallet or restore one from a 12- or 24-word BIP-39 recovery phrase. Your recovery phrase is generated and stored only inside the extension. It never leaves your browser. A spending password encrypts your keys with AES-256-GCM. PBKDF2 key derivation (100,000 iterations, SHA-256) protects your encrypted vault. Every send, stake action, SafHandle transaction, and dApp signature requires your spending password when the wallet is locked or when signing is requested. The wallet auto-locks after a configurable idle period (adjustable in Settings). You can change your spending password, reveal your recovery phrase (password required), or remove the wallet entirely (password or typed confirmation plus recovery phrase acknowledgement). Private keys and mnemonics are handled only in the background service worker. They are not exposed to web pages or dApp JavaScript. Send and receive Send native SAF and other tokens held in your wallet, including IBC transfers and token-factory assets. Pick a token from your balance list, enter an amount, review fees, and confirm with your spending password. Send to a Safrochain address (addr_safro...) or type a SafHandle name (for example alice.saf). The wallet resolves names to addresses before you confirm. Receive SAF and supported tokens by sharing your address or your SafHandle. The Receive screen supports two modes: show your SafHandle for a human-readable deposit target, or show your full address with a QR code. Copy either with one tap. Max-send and amount validation respect Safrochain decimal rules so testnet and mainnet sends behave correctly. SafHandle on-chain names SafHandle gives you a readable .saf name tied to your wallet on Safrochain. From the SafHandle screen you can: * Register a new name (with live availability checks and balance verification before you submit) * Transfer ownership of your name to another wallet * Release your name back to the public pool Your active SafHandle appears on the home overview, in the sidebar, and in Receive flows so you always know which name is linked to the current wallet. Staking Stake SAF directly from the wallet: * Delegate to validators * Undelegate (with unbonding period awareness) * Redelegate between validators * Claim rewards from one validator or claim all pending rewards Browse validators with avatars and commission details. Review each staking transaction before signing. Activity and portfolio The Overview shows your total balance, quick actions, and identity bar (SafHandle plus address). Activity lists sends, receives, staking operations, IBC transfers, contract interactions, and SafHandle transactions. History is loaded from the Safrochain GraphQL indexer when available, with live updates over WebSocket. If the indexer is unavailable, the wallet falls back to REST and shows a clear notice when history may be incomplete. Each activity entry opens a detail view with amounts, fees, memo, and a link to the block explorer. dApp connectivity EightSaf injects window.eightsaf into web pages. dApps discover the wallet through the Wallet Standard and can connect with a familiar Cosmos signing flow. Supported provider methods include: * enable(chainId) to connect and authorize an origin * getKey / getOfflineSigner / getOfflineSignerOnlyAmino for account and signing access * signAmino and signDirect for transaction and message signing * signArbitrary and verifyArbitrary for ADR-036 off-chain authentication * signAndBroadcast where applicable through CosmJS-compatible signers When a site requests a signature, a dedicated approval popup shows decoded message details, the requesting origin, and the active network. Off-chain ADR-036 requests are labeled separately from on-chain transactions so you can tell them apart. You approve or reject every request. Connected sites can be reviewed and disconnected in Settings. The dApps section loads the community Safrochain dApp directory so you can explore ecosystem apps from inside the wallet. Address book and contacts Save frequent recipients in your local address book with optional SafHandle labels. When sending, resolved names can be saved as contacts after a successful transfer. Settings and preferences * Switch mainnet / testnet * Auto-lock timer * Light / dark theme * Hide or show balances * Manage connected dApp origins * View extension version * Lock wallet manually Layout modes adapt to popup and expanded dashboard views for comfortable daily use. Reliability and offline behavior The wallet detects when you are offline and shows a banner on key screens. Send and stake are blocked offline. Cached balance data may still display so you can unlock and review your wallet without a live connection. If RPC, indexer, or balance services fail, status banners explain the issue and offer retry. RPC endpoints use fallbacks on mainnet for sends, staking, and gas simulation. Network details Mainnet *Chain ID: safrochain-1 *Native denom: SAF (usaf, 6 decimals) *Address prefix: addr_safro *Explorer: safrochain explorer (mainnet) Testnet *Chain ID: safrochain-testnet-1 *RPC chain ID: safro-testnet-1 *Explorer: explorer.testnet.safrochain.com Technical foundation * Chrome Manifest V3 service worker architecture * React and TypeScript UI * CosmJS for signing and broadcasting * Encrypted storage via Chrome extension APIs * Content script bridge with per-tab handshake (no sensitive data on the DOM) * Strict dApp origin access: sites must be approved per connection Permissions explained EightSaf requests only what it needs: * storage: encrypted wallet data and preferences * alarms: auto-lock timer * tabs / windows / scripting: inject the in-page provider and open approval popups * Host permissions: Safrochain RPC, REST, indexer, explorer, dApp registry, and price metadata endpoints used by the wallet No account is created on our servers. We do not custody funds or hold your keys. Who this wallet is for * Safrochain users who want a dedicated browser wallet * Developers testing dApps on Safrochain testnet * Stakers who delegate SAF from the browser * Anyone registering or using SafHandle names on Safrochain * dApp builders integrating via window.eightsaf or Wallet Standard Getting started 1. Install EightSaf Wallet from the Chrome Web Store. 2. Create a wallet or import your recovery phrase. 3. Choose mainnet or testnet in the network picker. 4. Fund your wallet or use testnet faucets if you are developing. 5. Connect to a Safrochain dApp when prompted, or open the dApps tab to browse. Security reminders * Write down your recovery phrase and store it offline. Anyone with the phrase controls your funds. * EightSaf will never ask for your recovery phrase on a website. Only enter it inside the extension during setup or restore. * Always verify the origin and transaction details in the approval popup before signing. * Disconnect sites you no longer use from Settings > Connected sites. Support and source EightSaf Wallet is developed by the EightSaf team for the Safrochain ecosystem. For security reports, see the project SECURITY policy on GitHub. For network documentation, visit safrochain.com and docs.safrochain.com.