{"id":641371,"date":"2025-03-24T07:40:48","date_gmt":"2025-03-24T07:40:48","guid":{"rendered":"https:\/\/gridnet.org\/wpp\/?p=641371"},"modified":"2025-03-24T10:55:09","modified_gmt":"2025-03-24T10:55:09","slug":"deploying-identity-tokens","status":"publish","type":"post","link":"https:\/\/gridnet.org\/wpp\/index.php\/2025\/03\/24\/deploying-identity-tokens\/","title":{"rendered":"Deploying Identity Tokens"},"content":{"rendered":"

Introduction<\/h2>\n

Welcome to the official guide for deploying identity tokens in GRIDNET OS, the world’s first 100% decentralized operating system. This document will walk you through the process of creating your personalized identity token, allowing you to establish a user-friendly nickname instead of using a complex wallet address when interacting with the network. Identity Tokens and their properties can be easily browsed when viewing accounts\/domains in the GRIDNET OS’ Blockchain Explorer UI dApp. In this UI dApp you can also search for accounts by Friendly Names\u00a0associated with Identity Tokens.<\/p>\n

The Rationale Behind Identity Tokens<\/h2>\n

Understanding Identity Token Types<\/h3>\n

In GRIDNET OS, identity tokens are fundamental building blocks that establish your presence in our decentralized ecosystem. Before diving into deployment steps, it’s essential to understand the various types of identity tokens available and why you might choose one over another:<\/p>\n\n\n\n\n\n\n\n\n\n
Token Type<\/th>\nDescription<\/th>\nBest For<\/th>\n<\/tr>\n<\/thead>\n
Basic<\/strong><\/td>\nMinimal functionality with limited features<\/td>\nTesting and development<\/td>\n<\/tr>\n
IdentityOnly<\/strong><\/td>\nProvides identity verification without additional features<\/td>\nPrivacy-focused users<\/td>\n<\/tr>\n
PoW (Proof of Work)<\/strong><\/td>\nRequires computational work rather than financial stake<\/td>\nResource-rich, capital-constrained users<\/td>\n<\/tr>\n
Stake<\/strong><\/td>\nRequires sacrificing GNC cryptocurrency<\/td>\nMost users, provides best rewards<\/td>\n<\/tr>\n
Hybrid<\/strong><\/td>\nCombines both PoW and Stake requirements<\/td>\nMaximum security and reward potential<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

This tutorial focuses on deploying a Stake<\/strong>-based identity token, which requires sacrificing a certain amount of GNC cryptocurrency. This approach is recommended for most users as it provides optimal balance between ease of deployment and network benefits.<\/p>\n

The Role of Stake in Preventing Sybil Attacks<\/h3>\n

Stake-based identity tokens play a crucial role in maintaining GRIDNET OS’s security and reliability. By requiring users to sacrifice GNC cryptocurrency, we create a financial barrier that thwarts Sybil attacks\u2014where malicious actors create multiple fake identities to gain disproportionate influence over the network.<\/p>\n

The stake mechanism ensures that creating numerous identities becomes prohibitively expensive, thereby preserving the integrity of:<\/p>\n

    \n
  1. Voting mechanisms within the ecosystem<\/li>\n
  2. Reputation systems built on top of GRIDNET OS<\/li>\n
  3. Resource allocation algorithms<\/li>\n
  4. Decentralized applications that rely on unique identity verification<\/li>\n<\/ol>\n

    Furthermore, higher stake amounts provide proportionally greater rewards as additional functionalities of GRIDNET OS are unveiled, particularly in the realm of crypto-incentivized, Sybil-proof data transmission protocols.<\/p>\n

    Practical Applications for Daily Users<\/h3>\n

    Beyond security considerations, identity tokens serve several practical purposes that enhance your experience in the GRIDNET OS ecosystem:<\/p>\n

    Embedded Public Keys for Verification<\/h4>\n

    Each identity token contains embedded public keys that enable instant verification of cryptographic signatures. This feature is critical for numerous use cases:<\/p>\n

      \n
    • Decentralized Social Media<\/strong>: When someone deploys a dApp similar to Twitter or Facebook on GRIDNET OS, the authenticity of all posts can be cryptographically verified against your identity token’s public key<\/li>\n
    • Secure Messaging<\/strong>: In decentralized email or messaging applications, recipients can verify both the integrity and authenticity of incoming messages<\/li>\n
    • Document Signing<\/strong>: Any document or content you create can be cryptographically signed and verified against your identity token<\/li>\n
    • Smart Contract Interactions<\/strong>: Automated verification of your identity in contract executions without requiring additional authentication steps<\/li>\n<\/ul>\n

      User-Friendly Domain Names<\/h4>\n

      Perhaps the most immediately apparent benefit is the ability to claim a memorable nickname that serves as your domain within the GRIDNET OS ecosystem:<\/p>\n

        \n
      • Others can browse your decentralized websites by simply visiting your GRIDNET OS domain (e.g., visit HappyDuck<\/code>)<\/li>\n
      • Value transfers can target your nickname instead of complex wallet addresses (e.g., send 5 GNC to HappyDuck<\/code>)<\/li>\n
      • Applications can reference your identity using human-readable names rather than machine-oriented addresses<\/li>\n
      • Your personal data and applications become intuitively accessible under a consistent namespace<\/li>\n<\/ul>\n

        Permanent Ownership<\/h4>\n

        Unlike traditional domain name systems, once registered, your GRIDNET OS domain name (established through your identity token) cannot be taken away from you:<\/p>\n

          \n
        • No renewal fees or subscription costs<\/li>\n
        • No central authority that can revoke or reassign your domain<\/li>\n
        • Truly permissionless ownership secured by cryptographic proofs<\/li>\n
        • Transferable only with your explicit cryptographic authorization<\/li>\n<\/ul>\n

          GRIDNET OS Domains vs. Traditional DNS Domains<\/h3>\n

          When comparing GRIDNET OS domains to traditional DNS domain names, the advantages become clear:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
          Feature<\/th>\nTraditional DNS Domains<\/th>\nGRIDNET OS Domains<\/th>\n<\/tr>\n<\/thead>\n
          Registration Cost<\/strong><\/td>\nInitial purchase fee<\/td>\nOne-time sacrifice (investment)<\/td>\n<\/tr>\n
          Renewal Fee<\/strong><\/td>\nAnnual renewal required<\/td>\nNone \u2013 permanent ownership<\/td>\n<\/tr>\n
          Central Authority<\/strong><\/td>\nICANN and domain registrars<\/td>\nNone \u2013 fully decentralized<\/td>\n<\/tr>\n
          Censorship Risk<\/strong><\/td>\nCan be seized or blocked<\/td>\nCannot be censored or revoked<\/td>\n<\/tr>\n
          Identity Verification<\/strong><\/td>\nOptional, separate process<\/td>\nBuilt-in cryptographic verification<\/td>\n<\/tr>\n
          Transfer Mechanism<\/strong><\/td>\nAdministrative process<\/td>\nCryptographic authorization only<\/td>\n<\/tr>\n
          Resolution Security<\/strong><\/td>\nVulnerable to DNS attacks<\/td>\nCryptographically secure resolution<\/td>\n<\/tr>\n
          Value Integration<\/strong><\/td>\nSeparate from payment systems<\/td>\nDirectly integrated with value transfer<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

          By establishing your identity token early in GRIDNET OS’s evolution, you secure your preferred nickname before others claim it. As the ecosystem grows and more services are built on this foundation, early adopters will benefit from having established recognizable identities in this new decentralized frontier.<\/p>\n

          Understanding GridScript Execution Context<\/h2>\n

          Before deploying your identity token, it’s important to understand how GridScript instructions work in our ecosystem and the critical importance of execution context:<\/p>\n\n\n\n\n\n\n\n\n
          Concept<\/th>\nDescription<\/th>\nImportance<\/th>\n<\/tr>\n<\/thead>\n
          State-Domain<\/strong><\/td>\nThe account-specific context for execution<\/td>\nInstructions are context-dependent and must be executed within the correct State-Domain<\/td>\n<\/tr>\n
          Execution Context<\/strong><\/td>\nThe scope in which GridScript commands operate<\/td>\nGridScript engine needs to know which account is making the sacrifice or deploying tokens<\/td>\n<\/tr>\n
          SSH Access<\/strong><\/td>\nRemote access to decentralized nodes<\/td>\nNo authentication required for SSH access, only for transaction commits<\/td>\n<\/tr>\n
          DUI Access<\/strong><\/td>\nConsole access through graphical Terminal UI dApp<\/td>\nNo authentication required, only for\u00a0operations’\u00a0commits<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

          Execution Types<\/h3>\n\n\n\n\n\n\n
          Execution Type<\/th>\nPurpose<\/th>\nSystem Impact<\/th>\nAuthentication<\/th>\n<\/tr>\n<\/thead>\n
          Ephemeral<\/strong><\/td>\nReal-time commands displayed in terminal or sent as encoded data to apps<\/td>\nNo permanent change to system state<\/td>\nNot required<\/td>\n<\/tr>\n
          Transactional<\/strong><\/td>\nState-changing operations (like token deployment)<\/td>\nPermanent change to decentralized state machine<\/td>\nRequired only at commit time (via mobile app)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

          Transaction Confirmation Workflow<\/h2>\n

          Execution of everything in GRIDNET OS usually boils down to Decentralized Processing Threads. Threads execute GridScript. Execution can be either ephemeral (code can cause computational effects – and data retrieval of data. A great example of this is the Blockchain Explorer UI dApp which invokes Blockchain Explorer JavaScript API. The in-web-browser sub-system of GRIDNET OS then formulated GridScritp instructions which are executed on remote nodes, remote nodes return BER encoded meta-data, which are onion routed and provided to instances of UI dApps).<\/p>\n

          But sometimes, what we call ‘kernel mode’ execution of a Decentralized Processing Thread is needed.<\/p>\n

          In such a case to put it simply – all\u00a0GridScript code needs to be wrapped in a Begin Thread<\/code>\u00a0(BT) and Commit Thread<\/code>\u00a0(CT) code sequence.<\/p>\n

          Such a thread would be executed at full redundancy by the entire network, affecting the entire system,<\/p>\n

          All transactional operations in GRIDNET OS must be confirmed before proceeding to dependent transactions:<\/p>\n

            \n
          1. Initial transaction must be committed and confirmed on the network<\/li>\n
          2. Subsequent dependent transactions must wait for confirmation of prior transactions<\/li>\n
          3. Each transaction requires its own Begin\u00a0Thread\u00a0 (bt) and Commit\u00a0Thread\u00a0(ct) sequenceNote that in nomenclature of GRIDNET OS a ‘transaction’ is similar in its meaning known in relational database system. It not necessarily has anything to do with a value transfer.<\/li>\n<\/ol>\n

            Identity Token Deployment Process
            \n\"\"<\/h2>\n

            Deploying an identity token requires following key steps, each involving specific GridScript commands and proper context management:<\/p>\n

            Step 1: Access Your State-Domain<\/h3>\n\n\n\n\n\n\n
            Command<\/th>\nPurpose<\/th>\nExample<\/th>\nNotes<\/th>\n<\/tr>\n<\/thead>\n
            ssh user@node.gridnet.org<\/code><\/td>\nAccess a decentralized node<\/td>\nssh griduser@node7.gridnet.org<\/code><\/td>\nNo authentication required for SSH access<\/td>\n<\/tr>\n
            cd ~\/account<\/code><\/td>\nEnter your account directory<\/td>\ncd ~\/23ZBwZfGcwSykunTd6<\/code><\/td>\nMust access your specific State-Domain for context<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            Step 2: Make a Sacrifice<\/h3>\n

            The “sacrifice” is a fundamental concept in GRIDNET OS that ensures network integrity by requiring users to dedicate resources.<\/p>\n\n\n\n\n\n\n\n\n\n
            Command<\/th>\nPurpose<\/th>\nExample<\/th>\nNotes<\/th>\n<\/tr>\n<\/thead>\n
            bt<\/code><\/td>\nBegin transaction<\/td>\nbt<\/code><\/td>\nInitiates the sacrifice transaction<\/td>\n<\/tr>\n
            sacrifice <amount><\/code><\/td>\nDedicate GBU to the network<\/td>\nsacrifice 1<\/code><\/td>\nMinimum 1 GBU; higher sacrifices increase trust and potential rewards<\/td>\n<\/tr>\n
            ct<\/code><\/td>\nCommit transaction<\/td>\nct<\/code><\/td>\nGenerates a QR code for authentication<\/td>\n<\/tr>\n
            [Mobile app scan]<\/td>\nAuthenticate and confirm<\/td>\nScan with GRIDNET Token app<\/td>\nGenerates a receipt ID for next step<\/td>\n<\/tr>\n
            [Wait for confirmation]<\/td>\nAllow transaction to be confirmed<\/td>\nCheck status with getstatus<\/code><\/td>\nMust wait for network confirmation before proceeding<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            Example Receipt ID:<\/strong> 43PLVuXvAz8thego8eQtYYEAeXQQddX4Z5CqzvAJLjYWwTRY7K<\/p>\n

            Step 3: Generate the Identity Token<\/h3>\n

            Once your sacrifice transaction is confirmed, you can generate your identity token:<\/p>\n\n\n\n\n\n\n\n\n\n
            Command<\/th>\nPurpose<\/th>\nParameters<\/th>\nExample<\/th>\n<\/tr>\n<\/thead>\n
            bt<\/code><\/td>\nBegin new transaction<\/td>\nbt<\/code><\/td>\nNote: A new bt command is required as this is a separate transaction<\/td>\n<\/tr>\n
            genid<\/code><\/td>\nGenerate identity token<\/td>\n-p<\/code> = public key<br>-f<\/code> = friendly name<br>-r<\/code> = receipt ID<\/td>\ngenid -p 23ZBwZfGcwSykunTd61CGzmkDuXdJTqf4AfBHpkpDXtKcwc7KN -f HappyDuck -r 43PLVuXvAz8thego8eQtYYEAeXQQddX4Z5CqzvAJLjYWwTRY7K<\/code><\/td>\n<\/tr>\n
            ct<\/code><\/td>\nCommit transaction<\/td>\nct<\/code><\/td>\nGenerates a QR code for authentication<\/td>\n<\/tr>\n
            [Mobile app scan]<\/td>\nAuthenticate and confirm<\/td>\nScan with GRIDNET Token app<\/td>\nConfirms token generation<\/td>\n<\/tr>\n
            [Wait for confirmation]<\/td>\nAllow transaction to be confirmed<\/td>\nCheck status with getstatus<\/code><\/td>\nMust wait for network confirmation before proceeding<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            Step 4: Register the Identity Token<\/h3>\n

            After the token generation transaction is confirmed, you must register it on the network:<\/p>\n\n\n\n\n\n\n\n\n\n
            Command<\/th>\nPurpose<\/th>\nNotes<\/th>\n<\/tr>\n<\/thead>\n
            bt<\/code><\/td>\nBegin new transaction<\/td>\nRequired as this is a separate transaction package<\/td>\n<\/tr>\n
            regid<\/code><\/td>\nRegister identity token<\/td>\nMust be committed in a transaction<\/td>\n<\/tr>\n
            ct<\/code><\/td>\nCommit registration<\/td>\nGenerates a QR code for authentication<\/td>\n<\/tr>\n
            [Mobile app scan]<\/td>\nAuthenticate registration<\/td>\nFinal security verification<\/td>\n<\/tr>\n
            [Wait for confirmation]<\/td>\nAllow transaction to be confirmed<\/td>\nCheck status with getstatus<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            Step 5: Synchronize with the Network<\/h3>\n

            After successful registration and confirmation, synchronize your changes with the network:<\/p>\n\n\n\n\n\n\n\n\n
            Command<\/th>\nPurpose<\/th>\nNotes<\/th>\n<\/tr>\n<\/thead>\n
            bt<\/code><\/td>\nBegin new transaction<\/td>\nRequired for sync operation<\/td>\n<\/tr>\n
            sync<\/code><\/td>\nSynchronize with network<\/td>\nUpdates network to reflect your new identity<\/td>\n<\/tr>\n
            ct<\/code><\/td>\nCommit synchronization<\/td>\nGenerates a QR code for authentication<\/td>\n<\/tr>\n
            [Mobile app scan]<\/td>\nAuthenticate synchronization<\/td>\nFinalizes the entire process<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            Complete Deployment Example<\/h2>\n

            Below is a complete script example for deploying the identity token “HappyDuck”, showing the proper sequence of transactions and confirmation waits:<\/p>\n


            \n# Step 1: Access your State-Domain
            \nssh griduser@node7.gridnet.org
            \ncd ~\/23ZBwZfGcwSykunTd6
            \n#
            \n# Step 2: Make a Sacrifice
            \nbt
            \nsacrifice 1
            \nct
            \n# [Scan QR code with mobile app]
            \n# [Wait for transaction confirmation]
            \n# [Receipt ID received: 43PLVuXvAz8thego8eQtYYEAeXQQddX4Z5CqzvAJLjYWwTRY7K]
            \n#
            \n# Step 3: Generate Identity Token
            \nbt
            \ngenid -p 23ZBwZfGcwSykunTd61CGzmkDuXdJTqf4AfBHpkpDXtKcwc7KN -f HappyDuck -r 43PLVuXvAz8thego8eQtYYEAeXQQddX4Z5CqzvAJLjYWwTRY7K
            \nct
            \n# [Scan QR code with mobile app]
            \n# [Wait for transaction confirmation]
            \n#
            \n# Step 4: Register Identity Token
            \nbt
            \nregid
            \nct
            \n# [Scan QR code with mobile app]
            \n# [Wait for transaction confirmation]
            \n#
            \n# Step 5: Synchronize with Network
            \nbt
            \nsync
            \nct
            \n# [Scan QR code with mobile app]<\/code><\/p>\n

             <\/p>\n

            Context-Dependent Execution<\/h2>\n

            <\/code><\/p>\n

            It’s critical to understand that many GridScript instructions are context-dependent. The engine needs to know:<\/p>\n

            <\/code><\/p>\n

              \n
            1. Who<\/strong> is executing the command (which account)<\/li>\n
            2. Where<\/strong> the command is being executed (which State-Domain)<\/li>\n
            3. What<\/strong> prior transactions have been confirmed<\/li>\n<\/ol>\n

              <\/code><\/p>\n

              This is why you must:<\/p>\n

              <\/code><\/p>\n

                \n
              • Always cd<\/code> into your specific account\/State-Domain<\/li>\n
              • Wait for transaction confirmation between dependent operations<\/li>\n
              • Begin each new operation with a fresh bt<\/code> command<\/li>\n<\/ul>\n

                <\/code><\/p>\n

                Mobile App Integration<\/h2>\n

                <\/code><\/p>\n

                The GRIDNET Token mobile app is essential for secure authentication and transaction confirmation. Here’s what you need to know:<\/p>\n

                <\/code><\/p>\n\n\n\n\n\n\n\n\n
                Feature<\/th>\nDescription<\/th>\nBenefit<\/th>\n<\/tr>\n<\/thead>\n
                Wallet Setup<\/td>\nGenerate new private\/public key pair with fingerprint confirmation<\/td>\nSecure key management<\/td>\n<\/tr>\n
                QR Code Scanning<\/td>\nAuthenticate all transactions by scanning QR codes<\/td>\nPrevents unauthorized access<\/td>\n<\/tr>\n
                Balance Reporting<\/td>\nMaintains connection with decentralized VM<\/td>\nReal-time account status<\/td>\n<\/tr>\n
                Transaction History<\/td>\nRecords all confirmed transactions<\/td>\nAudit trail for activities<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                <\/code><\/p>\n

                Advanced Topics<\/h2>\n

                <\/code><\/p>\n

                The Sacrifice Mechanism<\/h3>\n

                <\/code><\/p>\n

                The sacrifice mechanism serves multiple purposes in GRIDNET OS:<\/p>\n

                <\/code><\/p>\n

                  \n
                1. Trust Establishment<\/strong>: Higher sacrifices indicate greater commitment to the network<\/li>\n
                2. Resource Allocation<\/strong>: Ensures fair allocation of system resources<\/li>\n
                3. Reward Potential<\/strong>: Sacrificed GBUs contribute to potential rewards in data exchanges<\/li>\n
                4. Spam Prevention<\/strong>: Deters frivolous identity token creation<\/li>\n<\/ol>\n

                  <\/code><\/p>\n

                  View Transaction Command<\/h3>\n

                  <\/code><\/p>\n

                  For transparency, you can use the vt<\/code> command to view the auto-generated GridScript source code:<\/p>\n

                  \n
                  \n
                  bt
                  \n<\/span>sacrifice 1
                  \n<\/span>vt<\/span><\/code><\/div>\n<\/div>\n<\/div>\n

                  <\/code><\/p>\n

                  This displays the bytecode that will be executed, allowing for verification before commitment.<\/p>\n

                  <\/code><\/p>\n

                  Transaction Confirmation<\/h3>\n

                  <\/code><\/p>\n

                  Transaction confirmation is essential in GRIDNET OS’s decentralized architecture:<\/p>\n

                  <\/code><\/p>\n\n\n\n\n\n\n\n
                  Command<\/th>\nPurpose<\/th>\nExample<\/th>\n<\/tr>\n<\/thead>\n
                  getresult<\/code><\/td>\nCheck transaction status<\/td>\ngetresult\u00a0<tx_id><\/code><\/td>\n<\/tr>\n
                  info<\/code><\/td>\nsee all high-level information associated with an account<\/td>\ninfo<\/code><\/td>\n<\/tr>\n
                  tx<\/code><\/td>\nList all transactions associated with an account (execute while in scope of an account)<\/td>\ntx<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                  <\/code><\/p>\n\n\n\n\n\n\n\n\n\n\n
                  Issue<\/th>\nSolution<\/th>\n<\/tr>\n<\/thead>\n
                  Insufficient Balance<\/td>\nAcquire additional assets<\/td>\n<\/tr>\n
                  Failed Transaction<\/td>\nVerify your network connection and try again<\/td>\n<\/tr>\n
                  Context Errors<\/td>\nEnsure you’re in the correct State-Domain directory<\/td>\n<\/tr>\n
                  Dependency Errors<\/td>\nConfirm previous transactions before proceeding to dependent ones<\/td>\n<\/tr>\n
                  Mobile App Connection Issues<\/td>\nEnsure proper mobile internet connectivity<\/td>\n<\/tr>\n
                  Unrecognized Identity Token<\/td>\nComplete all steps including final sync transaction<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                  <\/code><\/p>\n

                  Conclusion: Claiming Your Place in the Decentralized Revolution<\/h2>\n

                  By deploying your identity token on GRIDNET OS, you’re not merely creating a nickname\u2014you’re staking your claim in humanity’s first truly decentralized digital frontier. This is more than a technical process; it’s your declaration of digital sovereignty.<\/p>\n

                  Beyond Traditional Identity Systems<\/h3>\n

                  For too long, our digital identities have been controlled by centralized authorities who dictate the terms of our online existence. With GRIDNET OS identity tokens, we break these chains once and for all:<\/p>\n

                    \n
                  • True Ownership<\/strong>: Your identity belongs to you alone\u2014not to corporations, not to governments, not to any central authority<\/li>\n
                  • Unstoppable Presence<\/strong>: No entity can erase your existence from the GRIDNET OS ecosystem<\/li>\n
                  • Value Integration<\/strong>: Your identity becomes a direct channel for value exchange without intermediaries<\/li>\n<\/ul>\n

                    Join the Vanguard of Digital Freedom<\/h3>\n

                    Early adopters of revolutionary technologies have always shaped the future. By establishing your identity token today, you position yourself at the forefront of a movement that is redefining how humans interact with technology and each other:<\/p>\n

                      \n
                    • Be among the first to claim your preferred nickname before mass adoption begins<\/li>\n
                    • Establish your presence in what will become the foundation of tomorrow’s decentralized internet<\/li>\n
                    • Participate in building a more equitable, censorship-resistant digital world<\/li>\n<\/ul>\n

                      The Power of Decentralized Identity<\/h3>\n

                      As more applications and services are built on GRIDNET OS, your identity token will become increasingly valuable\u2014not just financially, but functionally. Imagine a world where:<\/p>\n

                        \n
                      • Your online interactions are verified without surveillance<\/li>\n
                      • Your digital assets are truly yours, accessible through your immutable identity<\/li>\n
                      • Your voice cannot be silenced by arbitrary platform policies<\/li>\n<\/ul>\n

                        This isn’t just speculation\u2014it’s the inevitable trajectory of truly decentralized systems. GRIDNET OS is building this future today, and your identity token is your passport to this new reality.<\/p>\n

                        Take Action Now<\/h3>\n

                        Don’t wait for others to claim your digital identity. Follow this guide, deploy your identity token, and take your rightful place in the decentralized revolution. Your future self will thank you for having the foresight to establish your presence at the beginning of this transformative journey.<\/p>\n

                        For those bold enough to see beyond current paradigms, GRIDNET OS isn’t just another platform\u2014it’s the dawn of a new era in human technological progress. Your identity token is both your key and your flag planted firmly in this new territory.<\/p>\n

                        Welcome to true digital freedom.<\/p>\n


                        \n<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"

                        Introduction Welcome to the official guide for deploying identity tokens in GRIDNET OS, the world’s first 100% decentralized operating system. This document will walk you through the process of creating your personalized identity token, allowing you to establish a user-friendly nickname instead of using a complex wallet address when interacting with the network. Identity Tokens […]<\/p>\n","protected":false},"author":1,"featured_media":641518,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[125,10,17],"tags":[],"class_list":["post-641371","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-documentation","category-os-news","category-tutorial"],"_links":{"self":[{"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/posts\/641371","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/comments?post=641371"}],"version-history":[{"count":19,"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/posts\/641371\/revisions"}],"predecessor-version":[{"id":641557,"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/posts\/641371\/revisions\/641557"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/media\/641518"}],"wp:attachment":[{"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/media?parent=641371"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/categories?post=641371"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gridnet.org\/wpp\/index.php\/wp-json\/wp\/v2\/tags?post=641371"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}