Keystore Wallet

Keystore Wallet is the built-in, self-custody wallet option in 7.Exchange. It can create a new wallet or import a BIP-39 recovery phrase, then use that wallet to sign supported EVM and UTXO-chain requests without a browser extension.

It is a convenience wallet, not a replacement for a hardware wallet. Because it runs inside the 7.Exchange web page, using it means trusting the web page, the browser, and the device while the wallet is unlocked.

How it works

1. You create a new recovery phrase or deliberately import an existing one.
2. The webapp encrypts the phrase into an encrypted JSON keystore using your chosen password. The encrypted JSON is saved in this browser’s local storage and offered as a downloadable backup file.
3. When you unlock the keystore with its password, the webapp derives the chain-specific addresses needed for supported networks from that phrase. The unlocked wallet can sign messages and transactions for those addresses.
4. When you lock it, the webapp removes the active wallet material from its running state and disconnects the keystore wallet. Locking is an important safeguard, but it cannot provide the hardware isolation of a dedicated wallet device.

The recovery phrase and password are different secrets:

• The recovery phrase is the master backup. Anyone with it can control the wallet.
• The encrypted JSON backup needs its password to be opened. Anyone who obtains both can control the wallet.
• There is no password reset, account recovery, or ability for 7.Exchange to restore a lost wallet.

What you are trusting

Self-custody means 7.Exchange does not hold a server-side copy of your wallet secrets. It does not mean that a browser-based wallet has the same trust boundary as a hardware wallet or browser extension.

While the Keystore Wallet is unlocked, you must trust:

• The 7.Exchange page you load. The page’s code handles the unlocked wallet in order to produce signatures. A compromised site, a malicious script running in the same page, or a deceptive copy of the site could put the wallet at risk.
• Your browser and device. Malware, unsafe browser extensions, a compromised browser profile, or a shared computer can defeat the protections of an in-page wallet.
• Your password and local storage. The browser retains the encrypted JSON locally so it can be unlocked later. Encryption helps protect that file, but a copied file can be subject to password-guessing attempts; use a long, unique password stored in a reputable password manager.

Network services may receive normal wallet activity needed to complete a request, such as a public address, transaction data, or a signed transaction for broadcast. They do not need the recovery phrase or keystore password to broadcast a transaction. Still, public blockchain activity is observable and should not be treated as private.

When to use it

Keystore Wallet can be suitable for a dedicated, lower-value wallet when an extension or hardware wallet is unavailable. It may be useful when one wallet needs to interact with multiple supported chain types.

For significant balances or long-term storage, use a hardware wallet through a compatible wallet application where possible. A hardware wallet keeps signing keys outside the web page and typically requires confirmation on the device for each action.

Safe-use checklist

• Open 7.Exchange by typing or bookmarking the official address; do not follow unsolicited links.
• Only enter a recovery phrase after you intentionally choose the Keystore Wallet import flow. Never give it to support staff, community members, or any website claiming to verify it.
• Download and protect the encrypted JSON backup before funding a newly created wallet.
• Use a unique, strong keystore password; do not reuse an exchange, email, or social-media password.
• Keep the recovery phrase offline and never store it in screenshots, cloud notes, chat messages, or email.
• Lock the keystore when finished, especially on shared devices, and do not use it on a device or browser you do not trust.
• Consider using a dedicated wallet with limited funds for browser-based activity.

If you believe your recovery phrase, password, browser profile, or device may be compromised, move funds to a new wallet created from fresh recovery material as soon as it is safe to do so.