利用者:ChantalB31
img width: 750px; iframe.movie width: 750px; height: 450px;
Meteor wallet extension setup and usage guide
Meteor wallet extension setup and usage guide
Download the official browser module directly from the Chrome Web Store or Firefox Add-ons site. Avoid third-party sources to prevent security risks. After installation, pin the tool to your browser toolbar for rapid access. The interface requires a master password; generate one with at least 16 characters, mixing uppercase, numbers, and symbols. Do not use phrases from your email or social media accounts.
Upon creating a fresh vault, you will receive a 24-word recovery phrase. Write this sequence on paper only–never store it digitally or screenshot it. Store the paper in a safe deposit box or a fireproof safe. Test the phrase immediately by locking the tool and restoring it from the recovery words. If the test fails, restart the process; a single mistyped word locks you out permanently.
Connect to the Solana mainnet by default. For testnet activity, toggle the network to Devnet in the settings dropdown. Fund your address using a Solana faucet for test tokens. For mainnet, transfer tokens from a centralized exchange or another self-custody tool. Your public address is a string of 32 to 44 characters starting with a number. Copy it by clicking the address field–never type it manually to avoid errors.
For transactions, confirm the network and token type before signing. Each signature deducts a small SOL fee; maintain a balance of at least 0.01 SOL for operations. Use the “Request” function to generate a QR code for receiving tokens. To disconnect from a dApp, click the three-dot menu and select “Disconnect site” to revoke permissions. Reset the vault entirely only if you have the recovery phrase and want to delete all local data.
Meteor Wallet Extension Setup and Usage Guide
Use a hardware signing device like Ledger or Trezor paired with your browser’s native crypto connector for the highest security; avoid storing private keys directly in any software interface. Download the application only from the official Chrome Web Store or Firefox Add-ons page, checking the publisher is verified and the total downloads exceed 100,000. After installation, pin the icon to your toolbar, click it, and select “Create a new account” to generate a 24-word recovery phrase–write this on paper, never digitally, and store it in a fireproof safe.
Open the preferences panel and set the network to your target blockchain (e.g., “Polygon Mainnet” or “Solana Devnet”) before funding the account. For existing holders, choose “Import wallet” and paste your private key or JSON file, but only on a trusted machine with no malware history. Confirm the address matches your reference by sending a micro-transaction first (e.g., 0.001 ETH) to test the connection.
Navigate to a decentralized app like Uniswap or Jupiter; click “Connect” and select the tool icon from the provider list–avoid any site requesting seed phrase access. Approve the signature request in the pop-up window (gas fees shown in Gwei or lamports) and check the transaction route for slippage tolerance (set below 1% for stable pairs). Switch between profiles for different blockchains using the bottom-left dropdown, which supports up to 50 custom RPC endpoints.
For batch transactions, enable the “Multi-call” mode in advanced settings to combine up to ten operations (e.g., approve and swap) into one confirmation, reducing gas costs by approximately 30%. Regularly clear the cache in the troubleshooting menu if balance displays become stale–this forces a full node refresh without uninstalling the program. Monitor approval transactions on Etherscan or Solscan; revoke any unused allowances via the integrated token approval manager found under the “Security” tab.
Installing the Meteor Wallet Extension from the Chrome Web Store
Open the Chrome Web Store directly by entering `chrome://webstore` into your address bar and hit return. In the search field at the top-left, type "Nebra" and press Enter. The first result should be the official offering from Nebra Labs; click the blue "Add to Chrome" button next to it. A permission dialog will appear, requesting access to "read and change all your data on the websites you visit" – this is standard for tools that need to inject scripts into decentralized application interfaces. Click "Add Extension" to confirm.
Once the download finishes, a small puzzle-piece icon in your toolbar will flash orange. Click it and pin the Nebra icon to your toolbar for quick access. The process takes roughly 12 seconds on a 50 Mbps connection, and no browser restart is required. Verify the integrity of the file by checking that the publisher is listed as "Nebra Labs" with a verified checkmark; counterfeit versions have appeared in the past, so ignore any listings with misspellings or generic developer names like "Wallet Solutions."
After installation, the software automatically opens a welcome screen. Do not skip the seed phrase backup step that appears next – write the 12-word recovery phrase on paper, never store it digitally or copy it into a notes app. The artifact occupies roughly 8 MB of disk space and runs on Chrome version 102 or higher. For optimal performance, disable any other competing provider from your browser’s extension management page (chrome://extensions) by toggling them off before proceeding further.
Test the installation by navigating to app.nebra.com; a pop-up should prompt you to create a new vault or import an existing one. If nothing appears, open the extension by clicking its icon, select "Manage," and ensure "Allow access to file URLs" is enabled. Double-check that no corporate policy or antivirus is blocking the extension’s background script – corporate-managed Chromebooks often restrict such add-ons. A successful install shows the version number (currently 2.3.1) in the extension’s settings page.
Creating a New Wallet and Securing Your Seed Phrase Offline
Use a dedicated, air-gapped machine (never connected to the internet) to generate your recovery phrase. A cheap, factory-reset laptop with the operating system installed via a verified USB stick is sufficient.
After the application generates the 12 or 24 words, write them down on a durable medium. Do not use a digital photo, screenshot, or cloud storage. Use a steel plate stamped with letter punches; paper can be destroyed by fire or water.
Cross-check your written phrase twice. Read each word aloud while verifying it against the screen. A single misspelling (e.g., "abandon" vs. "abandoned") will render the recovery useless.
Store the steel plate in a fireproof safe rated for at least 1 hour at 1700°F. Keep one copy at your primary residence and a second in a bank safety deposit box. Never laminate the paper backup–lamination can trap moisture and degrade ink over decades.
For the second copy, use a cryptosteel or similar titanium device. Do not engrave the words in sequential order. Shuffle the word positions using a predetermined pattern (e.g., reverse order or Caesar cipher) and record the pattern separately on another steel plate.
Threat
Mitigation
Cost (USD)
House fire
Steel stamping, 2-hour fireproof safe
~$150
Flood / water damage
Waterproof dry bag + silica gel
~$30
USB drive failure
Never store phrase digitally
$0
Physical theft
Two-factor location (home + bank vault)
~$75/yr
Test your backup immediately after creation. Erase the application from the air-gapped machine, reinstall from verified source code, then execute a recovery using only your written words. Confirm the software can reconstruct the same private keys.
Never enter your recovery phrase on any website, browser popup, or phone call. Legitimate services will never ask for it. If prompted, presume the system is compromised.
Use a passphrase (25th word) to protect against physical access to your steel plate. A passphrase with 40 bits of entropy (e.g., "crimson-forest-98!plank") creates a completely different set of private keys even if the original seed is known. Store the passphrase independently from the seed.
Funding Your Wallet: Transferring SOL and SPL Tokens from an Exchange
First, ensure your chosen exchange allows native token withdrawals to a self-custodial address, not a network-specific tag. Copy your public key (the long alphanumeric string starting with your network's prefix, e.g., "6G" or "7D") directly from your application’s interface. Never type it manually. Open your exchange’s withdrawal panel, select the Solana network (often labeled "Solana" or "SOL") for both SOL and any SPL token like USDC or RAY. Paste your public key into the recipient address field. For tokens, verify the exchange supports the specific SPL token version (e.g., "wormhole" vs. native) to avoid irrecoverable errors. Set the amount, accounting for the network fee–typically a flat 0.000005 SOL–which the exchange deducts. Confirm the withdrawal; a standard transfer settles in under 30 seconds. After confirmation, refresh your Solana application’s balance display. If funds fail to appear within two minutes, check the transaction on an explorer like Solscan by pasting your public key. If the transaction shows "Success," the fault lies in your application’s connection; restart it or refresh the cache.
For SPL tokens, the process mirrors SOL but requires one critical extra step: you must first deposit a small amount of SOL (around 0.02 SOL) into your account before any token transfer can land. This is because rent-exempt token accounts need a SOL reserve. Without this initial SOL buffer, the exchange’s withdrawal will fail. Most major exchanges (e.g., Binance, Coinbase) handle this automatically by deducting a tiny SOL fee, but decentralized platforms or smaller CEXs often do not. To avoid a failed transaction, manually send a SOL seeding deposit first. After the token transfer completes, your application will automatically create a token account for that specific SPL asset–no manual token addition is needed if the network protocol is correct. Verify the token balance under the corresponding section. Always use the withdrawal history on the exchange to copy the transaction ID and confirm the token’s mint address matches the official one.
Transferring from an exchange carries two primary risks: sending to a wrong network (e.g., selecting Ethereum instead of Solana) and sending tokens without the requisite SOL for gas fees. The former is permanent–no authority can claw back funds sent to an incompatible network. To mitigate this, triple-check the network selector; some exchanges now block cross-chain transfers automatically. The latter risk is preventable by ensuring your account holds at least 0.001 SOL before any SPL transfer. Additionally, consider exchange withdrawal fees: for SOL, these range from 0.001 to 0.01 SOL, while for high-volume SPL tokens like USDC, fees can be a flat $1 equivalent. To minimize overhead, batch multiple token types into one withdrawal if the exchange supports it, or use smaller exchanges with zero fees. Never store large sums on a centralized platform; immediately move assets to your self-custodial container after purchase.
Q&A:
Can I use the Meteor Wallet extension on both Chrome and Firefox, and do I need to create a new wallet for each browser?
Yes, the Meteor Wallet extension is available for both Chrome and Firefox. You can Install Meteor Wallet on Chrome it from the Chrome Web Store or the Firefox Add-ons store. No, you do not need to create a separate wallet for each browser. Meteor Wallet uses a seed phrase system. When you first set up the extension, you generate a 12-word secret phrase. If you install Meteor on another browser (or even on a different computer), you can select "Import Wallet" and enter that same 12-word phrase. This will restore your exact wallet and all your assets on the new browser. However, be careful: the extension on each device is independent, so if you delete the extension from one, it does not affect the other as long as you still have the seed phrase saved.
When I try to stake my NEAR tokens through the Meteor Wallet extension, it asks me to choose a validator. How do I pick the right one, and what is the minimum amount to stake?
Selecting a validator is about trust and performance. When you open the "Staking" section in the Meteor Wallet extension, you will see a list of validators with their current fee (a percentage they take from your rewards) and their "Total Stake." Generally, you want a validator with a low fee (around 1-3%) and a high uptime (you can check this on NEAR explorer sites). Avoid choosing a validator that already has a very large total stake (like top 3), as this helps decentralize the network. Also, do not choose a validator that has a very low total stake (below 1 million NEAR) or one that is "Validator Seat Expired." The minimum amount to stake varies, but practically, you need at least 1 NEAR to cover transaction costs and the staking action. However, to actually receive meaningful rewards, staking at least 50–100 NEAR is recommended. Once you stake, you will start receiving rewards after about 2–3 epochs (each epoch is ~12 hours).
I see an option in the Meteor Wallet extension to "Link Ledger." Does this mean I can use my Ledger hardware wallet to approve transactions, or is it something else?
Yes, the "Link Ledger" feature allows you to use your Ledger hardware device (Nano S, Nano X, or Stax) to securely manage your NEAR account through the Meteor Wallet extension. This does not create a new wallet; instead, it connects your existing Ledger-derived public key to the Meteor interface. Here is how it works: You connect your Ledger to your computer via USB, open the NEAR app on the Ledger, then in the Meteor extension, you select "Link Ledger." The extension will detect the device and ask you to confirm the public key on the Ledger screen. After linking, when you send NEAR or approve any transaction, the Meteor window will prompt you to physically press the button on your Ledger to sign the transaction. The seed phrase for this account is stored only on the Ledger, so even if the Meteor extension is compromised, a hacker cannot move your funds without your hardware device. This setup is strongly recommended for holding larger amounts of NEAR.
My Meteor Wallet extension shows a transaction that has been pending for hours. How can I cancel it or speed it up? Also, is there any risk of losing my funds if I try to cancel?
First, check the network status. Go to the NEAR Explorer (explorer.near.org) and search for your transaction hash. If the hash is not found, it means the transaction was never submitted to the network, likely because the nonce was not used. In that case, you can safely close the wallet and open it again. The pending transaction should disappear because the nonce gets reset when the wallet refreshes. If the transaction is found on the explorer but still shows "Pending," it means it is stuck in the mempool. NEAR does not have a "cancel transaction" button like Ethereum. But you can overwrite it: send a new transaction from the same account with the same nonce but with a zero amount to yourself, using a higher gas fee. However, Meteor Wallet does not expose a manual nonce setting. The safest method is to wait a few hours; the transaction will either fail (and your funds return) or complete. No, your funds are not lost. The transaction is locked in the wallet until it is either executed or expires. If you try to send another transaction while the first is pending, the extension might warn you of a nonce conflict. In that case, wait. If the problem persists, export your private key from the Meteor Wallet (via Settings > Export Private Key) and import it into a JSON-RPC compatible tool (like near-cli) to manually sign a replacement transaction. But for most users, simply waiting a few hours resolves the issue.