Open the Vitreus Developer Explorer (stats.vtrs.io). If you already have Polkadot.js Extensions installed, then it will pop-up and ask you if you want to connect your account(s)
Ensure you're connected to the correct network (e.g., Vitreus mainnet).
Loading Your Account and Updating Metadata for Polkadot.js
If you're using Polkadot.js to connect your account to the Developer Explorer, this guide will help you set up your account, update the necessary metadata, and ensure smooth interaction with the network.
This method was chosen for safety considerations above in-browser account storage.
Click the extension icon to open the wallet interface.
Create or Import an Account:
IMPORTANT NOTE: Vitreus uses Ethereum Account types. Polkadot.js will naturally generate a Substate Account, which is not compatible with Vitreus. Updating Polkadot.js extension with the Mainnet metadata will make it possible to apply accounts to Vitreus. Any accounts added before the metadata update won’t be read by the orange explorer. They won’t be lost, they just cannot be properly read. Importing your seed phrase when Network is set to Mainnet configures the keypair in the correct manner to be compatible with Vitreus. No need to worry.
If you already have an account:
Click Import account from pre-existing seed. This extension acts like a wallet application, securely managing your seed/account and is not sent to anyone. This is a non-custodial browser extension.
Ensure the Network is set to Mainnet. If you do not see Mainnet, you will need to update the extensions metadata first, which requires an account. See Section 3 for details here
Enter your vApp wallets Seed Phrase into the extension.
Above is an eample of proper account setup
The box accepts 12 or 24 words and will highlight as viable after the first 12 are input.
Above is an example of Adding a name and password
Apply a Name and Password to your account. This Name is visible only to you, allowing you to track your accounts easier. The password will be required when you need to sign transactions. Clicking the orange button will load the account
Enter your mnemonic phrase or import a JSON file. Importing a JSON will require the password applied to that account.
If creating a new account: Click + Add Account. Make sure you set the Network to Mainnet Follow the prompts to set a name and password for your new account. Save your mnemonic phrase securely.
Set the Correct Network: Click the dropdown for the account and set it to the "Mainnet". If this option isn’t available, select the top option “Allow for use on any network” and see Section 3
Step 2: Connect Your Wallet to the Developer Explorer
Grant Permissions:
Open Polkadot.js, click Settings, and select Manage Website Access.
You can also click “Connect Accounts” at the top of the extension to open this window:
Note: See the wallet address? This wasn’t done correctly. Mainnet wasn’t set as the network so it created a Substrate account from the seed. Despite being added and connected, the Orange Explorer will not recognize this address as usable. You must try again.
See how this wallet address looks? This means it was done correctly with setting the Network to Mainnet. This is the proper format to use the Developer explorer.
Toggle on/off whichever accounts you want to grant access to the Developer Explorer and press the button at the bottom “Connect N Account(s)”
Refresh the Developer Explorer:
Reload the page to detect injected accounts. Press F5 on PC-based browsers to refresh the page. Your Polkadot.js account should now appear in the Developer Explorer under the "Accounts" or "Injected Accounts" section.
Step 3: Update Metadata for Custom Networks
If needed, there will be a notification icon near the Settings tab on the navigation bar. If this is the case, go to Settings > Metadata. Click to update the metadata in your extension
Sync the Metadata in Your Wallet: After uploading, your Polkadot.js wallet will automatically update to recognize the network’s runtime modules and features. Ensure that the network name (e.g., "Mainnet") appears correctly in your wallet's dropdown.
Step 4: Verify and Test Your Setup
Check Injected Accounts:
Return to the Developer Explorer and verify that your account is listed under "Accounts."
Perform a Test Transaction:
Use the Developer Explorer to initiate a small transaction or interaction (e.g., submit candidacy or a simple token transfer).
Approve the transaction in Polkadot.js to ensure everything is working correctly.
Resolve Any Errors:
If the Developer Explorer doesn’t recognize your account or network: Double-check the network prefix and metadata. Ensure you’ve granted permissions in Polkadot.js.
Updating the Polkadot.js Extension with Vitreus Mainnet Metadata
By default, the Polkadot.js Extension isn’t loaded with Vitreus Mainnet Metadata… yet.
In order to make the network recognizable, we will need to create a dummy account in the extension and prompt the developer explorer to give us the metadata update!
Click the blue text “polkadot-js extension” (takes you HERE)
Add the Extension
Add Extension
With the Extension installed, click back to the Developer Explorer. Refresh the page (F5)
You will have two, extension-based popups show up. Click them.
After these are clicked. Refresh OE again. You will see a notification on the Developer Explorer near the Setting tab on the navigation bar. You might need to refresh the page first.
Go to Setting > Metadata Click Update Metadata
This will pop up:
Depending on your settings in the extension, you may not see this popup until you go to the extension itself. It will have this red “Auth” banner awaiting for you to see the above screen.
Click “Yes, do this metadata update”
Your extension will now be updated.
You can now import your account with Mainnet as the Network.
Note: Metadata Updates are required for the network EVERYTIME there is a runtime update. This applies to all substrate networks.
Why Use A Polkadot Browser Extension?
1. Open-Source Transparency
Polkadot.js is fully open-source, meaning its codebase is publicly available for anyone to review, audit, and verify.
Developers and security experts worldwide scrutinize the code, ensuring there are no hidden vulnerabilities or backdoors.
Regular community and third-party audits bolster trust and reliability.
2. Local Management of Private Keys
Private keys never leave your device. Polkadot.js does not store your seed phrase or private keys on external servers. Instead, they are securely stored locally in your browser’s extension.
By managing keys locally, you maintain full ownership and control over your funds, reducing the risk of centralized breaches.
3. Non-Custodial Design
Polkadot.js is a non-custodial wallet, meaning it does not hold or have access to your funds, seed phrase, or private keys.
This ensures that only you have control of your assets, making it impossible for any third party (including Polkadot.js developers) to access your funds or data.
Polkadot.js doesn’t act as a wallet, the same way vApp, Metamask or Trust Wallet do. It is an account manager that can be used to sign transactions, such as transfers, with.
4. Secure Encryption Standards
Polkadot.js uses industry-standard encryption protocols to protect your seed phrase and account information.
Data is securely encrypted and stored locally on your device, minimizing the risk of unauthorized access.
5. User Permissions and Privacy
Polkadot.js does not collect personal information or track your activities.
It operates on a permission-based model, requiring you to explicitly grant access to any third-party website or app. You have full control over which applications can interact with your wallet.
Websites and dApps (like your Developer Explorer) cannot access your wallet or account unless explicitly authorized.
6. Network Compatibility and Updates
Polkadot.js is built specifically for Polkadot, Kusama, and Substrate-based networks like Vitreus, ensuring seamless integration with the latest network features and governance tools.
The wallet regularly updates its metadata to ensure compatibility with network upgrades, keeping it secure and functional.
7. Backup and Recovery Options
Polkadot.js provides a simple way to back up your account with your 12- or 24-word seed phrase, allowing you to recover your account even if you lose access to your device.
As long as you securely store your seed phrase offline (e.g., on paper or in a hardware wallet), you can rest assured that your account remains safe.
8. Proven Track Record
Polkadot.js has been used by hundreds of thousands of users across Polkadot, Kusama, and other Substrate ecosystems since its launch.
It has a strong track record of reliability and security, with no major vulnerabilities compromising user funds to date.
9. Customization and Fine-Tuned Control
Polkadot.js allows advanced users to customize their account settings, permissions, and network preferences, giving greater flexibility and control over their accounts.
This makes it ideal for participating in governance, staking, and other network-specific activities.
10. Community and Support
Polkadot.js is supported by a vibrant community of developers, security experts, and enthusiasts. If you have questions or concerns, there are active forums, documentation, and support channels to help you resolve them.
This community-driven approach adds an extra layer of transparency and trustworthiness.
Addressing Concerns
“What if I lose my seed phrase?”
As with any wallet, losing your seed phrase means losing access to your funds. Polkadot.js emphasizes the importance of securely backing up your seed phrase offline (e.g., in multiple physical locations).
“Can someone hack my wallet?”
Your private keys never leave your device, and strong encryption protects your data. As long as your computer is secure and free from malware, your Polkadot.js wallet is highly secure.
To enhance security, consider pairing Polkadot.js with a hardware wallet for an extra layer of protection.
“How do I know it’s safe to use on a new site?”
Polkadot.js only interacts with websites you explicitly authorize. Unauthorized sites cannot access your wallet, keeping your account safe from phishing attempts.
Final Note: Ownership Equals Responsibility
Using Polkadot.js empowers you with complete control over your accounts and assets. While this means you bear full responsibility for safeguarding your seed phrase, it also ensures that your funds are safe from third-party failures or exploits.
By following best practices—such as securing your seed phrase offline and using a secure device—you can confidently use Polkadot.js to manage your accounts and participate in the network’s governance, staking, and more.
What's the Difference between Browser Extension and In-Browser Account Storage?
Comparison Table
Browser Extension
The Polkadot.js browser extension is a standalone application installed in your browser (like Chrome, Firefox, or Edge) to securely manage your accounts.
How It Works
The extension stores your private keys and seed phrases securely on your local device, isolated from the main browser storage.
It acts as an intermediary between your accounts and web applications (e.g., the Developer Explorer), injecting your accounts securely when permission is granted.
Key Features
Account Isolation:
The extension keeps your accounts independent of specific websites, meaning they are only "injected" into apps when explicitly allowed.
This protects your accounts from unauthorized access.
Enhanced Security:
Private keys are encrypted and stored within the extension itself, not in the browser's general storage.
Websites cannot access the keys or accounts unless explicitly permitted.
Portable Across dApps:
Once installed, the extension works seamlessly with multiple dApps and websites, providing a unified interface for account management.
Explicit Permissions:
Before interacting with any website, the extension prompts you to grant or deny access. Only trusted websites are allowed to interact with your accounts.
User-Friendly Account Management:
The extension provides an easy-to-use interface for managing multiple accounts, networks, and configurations.
Best Use Cases
Frequent use of multiple Polkadot/Substrate dApps.
Maximum security for accounts used across multiple browsers and devices.
Easy switching between networks and accounts.
In-Browser Local Storage
When you store your account directly in the in-browser local storage, the private keys and account data are stored as part of the browser's internal storage system.
How It Works
The browser stores your account data locally, typically within the application’s cache or local storage.
The Developer Explorer (or other dApps) directly accesses this data without needing an intermediary like the extension.
Key Features
Direct Integration with the dApp:
The account is managed directly by the application (e.g., Developer Explorer), which simplifies integration but ties the account to the specific dApp.
Less Secure Storage:
Local storage is more vulnerable to security risks compared to the extension.
If malicious scripts gain access to your browser’s storage (e.g., via an untrusted website), they may retrieve your account data.
No Cross-App Portability:
Accounts stored in local storage are not accessible to other applications or websites. They are tied to the specific app or domain that created them.
No Explicit Permissions:
Unlike the extension, local storage doesn't provide a mechanism to control which apps or websites can access the account. It relies entirely on the app's implementation.
Best Use Cases
Single-purpose accounts used exclusively for one dApp or application.
Experimental or low-stakes accounts where maximum security is not a priority.
Offline or isolated environments where additional security is enforced at the system level.
The browser extension is the safer and more flexible option for managing accounts, particularly for high-value or frequently-used wallets. It provides better isolation, security, and control over account permissions. On the other hand, in-browser local storage can be useful for temporary or low-stakes accounts, but it comes with increased security risks and limited portability.