img width: 750px; iframe.movie width: 750px; height: 450px;
Meteor wallet extension setup and usage guide
Meteor wallet extension setup and usage guide
Immediately after installation, click the browser toolbar icon and select "Import wallet" if you possess a pre-existing seed phrase from another cryptocurrency interface. For new users, choose "Create wallet" and securely store the generated 12-word mnemonic phrase offline–never digitally. Write it on paper and store it in a fireproof safe. Losing this seed phrase means permanent loss of access to your funds; no recovery mechanism exists.
Once inside the interface, locate the "Settings" or "Security" tab to enable two-factor authentication (2FA) via a hardware device like a Ledger or via a TOTP app such as Authy. Without 2FA, your stored assets remain vulnerable to browser-level malware. Next, configure the network selection: for token transfers, choose the fastest option with the lowest gas fees, such as a Layer-2 solution; for main asset holdings, select the secure base chain (e.g., mainnet).
To execute a transfer, click the "Send" button, paste the recipient’s public address (derived from a QR code or copied directly from a trusted exchange), and specify the exact amount. Set the gas limit manually to avoid overpaying or transaction failure–use a current average estimate from an analytics site like Etherscan. After confirming the transaction, monitor its status via a block explorer linked directly from the interface. Never share your private key or seed phrase with anyone, even under technical support requests; legitimate teams will never ask for these.
Meteor Wallet Extension Setup and Usage Guide
Download the official software exclusively from the Chrome Web Store or the publisher's GitHub repository. Confirm the publisher is "Tuum Tech" and verify a minimum of 10,000 user reviews to avoid counterfeit copies. After installation, pin the icon to your toolbar for rapid access. Click the icon to initiate the bootstrap sequence, which presents two pathways: generation of a fresh cryptographic identity or restoration via a seed phrase.
Privileged backup: The system displays a 12 or 24-word recovery phrase. Write this sequence on paper only; never store it digitally. Store this paper in a fireproof safe. Losing this string forfeits all asset access permanently.
Validation check: The application requests confirmation of the third, seventh, and eleventh words from your backup. This ensures you recorded the cipher correctly before proceeding.
Access credential: Define a local password with a minimum of 8 characters, combining uppercase, lowercase, and numerals. This key only unlocks the local interface; it cannot restore your funds if the recovery phrase is lost.
Upon completing initialization, the dashboard displays your primary public address (a 64-character hexadecimal value beginning with "0x"). This address is your blockchain identifier for receiving tokens. Copy it via the "copy" icon (clipboard symbol) to share with counterparties. The interface also shows a zero balance for NEAR and any NEP-141 tokens until you execute a transfer.
For incoming transfers: Provide your public address to the sender. Confirm the transaction on a block explorer like NearBlocks.io after 2-3 block confirmations (approximately 2-3 seconds on NEAR).
For outgoing transactions: Click "Send", paste the recipient’s address, input the amount (e.g., 1.5 NEAR), review the gas fee (typically 0.0001 NEAR), and confirm with your password.
Token management: Click "Manage Tokens" to toggle visibility for assets like USDC, AURORA, or REF. Add custom contracts via their NEP-141 contract address.
Configure network preferences by clicking the gear icon. The default is "Mainnet" (hash: `mainnet.near.org`). Switch to "Testnet" (hash: `testnet.near.org`) for development. Each network requires a separate identity; testnet tokens have no monetary value. Avoid custom RPC endpoints unless you operate a private node, as public endpoints may leak your IP address.
For security hardening, enable "Auto-lock" under Settings → Security. Set the timer to 1 minute of inactivity. Disable "Allow dApp Connections" globally to prevent automatic approvals; approve per-site requests manually only after verifying the dApp URL (e.g., `app.ref.finance`). Never click "Approve" on pop-ups that appear without user action.
Troubleshooting common failures: If the "Not enough balance" error appears despite visible funds, refresh the interface (Ctrl+R) or switch to a different RPC provider. For transaction failures with error `-32000`, clear the browser cache and reconnect the network in settings. If the extension fails to load, verify browser compatibility (Chrome 100+, Brave 1.50+, Edge 99+).
Downloading and Verifying the Official Meteor Wallet Extension from the Chrome Web Store
Open Chrome and navigate directly to the Chrome Web Store, then search for the specific tool by its exact name, "Meteor Wallet recovery phrase Wallet." The verified software will appear with a distinctive "Featured" badge and an official developer name, "Meteor Wallet Team," often displaying over 100,000 users and a high rating above 4.5 stars. Click on the listing and meticulously inspect the developer’s email address and support site listed in the "Additional Information" section; any discrepancy indicates a fraudulent copy. Avoid any identical-looking clones with different publisher names or recent upload dates.
Before initiating the download, verify the digital signature by checking for a blue "Verified" checkmark next to the publisher name. Cross-reference the total number of installs and the date of the most recent update, which should be within the last two months. After confirming these indicators, click "Add to Chrome" and authorize the permissions, which should be limited to reading your browser’s storage for session management and accessing a few specific website URLs for transaction interaction. Once installed, immediately locate the "Puzzle Piece" icon in the top-right browser bar, pin the new icon, right-click it, and select "Manage Extension" to confirm the source code ID matches the official listing on the Chrome Web Store (e.g., "ojgnkmkapgnjnjjlfgmdboklcnaoompi"). Reject any pop-ups asking for manual import of secret phrases or private keys at this stage.
Creating a New Wallet: Seed Phrase Generation, Backup, and Secure Storage
Initiate key generation only on a fresh, offline device disconnected from any network. The software will produce a 12 or 24-word mnemonic seed phrase using the BIP-39 standard; prefer 24 words for 256-bit entropy. Immediately after display, write the phrase on two separate steel plates (e.g., Cryptosteel or a Billfodler) using a punch tool–paper is vulnerable to fire and water. Never photograph the phrase, type it into any computer file, or paste it into a cloud service.
Storage MethodThreat MitigatedRecommended QuantitySteel plate (fireproof/waterproof)Fire, flood, physical decay2 copies in separate locationsBank safe deposit boxTheft, unauthorized access1 copy (backup only)Encrypted USB (offline only)Digital key loss0 (do not store digitally)
Test recovery by wiping the application data (not the phrase) on a secondary machine and entering the seed phrase to verify it restores the same cryptographic identity. Store one steel plate off-site–e.g., a trusted relative’s safe–and the other in a fire-resistant home safe bolted to a concrete floor. Never store the phrase in a phone note, password manager (e.g., LastPass), or email draft; these are hot targets for remote extraction. Use a BIP-39 passphrase (25th word) for plausible deniability: store a "decoy" wallet with a small balance and a separate passphrase for the primary account.
Importing an Existing Wallet Using a Seed Phrase or Private Key
Click the primary icon of the application in your browser toolbar, then select the option labeled "Import an existing profile" instead of creating a new one. You will be presented with two distinct methods: entering a 12 or 24-word mnemonic phrase, or pasting a raw private key. Choose the seed phrase option if your original account was generated via a mnemonic standard–this method restores your entire suite of addresses derived from that specific seed. For a single account, such as one from a hardware device or a specific Ethereum address, use the private key field. Ensure you are in a completely offline environment (no screen recording software active) before typing or pasting any sensitive data.
When pasting a mnemonic phrase, verify that every word is in the correct order and from the official BIP-39 English wordlist. A single misspelled or out-of-sequence entry will produce a different cryptographic root, resulting in a completely different account set. The interface will automatically strip leading and trailing spaces, but check for extra spaces between words manually. After confirming the phrase, the system will compute the checksum internally; if it fails, you will see a "Invalid mnemonic" error immediately. Do not attempt to fix a phrase by guessing–recheck your original backup. For private key import, the key must be 64 hexadecimal characters (for an uncompressed key) or 66 characters (starting with "04"), or a 128-character string for certain extended keys. The application supports both raw hex and the common 0x-prefixed format; remove any quotation marks or line breaks before submission.
Once the system validates your input, it will display a preview of the primary address and its associated balance (if the network is live and connected). This is a read-only confirmation step; the actual import does not occur until you click the "Import" or "Confirm" button. At this stage, you can choose an account name–use a descriptive label like "Ledger Main Account" or "Old Trust Wallet" to differentiate multiple imported profiles. After confirming, the app will derive the standard paths (m/44'/60'/0'/0/0 for Ethereum-based chains) and add the account to your local storage. Note that importing via private key only brings in that single address; it does not scan for additional accounts or token balances on other derivation paths. To recover a full multi-account setup, always use the seed phrase.
After the import completes, immediately verify that you can sign a simple test transaction (e.g., sending 0 ETH to your own address) to confirm the cryptographic keys are correctly loaded. If you imported using a private key, delete the plaintext key from your clipboard and any temporary files–never store it in a text file or note app. For mnemonic imports, the software will prompt you to set a new local password; choose one that is at least 12 characters long with mixed case and symbols. This password encrypts the stored key material on disk, so losing it means you must re-import using the original recovery data. Finally, navigate to the settings and enable the "Hide balances" feature to prevent shoulder-surfing attacks when your browser is open in public spaces.
Q&A:
I just installed the Meteor Wallet extension on Chrome. Why can't I see my SOL balance even though I already have tokens on that address?
This typically happens because Meteor Wallet creates a new wallet by default. After installation, the extension will generate a fresh Solana address for you, and your existing tokens are on a different keypair. To see your SOL balance, you need to import your existing wallet using the seed phrase. Click the wallet icon, select "Import Wallet," and enter the 12 or 24-word recovery phrase from your previous wallet. Once imported, your balance should appear. If it still shows zero, double-check that you imported the exact phrase and that the network selected (Mainnet Beta vs. Devnet) matches where your tokens are stored.
When I try to send SOL from Meteor Wallet, the transaction keeps failing. What could be wrong?
Transaction failures in Meteor Wallet usually stem from insufficient funds for gas fees or network congestion. First, confirm you have at least 0.001 SOL in your wallet to cover the transaction fee. If you have enough SOL, check the RPC endpoint your extension is using. A slow or overloaded RPC (like the public default one) can cause timeouts. Go to Settings, then "Network," and switch to a different RPC provider, such as Helius, Triton, or QuickNode. If the issue persists, try clearing the extension's cache or disabling any ad blockers that might interfere with the transaction signing process.
I connected Meteor Wallet to a dApp, and it asks me to "approve" a token approval transaction. After I did that, the site took some SOL from my wallet. Was I scammed?
You likely encountered a malicious dApp that asked for an infinite approval (unlimited token spending authority). Unlike standard transaction approvals that allow a one-time transfer, a malicious contract can request permission to move all tokens from your wallet address. Once approved, it can drain your SOL and SPL tokens without further warnings. Immediately revoke the approval by going to Meteor Wallet's "Activity" tab, finding the approval transaction, and selecting "Revoke." You can also use a Solana revoke tool like "Solscan" or "Rabby Revoke" to find and remove suspicious allowances. Next time, only approve contract interactions for trusted dApps and specify a strict spending limit if the wallet interface allows it.
I am trying to stake my SOL through Meteor Wallet. The process looks different from other wallets I've used. How do I choose a validator, and is my SOL locked up?
Meteor Wallet integrates native staking directly into the extension. To stake, click on "Stake" in the sidebar. You will see a list of validators with their APY, commission rate, and stake pool size. Choose a validator—lower commission (under 10%) and a pool size of 50 million to 200 million SOL are considered stable. After clicking "Delegate," you will sign a transaction. Your SOL is not locked; it stays in your wallet but becomes "staked." To withdraw, you must "undelegate," which takes 2–3 epochs (roughly 4–6 days). During that cooling-off period, your SOL cannot be traded or used in DeFi. One detail many users miss: you can stake any amount above 0.001 SOL, but you need around 0.002 SOL remaining for transaction fees.