Dual-Wallet System: Asset Wallet and Data Wallet

NCOG Earth Chain not only enhances the network side of blockchain but also the user side, via its dual-wallet system. The NCOG Wallet application is split into two integrated components: an Asset Wallet and a Data Wallet. This design recognizes that in Web3, users don’t just own tokens – they also may own personal data that they want to control and utilize. By separating asset transactions and data operations, the wallet provides specialized security for each and enables new functionality around private data management in a decentralized context. 

Asset Wallet – Managing Cryptocurrency Assets: The Asset Wallet is the familiar part of a crypto wallet. It: 

• Stores the user’s private ML-DSA87 key for signing blockchain transactions (e.g., transferring $NEC, voting in governance, deploying contracts). 

• Derives the user’s public address, allows creation of multiple addresses/accounts if needed (users can have multiple key pairs for different purposes, and the wallet can handle them under one interface). 

• Signs transactions to be sent to the network. Thanks to PQC, even if an attacker records these, they can’t reverse-engineer the key. 

• Handles typical crypto features: checking balances, viewing transaction history, staking or delegation of $NEC, etc. 

• It keeps the private keys secure, likely encrypted by a passphrase or stored in a secure enclave on the device. Since NCOG uses PQ keys, the wallet might enforce strong passphrases (to protect the somewhat larger keys) or integrate with hardware that supports PQ keys. 

The Asset Wallet’s security model is similar to other non-custodial wallets: the user’s keys never leave their device. But it benefits from NCOG’s PQ security (the keys are immune to quantum attacks) and from the separation from data keys (meaning any vulnerability in data handling does not expose the asset keys, and vice versa). 

Data Wallet – Managing Personal Data: The Data Wallet is an innovative addition that extends the concept of ownership to personal data and digital identity. It can be thought of as a secure vault for any kind of user data, where the user fully controls access. Key aspects include: 

• Encryption Keys: The Data Wallet generates and stores the user’s encryption keys (these could be symmetric keys or a combination of symmetric and ML-KEM public/private keys). For example, it might have a master key pair for the user (PQC-based) and then derive subkeys for various data categories. All these keys are kept safe (never exposed in plaintext outside the wallet, often encrypted at rest with the user’s passphrase or device secure element). 

• Secure Data Storage: Users can encrypt files or pieces of data through the wallet. This could be documents, personal identifiers (like a passport scan), credentials, health records, or even preferences/settings for dApps. The Data Wallet provides an interface to select a file or input data and encrypt it. The encrypted data can then be uploaded or stored anywhere (on the NCOG blockchain, on IPFS, cloud storage, etc.) without privacy concern, because only the user holds the decryption key. 

• Data Sharing with Consent: The powerful feature is that the wallet can selectively share data with dApps or other users in a controlled way. If a decentralized application needs some personal information (say a shipping address for an order, or KYC info for a DeFi service), the dApp can request access from the Data Wallet via an API. The wallet will prompt the user: “App X is requesting your {Email Address}. Allow?” If the user approves, the Data Wallet can either: 

• Decrypt that specific piece of data and send it to the dApp (perhaps encrypted to the dApp’s public key so only the app can read it). 

• Or provide a verifiable claim about the data instead of the raw data (e.g., prove the user is over 18 without revealing birthdate, potentially using zero-knowledge proofs in the future). 

The key point is no personal data leaves the wallet without user consent, and when it does, it’s only the minimum necessary and is encrypted for the recipient. This implements the principle of self-sovereign identity and data privacy by design. 

• Data Usage Logging: The wallet can keep a log of which app accessed what data and when. Users can review and revoke permissions. For instance, if the user previously allowed a certain dApp to fetch their email, the user can later revoke that, and the Data Wallet will refuse future requests from that dApp. 

• Integration with Blockchain Functions: The Data Wallet is integrated with on-chain actions when needed. If a user wants to store data on the blockchain (for permanence or timestamping), the Data Wallet can facilitate encrypting it and then sending an on-chain transaction to store the ciphertext (with a hash on-chain for audit). Or if a smart contract requires some input that is the result of a private computation, the Data Wallet could sign a message or transaction to provide it. NCOG even envisions use cases like a blockchain-based email system – using Data Wallet, a user can send an email to another user by encrypting it to their public key and broadcasting it; only the recipient’s Data Wallet can decrypt it. This is a unique kind of dApp made possible by having encryption keys in every wallet. 

