Questions about the product

Developers, security researchers, and advanced users who want a serious signer. Detailed confirms, easy RPC switching, and hardware. If you already live in MetaMask or Rabby and wish the wallet assumed you can inspect a transaction, you are the audience.

It is self-custody for people who want power-user defaults, not onboarding for someone buying crypto for the first time. Seed, private key, Ledger, and Trezor are all supported. The UI does not hide details behind a cartoon.

Yes. The wallet is open source under the MIT license. Read the code, open issues, and send pull requests on GitHub. Install the signed build from the Chrome Web Store; the repository is how you inspect what that build is made from.

Same job (connect to dapps, send, sign) with a denser toolkit: per-chain RPC picker and network doctor, Inspect, approval revoke, LiFi swaps, multisend, ENS, side panel, optional Burner Mode on a disposable key. MetaMask is the compatibility baseline. Rabby is the closest power-user cousin. 1337 is privacy and power: no analytics, no 1337 server, no central entity that could watch you. User data stays on the user's machine.

For keys and hardware, security is the same class. That question lives on Security. For what the vendor can collect about you, see the privacy comparison.

Install from the Chrome Web Store. Chrome, Brave, Opera, and Arc all use that same listing. After install it opens in the side panel by default. Switch to popup in Settings if you prefer MetaMask-style chrome. You can also clone and build from source.

Yes. Enable MetaMask drop-in for window.ethereum sites that only look for MetaMask, or connect as 1337 via EIP-6963. Most Wagmi / RainbowKit / Ethers stacks just work. Builders: integration guide · RPC methods.

Yes. A seed derives HD accounts on the same path style as MetaMask (m/44'/60'/0'/0/n). You can also import extra private keys and attach Ledger or Trezor accounts. Pick the active account in the header.

Twenty-plus popular EVM chains ship with curated public RPCs. Switch the endpoint per chain in one click, add a custom URL if you want, and run the network doctor when something looks off.

Side panel is the default so the dapp and the wallet can sit next to each other. Settings can switch you to a popup. Same extension, same vault.

Normal (default) confirms every dapp sign/send, like MetaMask and Rabby. Burner Mode auto-signs ordinary requests on a local key you treat as disposable. Risky actions still pause unless you ungate them. Hardware always confirms on the device. More on Security.

Signings (local message / typed-data history), Approvals (ERC-20, NFT operators, Permit2), Swap (LI.FI), ENS & DNS, Multisend, and Gas station. Inspect (address, token, ENS, tx hash) is off until you enable it in Settings. Inspect is a search box, not a fourth tab. Nav stays Assets / History / Tools.

Cross-chain routes come from LI.FI when you open Swap. 1337 does not run a swap backend. You still confirm (or, on hardware, confirm on the device). Slippage and route details are in the flow.

Paste a list of addresses and batch native or ERC-20 through Disperse.app, the familiar no-fee batch contract, including on hardware accounts. If a chain has no Disperse yet but has CreateX, the first user can deploy that same Disperse for everyone. It is a send tool.

Your own Etherscan-compatible API key in Settings. Rows deep-link to the explorer. Public RPCs cannot list “all txs for this address,” so we do not pretend otherwise. There is no 1337 history backend.

Yes. Names resolve on send, and Tools covers register / renew / DNS-style records. Paste an ENS name into Inspect the same way you would paste an address.

Same self-custody on the device: seed and private keys do not leave the machine in 1337, MetaMask, or Rabby. The split is what the vendor can collect. MetaMask ships MetaMetrics and vendor APIs. Rabby runs product and security services that can see usage. 1337 has no account, no analytics, no crash telemetry, and no 1337 server that could receive your IP or address.

An RPC you choose still sees requests from your wallet. That is true in every signer. Bring your own RPC if you do not want a public endpoint to see those calls. Third parties you opt into — LI.FI, an explorer key, Trezor Connect — still see what those features need. We do not get a copy. Full policy: Privacy.

Privacy is only possible when there is no central entity with the power to violate it. Other wallets keep that power: analytics, accounts, or a server that could watch you if they chose to. 1337 does not. There is no 1337 backend, no user database, and no analytics SDK. Keep all user data where it belongs on the user's machine. We cannot leak or sell what we do not have. That is architecture, not a privacy setting we might change later.

No. The wallet does not collect analytics, telemetry, addresses, balances, or usage. There is no 1337 server that receives your data, and there never will be. Vault, settings, and session stay in Chrome extension storage on the user's machine.

Third parties you choose — RPC, LI.FI when you swap, the explorer key you paste for History, Trezor Connect — still see what those features need. We do not get a copy. Full policy: Privacy.

No. A wallet that can collect is not private; it is promising not to. We will not add a 1337 analytics SDK, tracking server, or user database. If a feature talks to a third party you opt into, it is listed on the privacy page — it still does not phone home to us.

No. 1337 is a self-custody tool, not a bank. You hold the keys. We cannot recover a lost seed, reverse a send, or reimburse stolen or mis-sent assets. Software is provided as-is. Simulation and danger flags help you judge a request. They do not insure the outcome. Full text: Terms.

Ledger (WebHID) and Trezor Connect, alongside seed and private-key accounts. For “what if the extension is evil,” read hardware on Security.

It is a Chrome MV3 extension (side panel + popup). Chrome, Brave, Opera, and Arc install from the same Chrome Web Store listing. We develop against Chrome. Firefox is not listed.

Join Discord, follow @1337wallet on X, or open an issue on GitHub. Dapp and AI integration lives on Integrate. Keys and hardware: Security. Privacy compared with MetaMask and Rabby: Privacy FAQ.