{"id":552817,"date":"2025-01-30T15:49:36","date_gmt":"2025-01-30T15:49:36","guid":{"rendered":"https:\/\/gridnet.org\/wpp\/?p=552817"},"modified":"2026-03-07T20:08:20","modified_gmt":"2026-03-07T20:08:20","slug":"gridnet-os-wallets-and-identity-management","status":"publish","type":"post","link":"https:\/\/mag.gridnet.org\/index.php\/2025\/01\/30\/gridnet-os-wallets-and-identity-management\/","title":{"rendered":"GRIDNET OS Wallets and Identity Management"},"content":{"rendered":"

Introduction to Public Key Cryptography in GRIDNET<\/h2>\n

Notice: Many GRIDNET OS GridScript commands come with built-in MAN pages. The MAN page of the main utility described herein is available through keychain -help<\/code><\/p><\/blockquote>\n

<\/code> \nPublic key cryptography forms the foundation of security in GRIDNET’s decentralized operating system. To understand how GRIDNET manages identities and secures assets, let’s first explore the core concepts of public key cryptography.<\/p>\n

Core Concepts<\/h2>\n<\/p>\n
At its heart, public key cryptography uses a pair of mathematically related keys: a private key and a public key. In GRIDNET, these keys are generated using Elliptic Curve cryptography, which provides strong security while keeping key sizes manageable. Here’s how the system works:<\/p>\n
Private Keys<\/h3>\n\nA private key is a secure, randomly generated number that must be kept strictly confidential<\/li>\n
Think of it as your digital master key or signature<\/li>\n
In GRIDNET, this is what you see as your “Secret” in the mobile app<\/li>\n
Anyone who has your private key can control your State Domains (accounts) and assets<\/li>\n
Private keys should never be shared or stored in unsecured locations<\/li>\n<\/ul>\nPublic Keys<\/h3>\n\nEach private key has a corresponding public key that’s mathematically derived from it<\/li>\n
The public key can be freely shared without compromising security<\/li>\n
It’s computationally infeasible to determine the private key from the public key<\/li>\n
In GRIDNET, your public key is used to derive your State Domain addresses<\/li>\n<\/ul>\nAddresses<\/h3>\nIn GRIDNET, your public-facing identity (address) is derived from your public key through a series of cryptographic operations. This creates a human-readable format that’s easier to work with than raw public keys. Think of your address as your account number that others can use to interact with your State Domain.<\/p>\n
Digital Signatures and Authentication<\/h2>\nGRIDNET OS State Domains and authentication are brought to next level due to innovative authentication model. Imagine you are using a decentralized graphical application hosted atop of GRIDNET OS. The application is a decentralized streaming service delivering movies frames to you while every now and then displaying a QR code indicating the service provider (the remote app) requires an off-the-chain payment. You pull out your mobile app scan the QR code and everything happens under the hood through an onion routed connection. The remote app is notified and so is the decentralized user interface visibile in your web browser.
\n<\/p>\n
When you perform operations in GRIDNET, such as sending tokens or interacting with smart contracts, here’s what happens behind the scenes:<\/p>\n
\nThe operation details are combined into a message<\/li>\n
Your private key creates a unique digital signature for this message<\/li>\n
Anyone can verify this signature using your public key<\/li>\n
The signature proves you authorized the operation without revealing your private key<\/li>\n<\/ol>\n<\/p>\n
This system ensures that:<\/p>\n
\nOnly you can create valid signatures for your State Domain<\/li>\n
Others can verify your signatures without knowing your private key<\/li>\n
Signatures cannot be forged without access to the private key<\/li>\n
Each signature is unique to the specific operation being performed<\/li>\n<\/ul>\nThe GRIDNET Innovation: Multi-dimensional Keys
\n<\/h2>\nGRIDNET introduces an innovative, in terms of interactive (also supporting autonomous identity switching during mining Operations!) command line management , approach to key management through its multi-dimensional key system:<\/p>\n
Flat Keys<\/h3>\n\nTraditional single-purpose private keys<\/li>\n
Each key controls exactly one State Domain<\/li>\n
Simpler to understand but less flexible for managing multiple accounts<\/li>\n<\/ul>\nMulti-dimensional Keys (Master Private Keys)<\/h3>\n<\/p>\n
\nCan control multiple State Domains from a single master key<\/li>\n
Uses a clever “Vector IV” system to derive sub-identities<\/li>\n
More efficient for users managing multiple accounts<\/li>\n
Built-in support in both GRIDNET Core and Mobile app
\n<\/li>\n<\/ul>\nThis multi-dimensional approach offers several advantages:<\/p>\n
\nSimplified backup (just one master key to secure)<\/li>\n
Easy management of multiple identities<\/li>\n
Seamless switching between different State Domains<\/li>\n
Enhanced security through compartmentalization<\/li>\n<\/ul>\nSecurity Implications<\/h2>\nUnderstanding public key cryptography helps you appreciate why:<\/p>\n
\nPrivate keys must be backed up securely<\/li>\n
Never share your private key or “Secret” with anyone<\/li>\n
Export operations should be performed in secure environments<\/li>\n
Different State Domains can be isolated while still being controlled by one master key<\/li>\n
The importance of the fingerprint verification in the mobile app<\/li>\n<\/ul>\nIn the following sections, we’ll explore how to practically manage these cryptographic elements using both GRIDNET Mobile and Core, but this fundamental understanding of public key cryptography will help you make informed decisions about key management and security.<\/p>\n
Next, we’ll dive into how GRIDNET implements these concepts in its identity system, building on this cryptographic foundation to create a flexible and secure decentralized operating system.<\/p>\n
GRIDNET Identity System Overview<\/h2>\n
State Domains: The Foundation of GRIDNET Identity<\/h2>\nIn GRIDNET’s decentralized operating system, a State Domain functions as what we traditionally think of as an account or wallet. However, it’s more sophisticated than traditional cryptocurrency wallets, as it represents a complete computational environment within the decentralized OS. User may use these State Domain to host decentralized applications, also graphical ones, apps that can be interacted with in real-time, decentralized websites, use these for real-time off the chain transactions and so much more!<\/p>\n
State Domains have several key characteristics:<\/p>\n
\nEach has a unique address derived from a public key<\/li>\n
Can hold tokens and other digital assets<\/li>\n
Functions as a complete operating environment<\/li>\n
Can interact with other State Domains<\/li>\n
Requires cryptographic authorization for operations<\/li>\n<\/ul>\nThe Two-Tier Key Architecture<\/h2>\nGRIDNET implements an innovative two-tier approach to key management:<\/p>\n
Flat Keys (Single-Dimensional)<\/h3>\n\nTraditional one-to-one relationship<\/li>\n
One private key \u2192 one State Domain<\/li>\n
Simpler to understand and manage<\/li>\n
Ideal for single-purpose accounts<\/li>\n
Limited flexibility for managing multiple domains<\/li>\n<\/ul>\nMaster Private Keys (Multi-Dimensional)<\/h3>\n\nOne master key \u2192 many State Domains<\/li>\n
Uses Vector IV system for sub-identity derivation<\/li>\n
More efficient for managing multiple domains<\/li>\n
Built-in support in both Core and Mobile<\/li>\n
Enhanced backup efficiency<\/li>\n<\/ul>\nUnderstanding Vector IV and Sub-Identities<\/h2>\nThe Vector IV system is what makes GRIDNET’s multi-dimensional keys possible. Here’s how it works:<\/p>\n
\nMaster Key Generation<\/strong>\n\nA secure random master private key is generated<\/li>\n
This becomes the root of all sub-identities<\/li>\n<\/ul>\n<\/li>\n
Sub-Identity Derivation<\/strong>\n\nEach sub-identity is derived using the Vector IV value<\/li>\n
Vector IV starts at 0 and can be incremented<\/li>\n
Mathematical formula: Sub-Identity Private Key = Master Private Key + Vector IV<\/li>\n
Each increment creates a new, unique sub-identity<\/li>\n<\/ul>\n<\/li>\n
Key Properties<\/strong>\n\nAll sub-identities are deterministic<\/li>\n
Can be reconstructed from master key<\/li>\n
Each has its own unique address<\/li>\n
Completely isolated from other sub-identities<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nExample using the keychain<\/code> utility:<\/p>\n
# Generate a new master key chain\nkeychain -gen -name masterchain1\n\n# Create first sub-identity (Vector IV = 0)\nkeychain -activate -id 0\n\n# Create next sub-identity (Vector IV = 1)\nkeychain -genid<\/pre>\nIdentity Management in Practice<\/h2>\n
In GRIDNET Core<\/h3>\nCore users (typically miners) can manage identities through the keychain<\/code> utility:<\/p>\n
\nGenerate new key chains<\/li>\n
Store keys in cold storage<\/li>\n
Export keys in various formats<\/li>\n
Manage multiple sub-identities<\/li>\n
Switch between active identities<\/li>\n<\/ul>\nExample of managing identities in Core:<\/p>\n
# Show current identity information\nkeychain -show\n\n# Switch to a different sub-identity\nkeychain -activate -id 2\n\n# Export master key for backup\nkeychain -export -master\n\n# Generate QR code for mobile import\nkeychain -export -qr<\/pre>\nIn GRIDNET Mobile<\/h3>\nMobile app users have a streamlined interface:<\/p>\n
\nSingle master key storage<\/li>\n
Simple identity switching<\/li>\n
Fingerprint security<\/li>\n
QR code import support<\/li>\n
Automatic address generation<\/li>\n<\/ul>\nNavigation:<\/p>\n
\nTap settings wheel (bottom right)<\/li>\n
Access Secret field for key management<\/li>\n
Use fingerprint scanner for security<\/li>\n
Toggle between sub-identities as needed<\/li>\n<\/ol>\nIdentity Isolation and Security<\/h2>\nEach sub-identity, despite coming from the same master key, operates as a completely isolated environment:<\/p>\n
\nSeparate address<\/li>\n
Independent balance<\/li>\n
Distinct transaction history<\/li>\n
Isolated computational state<\/li>\n
Individual access controls<\/li>\n<\/ul>\nThis provides several benefits:<\/p>\n
\nCompartmentalization of assets<\/li>\n
Risk management<\/li>\n
Privacy enhancement<\/li>\n
Organizational flexibility<\/li>\n<\/ul>\nPractical Applications<\/h2>\n\nMining Operations<\/strong>\n\nSeparate mining identity<\/li>\n
Isolated mining rewards<\/li>\n
Independent operational control<\/li>\n<\/ul>\n<\/li>\n
Personal Finance<\/strong>\n\nDifferent identities for different purposes<\/li>\n
Easy switching between accounts<\/li>\n
Unified backup through master key<\/li>\n<\/ul>\n<\/li>\n
Business Operations<\/strong>\n\nSegregated business accounts<\/li>\n
Clear operational boundaries<\/li>\n
Simplified key management<\/li>\n<\/ul>\n<\/li>\n
Development and Testing<\/strong>\n\nIsolated test environments<\/li>\n
Easy creation of new identities<\/li>\n
No risk to main accounts<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nBest Practices for Identity Management<\/h2>\n\nAlways backup master keys<\/li>\n
Use meaningful key chain names in Core<\/li>\n
Document sub-identity purposes<\/li>\n
Regularly verify active identities<\/li>\n
Use fingerprint security in mobile<\/li>\n
Export keys in secure environments<\/li>\n
Maintain clear identity organization<\/li>\n<\/ol>\nGRIDNET Mobile App Key Management<\/h2>\n
Overview<\/h2>\nGRIDNET’s mobile app provides a user-friendly interface for managing both flat and multi-dimensional keys while maintaining robust security. This section explores the complete key management functionality available in the mobile application.<\/p>\n
<\/p>\n
Default Key Generation<\/h2>\nWhen you first launch the GRIDNET mobile app, it automatically generates a Master Private Key (multi-dimensional key). This approach provides several advantages:<\/p>\n
\nSingle key backup requirement<\/li>\n
Built-in support for multiple identities<\/li>\n
Seamless identity switching<\/li>\n
Future-proof key management<\/li>\n<\/ul>\nNavigating the Settings View<\/h2>\nTo access key management features:<\/p>\n
\nLocate the settings wheel icon in the bottom right corner<\/li>\n
Tap to open the Settings view<\/li>\n
The “Secret” field appears at the top<\/li>\n
Additional controls become available after key activation<\/li>\n<\/ol>\nUnderstanding the Secret Field<\/h2>\nThe Secret field is your gateway to key management:<\/p>\n
\nDisplays your active private key<\/li>\n
Accepts both flat and master private keys<\/li>\n
Automatically derives public keys<\/li>\n
Generates corresponding addresses<\/li>\n
Supports manual key entry and QR scanning<\/li>\n<\/ul>\nIdentity Activation Process<\/h2>\n\nKey Entry<\/strong>\n\nEnter private key in Secret field<\/li>\n
Or scan QR code from GRIDNET Core<\/li>\n<\/ul>\n# Generate QR in Core for scanning\nkeychain -export -qr<\/pre>\n<\/li>\nFingerprint Verification<\/strong>\n\nVirtual Fingerprint Scanner appears<\/li>\n
Touch to confirm identity activation<\/li>\n
Provides additional security layer<\/li>\n
Prevents accidental identity changes<\/li>\n<\/ul>\n<\/li>\n
Automatic Processing<\/strong>\n\nPublic key generation<\/li>\n
Address derivation<\/li>\n
Balance checking<\/li>\n
Sub-identity detection<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nManaging Multiple Identities<\/h2>\nOnce a master key is activated, the app provides tools for managing sub-identities:<\/p>\n
Identity Switching<\/h3>\n\nAdditional controls appear after activation<\/li>\n
Seamlessly toggle between sub-identities<\/li>\n
Real-time balance updates<\/li>\n
Automatic address switching<\/li>\n<\/ul>\nSub-Identity Controls<\/h3>\n\nIdentity Index: [0] [1] [2] [3]<\/li>\n
Current Address<\/li>\n
Current Public Key<\/li>\n<\/ul>\nIdentity Tracking<\/h3>\n\nEach sub-identity maintains:\n\nUnique address<\/li>\n
Independent balance<\/li>\n
Separate transaction history<\/li>\n
Individual settings<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nImporting Keys<\/h2>\nThe mobile app supports two key import methods:<\/p>\n
QR Code Import<\/h3>\n\nFrom GRIDNET Core:\n# Export master key as QR\nkeychain -export -master -qr\n\n# Export specific sub-identity\nkeychain -export -id 2 -qr<\/pre>\n<\/li>\nIn mobile app:\n\nTap QR scanner icon<\/li>\n
Center QR code in viewport<\/li>\n
Automatic key detection<\/li>\n
Fingerprint verification required<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nManual Text Import<\/h3>\n\nFrom GRIDNET Core:\n# Export master key as text\nkeychain -export -master\n\n# Export specific sub-identity\nkeychain -export -id 2<\/pre>\n<\/li>\nIn mobile app:\n\nCopy key to Secret field<\/li>\n
Verify fingerprint<\/li>\n
Automatic activation<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nBackup Recommendations<\/h2>\nThe mobile app supports robust key backup strategies:<\/p>\n
Essential Backup Practices<\/h3>\n\nMaster Key Backup<\/strong>\n\nExport master key from Settings<\/li>\n
Store in secure location<\/li>\n
Consider multiple backup copies<\/li>\n
Use offline storage when possible<\/li>\n<\/ul>\n<\/li>\n
Sub-Identity Documentation<\/strong>\n\nRecord active identity indices<\/li>\n
Document identity purposes<\/li>\n
Maintain usage records<\/li>\n
Keep backups updated<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nSecurity Considerations<\/h3>\n\nNever share your Secret<\/li>\n
Use secure channels for key transfer<\/li>\n
Enable device security features<\/li>\n
Regular backup verification<\/li>\n
Consider cold storage solutions<\/li>\n<\/ul>\nCommon Operations<\/h2>\n
Checking Active Identity<\/h3>\n\nOpen Settings<\/li>\n
View current Secret<\/li>\n
Note identity index<\/li>\n
Verify address<\/li>\n<\/ol>\nSwitching Identities<\/h3>\n\nAccess Settings<\/li>\n
Use identity toggles<\/li>\n
Confirm with fingerprint<\/li>\n
Verify new address<\/li>\n<\/ol>\nCreating New Sub-Identity<\/h3>\n\nNavigate to Settings<\/li>\n
Select next available index<\/li>\n
Verify with fingerprint<\/li>\n
Document new identity<\/li>\n<\/ol>\nTroubleshooting<\/h2>\nCommon issues and solutions:<\/p>\n
\nInvalid Key Format<\/strong>\n\nVerify key format<\/li>\n
Check for copy errors<\/li>\n
Try QR import instead<\/li>\n<\/ul>\n<\/li>\n
Failed Activation<\/strong>\n\nRetry fingerprint scan<\/li>\n
Check key validity<\/li>\n
Restart app if needed<\/li>\n<\/ul>\n<\/li>\n
Balance Issues<\/strong>\n\nVerify correct identity<\/li>\n
Check network connection<\/li>\n
Allow sync completion<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nBest Practices<\/h2>\n\nRegular Backups<\/strong>\n\nExport master key periodically<\/li>\n
Store backups securely<\/li>\n
Test backup restoration<\/li>\n<\/ul>\n<\/li>\n
Identity Organization<\/strong>\n\nLabel sub-identities<\/li>\n
Document usage<\/li>\n
Regular verification<\/li>\n<\/ul>\n<\/li>\n
Security Habits<\/strong>\n\nRegular fingerprint checks<\/li>\n
Secure app access<\/li>\n
Private key confidentiality<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nGRIDNET Core Key Management<\/h2>\n
Introduction to the KeyChain Utility<\/h2>\nThe keychain<\/code> utility in GRIDNET Core is the primary tool for managing cryptographic identities. It provides comprehensive functionality for handling both flat and multi-dimensional keys, with powerful features for miners and advanced users.<\/p>\n
Core Concepts and Operations<\/h2>\nKey Storage Architecture<\/h3>\nGRIDNET Core implements a two-tier storage system:<\/p>\n
\nActive Memory (Ephemeral State)<\/strong>\n\nCurrently loaded keys<\/li>\n
Active identities<\/li>\n
Runtime configurations<\/li>\n<\/ul>\n<\/li>\n
Cold Storage (Persistent State)<\/strong>\n\nSaved key chains<\/li>\n
Long-term storage<\/li>\n
Backup configurations<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nBasic Key Management Commands<\/h3>\n
Generating New Key Chains<\/h4>\n# Generate with auto-assigned name\nkeychain -gen\n\n# Generate with custom name\nkeychain -gen -name mining_master\n\n# Generate and immediately store\nkeychain -gen -name mining_master -store<\/pre>\nViewing Key Information<\/h4>\n# Show current key chain\nkeychain -show\n\n# Show including private key\nkeychain -show -priv\n\n# Show specific key chain\nkeychain -show -name mining_master<\/pre>\nManaging Multiple Key Chains<\/h3>\n
Storage Operations<\/h4>\n# Store current key chain\nkeychain -store\n\n# Store with new name\nkeychain -store -name backup_chain\n\n# Store specific identity\nkeychain -store -id 2 -name mining_backup<\/pre>\nActivation Operations<\/h4>\n# Activate stored key chain\nkeychain -activate -name mining_master\n\n# Activate specific sub-identity\nkeychain -activate -id 2\n\n# Generate and activate new sub-identity\nkeychain -genid -activate<\/pre>\nAdvanced Features<\/h2>\n
Sub-Identity Management<\/h3>\n# List all sub-identities\nkeychain -show\n\n# Generate next available identity\nkeychain -genid\n\n# Switch to specific identity\nkeychain -id 3 -activate\n\n# Export specific sub-identity\nkeychain -export -id 2<\/pre>\nExport Operations<\/h3>\n
Text-Based Export<\/h4>\n# Export master key\nkeychain -export -master\n\n# Export current sub-identity\nkeychain -export\n\n# Export named key chain\nkeychain -export -name backup_chain<\/pre>\nQR Code Export<\/h4>\n# Export master key as QR\nkeychain -export -master -qr\n\n# Export sub-identity as QR\nkeychain -export -id 2 -qr\n\n# Export with custom name included\nkeychain -export -qr -named<\/pre>\nKey Chain Naming Conventions<\/h2>\nGRIDNET Core uses a structured naming system:<\/p>\n
\nDefault format: keyX<\/code> (where X is an incremental number)<\/li>\n
Custom names: up to 20 alphanumeric characters<\/li>\n
Case-sensitive<\/li>\n
No special characters allowed<\/li>\n<\/ul>\nExamples:<\/p>\n
# Default names\nkey0, key1, key2\n\n# Custom names\nmining_master\nvalidator_backup\ntest_chain<\/pre>\nPractical Workflows<\/h2>\n
Setting Up Mining Identity<\/h3>\n# Generate new key chain\nkeychain -gen -name mining_master\n\n# Store it\nkeychain -store\n\n# Activate for mining\nkeychain -activate\n\n# Verify active identity\nkeychain -show<\/pre>\nManaging Multiple Mining Identities<\/h3>\n# Generate new sub-identity\nkeychain -genid\n\n# Activate it\nkeychain -activate -id 1\n\n# Export for backup\nkeychain -export -master -name mining_backup<\/pre>\nMobile Integration<\/h3>\n# Export to mobile (QR)\nkeychain -export -master -qr\n\n# Export specific identity (QR)\nkeychain -export -id 2 -qr\n\n# Export text format\nkeychain -export -master<\/pre>\nSecurity Considerations<\/h2>\n
Private Key Protection<\/h3>\n\nUse -priv<\/code> flag carefully<\/li>\n
Secure environment for exports<\/li>\n
Regular backup procedures<\/li>\n
Cold storage best practices<\/li>\n<\/ul>\nIdentity Isolation<\/h3>\n\nSeparate mining identities<\/li>\n
Different chains for different purposes<\/li>\n
Regular verification of active identity<\/li>\n
Clear documentation<\/li>\n<\/ul>\nTroubleshooting Common Issues<\/h2>\nFirst of all worry not. Assets or your account can never disappear just like that. That is impossible. As long as you keep your private keys secure.
\nBelow we outline a couple of methodologies for investigating things and moving around. In short, in GRIDNET OS your ‘wallet’ is a true ‘account’ on a decentralized operating system GRIDNET OS. Which mean you can CD<\/code>\u00a0into your account just as you would on Linux , MacOS, DOS or Windows.<\/p>\n
First you may want to execute the whoami<\/code>\u00a0GridScript command to see if it corresponds to the identity you’ve\u00a0activated with keychain<\/code>:
\n<\/p>\n
whoami<\/code>\u00a0would report all sub-identities associated with your active key-chain along with all corresponding assets, including locked ones. Notce that currently active sub-identity is clearly depicted. That’s the identity which is currently being used for mining\/Operating purposes.<\/p>\n
Next, you may try to CD<\/code>\u00a0into your account, just like so:
\n<\/p>\n
Notice that GRIDNET OS automatically attempts to associate current State Domain with one of private keys available in your currently active key-chain. Here it reports having successfully found a corresponding private key at position 0 in your active Key Chain.<\/p>\n
If on the other hand you attempt CD<\/code>ing into someone else’s account:
\n
\nThat means Core was unable to find a private sub-key which would match the currently active domain. Probably you’ve imported an invalid Mater Private Key or haven’t activated the proper key-chain.<\/p>\n
\nKey Chain Not Found<\/strong>\n# Verify existence\nkeychain -show -name missing_chain\n\n# List available chains\nkeychain -show<\/pre>\n<\/li>\nInvalid Operations<\/strong>\n# Check active chain\nkeychain -show\n\n# Verify permissions\nkeychain -store<\/pre>\n<\/li>\nExport Issues<\/strong>\n# Verify key chain status\nkeychain -show\n\n# Try alternative export format\nkeychain -export -master<\/pre>\n<\/li>\n<\/ol>\nBest Practices<\/h2>\n\nRegular Maintenance<\/strong>\n\nDocument all key chains<\/li>\n
Regular backup exports<\/li>\n
Verify active identities<\/li>\n
Clean up unused chains<\/li>\n<\/ul>\n<\/li>\n
Security Protocols<\/strong>\n\nSecure export environment<\/li>\n
Regular permission checks<\/li>\n
Backup verification<\/li>\n
Access control<\/li>\n<\/ul>\n<\/li>\n
Organization<\/strong>\n\nConsistent naming<\/li>\n
Clear documentation<\/li>\n
Regular audits<\/li>\n
Version control<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nPractical Scenarios with Examples<\/h2>\n
A. Generating New Keys<\/h2>\n
Creating New Key Chains<\/h3>\nThe process of generating new keys in GRIDNET can be done through both Core and Mobile app. Let’s explore each method:<\/p>\n
In GRIDNET Core<\/h4>\n# Basic key generation\nkeychain -gen\n# Named key generation\nkeychain -gen -name mining_main\n# Generate, store, and activate in one command\nkeychain -gen -name mining_main -store -activate<\/pre>\nIn GRIDNET Mobile<\/h4>\n\nClear the Secret field in Settings<\/li>\n
Let the app auto-generate a new master key<\/li>\n
Confirm with fingerprint<\/li>\n
Back up the generated key immediately<\/li>\n<\/ol>\nNaming Conventions<\/h3>\nGRIDNET follows specific naming rules for key chains:<\/p>\n
# Standard auto-generated format\nkey0, key1, key2...\n# Recommended naming patterns\nmining_[purpose]  # e.g., mining_main, mining_backup\nvalidator_[role]  # e.g., validator_primary\ntest_[purpose]   # e.g., test_development<\/pre>\nBest Practices for Names:<\/p>\n
\nMaximum 20 characters<\/li>\n
Alphanumeric only<\/li>\n
Use underscores for readability<\/li>\n
Include purpose in name<\/li>\n
Be consistent across chains<\/li>\n<\/ul>\nStorage and Activation<\/h3>\n# Store newly generated key\nkeychain -store -name mining_primary\n# Verify storage success\nkeychain -show -name mining_primary\n# Activate stored key\nkeychain -activate -name mining_primary\n# Verify active status\nkeychain -show<\/pre>\nB. Managing Multiple Identities<\/h2>\n
Generating Sub-identities<\/h3>\n# Generate next available sub-identity\nkeychain -genid\n# Generate and activate specific index\nkeychain -genid -id 3 -activate\n# Verify new identity\nkeychain -show<\/pre>\nExample workflow for creating mining sub-identities:<\/p>\n
# Start with master chain\nkeychain -gen -name mining_master -store\n# Create mining identity\nkeychain -genid -activate\n# Create backup mining identity\nkeychain -genid -id 2 -store\n# Verify all identities\nkeychain -show<\/pre>\nSwitching Between Identities<\/h3>\n
In Core:<\/h4>\n# Switch to specific identity\nkeychain -activate -id 2\n# Verify active identity\nkeychain -show\n# Switch back to primary\nkeychain -activate -id 0<\/pre>\nIn Mobile:<\/h4>\n\nOpen Settings<\/li>\n
Use identity toggle controls<\/li>\n
Verify address change<\/li>\n
Confirm with fingerprint<\/li>\n<\/ol>\nIdentity Tracking and Organization<\/h3>\nCreate an identity management system:<\/p>\n
\nDocument Structure:\nMaster Chain: mining_master\n\u251c\u2500\u2500 ID 0: Primary Mining (Active)\n\u251c\u2500\u2500 ID 1: Backup Mining\n\u251c\u2500\u2500 ID 2: Test Operations\n\u2514\u2500\u2500 ID 3: Development<\/pre>\n<\/li>\nTracking Commands:\n# Log all identities\nkeychain -show > identity_log.txt\n# Track specific identity\nkeychain -show -id 2 >> identity_log.txt<\/pre>\n<\/li>\nOrganization Tips:\n\nKeep a secure document mapping IDs to purposes<\/li>\n
Regular verification of active identities<\/li>\n
Clear naming conventions for each purpose<\/li>\n
Document all identity changes<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nSample Identity Tracking Sheet:<\/p>\n
Chain: mining_master\nLast Updated: [Date]\nID 0:\n- Purpose: Primary Mining\n- Address: GRD...\n- Last Active: [Date]\nID 1:\n- Purpose: Backup Mining\n- Address: GRD...\n- Last Active: [Date]<\/pre>\n <\/p>\n
Ethereum (EVM) Address Support in GRIDNET OS Keychains<\/h2>\nEach sub-identity in a GRIDNET OS keychain now also reports its corresponding Ethereum (EVM) address<\/strong> (EIP-55 checksum format), derived from the same secp256k1 private key scalar via keccak256 hashing. This means every GRIDNET OS wallet identity has a paired EVM address that can be used on Ethereum, Arbitrum, HyperEVM, and other EVM-compatible chains.<\/p>\n
The EVM address is deterministically derived \u2014 given the same GRIDNET master key, the EVM address at each sub-identity index is always the same, recoverable without storing separately.<\/p>\n
Updated keychain<\/code> Command Behaviour<\/h3>\n\nkeychain -show<\/code> \u2014 displays all sub-identities with both GRIDNET OS address and EVM address (no private keys shown)<\/li>\n
keychain -show -priv<\/code> \u2014 additionally reveals the EVM private key (0x-prefixed hex, 32 bytes), EVM uncompressed public key (0x04-prefixed hex, 65 bytes), and GRIDNET private key (base58)<\/li>\n
keychain -export<\/code> (domain-specific) \u2014 now also outputs EVM address and optionally EVM keys<\/li>\n<\/ul>\nExample Output<\/h3>\n# Show all sub-identities including EVM addresses\nkeychain -show\n\n# Example output:\n# Sub-identity 0:\n#   GRIDNET OS Address : 1BKGXMj441G5iWuQyxS7Bpr4bxr9vAvXWy\n#   EVM Address        : 0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B\n\n# Reveal private key material (handle with care)\nkeychain -show -priv\n\n# Example output (in addition to the above):\n#   GRIDNET Private Key (base58) : DTKUfRptVa8HTX7pjXTNPmvyGbZ...\n#   EVM Private Key (hex)        : 0x18471e3543ebc44b7dc165ae66121e11306b5ad5...\n#   EVM Public Key (uncompressed): 0x04a1b2c3d4e5f6...<\/pre>\nCross-Chain Identity Pairing<\/h3>\nBecause both addresses derive from the same secp256k1 scalar, a single GRIDNET OS keychain effectively controls identities on:<\/p>\n
\nGRIDNET OS<\/strong> \u2014 native L1 address (base58Check format)<\/li>\n
Ethereum mainnet<\/strong> \u2014 same secp256k1 key, EIP-55 checksummed address<\/li>\n
Arbitrum<\/strong> \u2014 EVM-compatible, same address as Ethereum<\/li>\n
HyperEVM (Hyperliquid)<\/strong> \u2014 EVM-compatible, same address as Ethereum<\/li>\n
Any other EVM-compatible chain<\/li>\n<\/ul>\nThis enables seamless cross-chain operations such as the GRIDNET Bridge (GRIDNET OS ↔ Arbitrum ↔ HyperEVM) without requiring separate key management for each chain.<\/p>\n","protected":false},"excerpt":{"rendered":"
Introduction to Public Key Cryptography in GRIDNET Notice: Many GRIDNET OS GridScript commands come with built-in MAN pages. The MAN page of…<\/p>\n","protected":false},"author":1,"featured_media":552851,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[125],"tags":[],"class_list":["post-552817","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-documentation"],"_links":{"self":[{"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/posts\/552817","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/comments?post=552817"}],"version-history":[{"count":18,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/posts\/552817\/revisions"}],"predecessor-version":[{"id":552897,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/posts\/552817\/revisions\/552897"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/media\/552851"}],"wp:attachment":[{"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/media?parent=552817"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/categories?post=552817"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mag.gridnet.org\/index.php\/wp-json\/wp\/v2\/tags?post=552817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

The GRIDNET Innovation: Multi-dimensional Keys
\n $\"\"$ <\/h2>\n
GRIDNET introduces an innovative, in terms of interactive (also supporting autonomous identity switching during mining Operations!) command line management , approach to key management through its multi-dimensional key system:<\/p>\n

GRIDNET Identity System Overview<\/h2>\n

The Two-Tier Key Architecture<\/h2>\n
GRIDNET implements an innovative two-tier approach to key management:<\/p>\n

Identity Management in Practice<\/h2>\n

GRIDNET Mobile App Key Management<\/h2>\n

Overview<\/h2>\n
GRIDNET’s mobile app provides a user-friendly interface for managing both flat and multi-dimensional keys while maintaining robust security. This section explores the complete key management functionality available in the mobile application.<\/p>\n
$\"\"$ <\/p>\n

Managing Multiple Identities<\/h2>\n
Once a master key is activated, the app provides tools for managing sub-identities:<\/p>\n

Importing Keys<\/h2>\n
The mobile app supports two key import methods:<\/p>\n

Backup Recommendations<\/h2>\n
The mobile app supports robust key backup strategies:<\/p>\n

Common Operations<\/h2>\n

GRIDNET Core Key Management<\/h2>\n

Basic Key Management Commands<\/h3>\n

Managing Multiple Key Chains<\/h3>\n

Advanced Features<\/h2>\n

Export Operations<\/h3>\n

Practical Workflows<\/h2>\n

Security Considerations<\/h2>\n

Practical Scenarios with Examples<\/h2>\n

A. Generating New Keys<\/h2>\n

Creating New Key Chains<\/h3>\n
The process of generating new keys in GRIDNET can be done through both Core and Mobile app. Let’s explore each method:<\/p>\n

B. Managing Multiple Identities<\/h2>\n

Switching Between Identities<\/h3>\n

The GRIDNET Innovation: Multi-dimensional Keys\n<\/h2>\nGRIDNET introduces an innovative, in terms of interactive (also supporting autonomous identity switching during mining Operations!) command line management , approach to key management through its multi-dimensional key system:<\/p>\n