• Key Isolation: The Data Wallet’s keys are distinct from the Asset Wallet’s keys. This means, for example, if an attacker somehow phished the user into signing a transaction with their Asset key, they still cannot access the user’s data because that’s locked by different keys in the Data Wallet. Conversely, if somehow an attacker tricked the user into revealing a piece of data, the asset private key isn’t exposed. This separation of concerns follows the principle of least privilege and minimizes damage from any single compromise. It’s analogous to not keeping your money and your personal documents in the exact same safe – NCOG gives you two safes, each specialized. 

User Experience: From the user’s perspective, the official NCOG Wallet app likely presents these two facets in a unified interface, but under the hood, it treats them differently. For example: 

• When sending tokens, the UI uses the Asset Wallet functions (sign transaction). 

• When a dApp wants data, the UI pops up a Data Wallet consent dialog. 

• The user might have a tab for “My Data” where they can manage stored documents, back them up (in encrypted form), and set which dApps have permission. 

• The Data Wallet could also eventually integrate with identity frameworks (for example, store verifiable credentials like a driver’s license attestation, and sign presentations of those upon request). 

Empowering Developers and Services: For developers, the dual-wallet means they can build dApps that utilize user data without custodianship. For instance: 

• A healthcare dApp can ask the Data Wallet for the user’s medical history that the user previously encrypted from their medical records. The dApp gets it (if allowed) and can display it or include it in an on-chain encrypted form, without any central server storing that history. 

• A DeFi lending dApp could request proof of the user’s income or credit score from the Data Wallet. If the user has that data (maybe provided by an oracle or a credential issuer and stored in Data Wallet), they can share it securely to get better loan terms. 

• An NFT marketplace could use Data Wallet to let artists attach high-resolution original files that only NFT owners can decrypt (the Data Wallet of the owner would hold the decrypt key after purchase). 

All of this reduces the need for external databases and puts users in control, aligning with Web3 ethos. 

Self-Sovereign Identity (SSI): The Data Wallet essentially turns NCOG into a platform for SSI. Users can accumulate verifiable credentials (VCs) and store them encrypted. They can present selective disclosures when needed. The blockchain can serve as a public key registry and timestamp authority for these credentials, while the Data Wallet manages the actual claims. The whitepaper even mentions potential zero-knowledge integrations in the future, meaning the wallet could prove things about user data without revealing it (e.g., prove you have a valid driver’s license without showing the license itself). This would likely leverage the robust cryptography already in place. 

Privacy and Transparency Balance: NCOG’s dual-wallet is careful to not compromise privacy while retaining transparency where needed: 

• On-chain data: remains mostly hashed or encrypted. Personal data is not put in plaintext on-chain unless a user explicitly wants to publish something. 

• On-chain actions: like which Data Wallet operations took place, could be less transparent (because if you send an encrypted message, observers just see random ciphertext). But they know that some message was sent. This is a trade-off: NCOG leans towards user privacy. If needed, users can reveal contents (e.g., in disputes). 

• No central storage: The user is responsible for backing up their Data Wallet (just like their keys). The wallet might offer to back up encrypted data to the user’s cloud in case they lose their device, but it’s all under user encryption. NCOG itself (the network) doesn’t hold your plaintext data – it only might store encrypted forms. So it’s non-custodial for data as well. 

Security of the Wallet App: The wallet app is a crucial piece of the security chain. NCOG will likely provide open-source, audited wallet software with strong device security (e.g., using secure enclaves, biometric locks). Because if the wallet is compromised (malware on user’s phone), both Asset and Data keys could be at risk. Separation helps, but a rooted device could siphon both. Thus, user education and secure app practices are important. Possibly, hardware wallets or HSM integrations will appear for PQ keys as the ecosystem matures, which NCOG can adopt. 

In summary, the Asset & Data Wallet system in NCOG Earth Chain expands the notion of ownership to include data. It gives users full control of their digital identity and assets in one toolkit. This system is a major differentiator for NCOG: 

• It addresses user privacy concerns by design (something many blockchains don’t focus on). 

• It opens new possibilities for applications that need personal data without giving up decentralization. 

• It complements the blockchain’s PQ security by also protecting data with PQ encryption. 

• It enhances security by isolating critical functions. 

For users, it means a more empowering experience: you hold your coins and your data, and you decide how both are used. For organizations, it means they can build on NCOG knowing that user data compliance (e.g., GDPR) can be handled elegantly – data isn’t sitting on their servers, it’s with the user, with clear consent flows. This is a step towards the vision of Web3 where users truly own their digital life.