# US 12,602,184 B2 · Systems and methods for source chain management with identity-based tokens and enhanced security > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,602,184 B2 - Document ID: US12602184B2 - Status: Granted - Kind: B2 - Application number: 19/079,946 - Filed: 2025-03-14 - Published: 2025-09-18 - Granted: 2026-04-14 - Earliest claimed: 2024-03-16 - Assignees: Vannadium, Inc. - Applicants: Vannadium, Inc. - Inventors: Richard Gilchrist; Randy Krebs; Jonathan Boyd Scott - Web page: https://patentgrep.com/patent/US12602184B2 ## CPC - G06F 3/0655: {Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices} - G06F 3/0604: {Improving or facilitating administration, e.g. storage management} - G06F 3/0671: {In-line storage system} - G06F 21/602: {Providing cryptographic facilities or services} - G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database} - G06Q 20/3825: {Use of electronic signatures} - G06Q 20/3827: {Use of message hashing} - G06Q 20/3829: {involving key management} - G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction} - G06Q 20/401: {Transaction verification} - H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates} - H04L 9/0838: {Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these (network architectures or network communication protocols for key exchange in a packet data network H04L63/061)} - H04L 9/0866: {involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics} - H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage} - H04L 9/32: including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials} - H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)} - H04L 9/3236: {using cryptographic hash functions} - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/3247: {involving digital signatures} - H04L 9/3297: {involving time stamps, e.g. generation of time stamps} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - G06F 2221/2141: Access rights, e.g. capability lists, access control lists, access tables, access matrices - G06Q 2220/00: Business processing using cryptography - H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Systems and methods for source chain management with identity-based tokens and enhanced security are disclosed. A processing system receives input that includes a decentralized identifier (DID) uniquely associated with an entity. The processing system invokes a smart contract deployed on a distributed ledger to mint a non-transferable identity-based token permanently linked to the DID. Metadata generated for the token includes cryptographic references to a hierarchical source chain structure stored in a decentralized data storage system, along with cryptographic verification data. Events associated with the DID are memorialized by appending granular event details, including timestamps, data changes, and origin identifiers, into the hierarchical source chain. Authorized access to event details and tokens is provided via an authenticated interface that securely retrieves and reconstructs encrypted data shards distributed across decentralized nodes, enhancing data security, immutability, and verifiability in decentralized environments. ## Claims ### Claim 1 A computing system, comprising: a processing system comprising one or more processors configured to: receive, from an entity, an input comprising a decentralized identifier (DID) uniquely associated with the entity; invoke a smart contract deployed on a distributed ledger to mint a non-transferable identity-based token linked permanently to the DID, wherein the token cannot be transferred to another DID; generate metadata for the identity-based token comprising: a cryptographic reference to a hierarchical source chain structure stored within a decentralized data storage system; and cryptographic verification data configured to validate integrity of the metadata and the hierarchical source chain structure; store the metadata and a link to the identity-based token in the decentralized data storage system, wherein the decentralized data storage system partitions data into a plurality of encrypted data shards and distributes each encrypted data shard across decentralized storage nodes; memorialize an event associated with the entity by: recording granular event details comprising a timestamp, a comprehensive log documenting specific data changes, and an origin identifier of the event; and appending the granular event details into the hierarchical source chain structure stored within the decentralized data storage system; verify integrity of the hierarchical source chain structure by validating cryptographic links between event records; and provide authorized access through an authenticated interface to reconstruct data from encrypted shards stored in the decentralized data storage system, wherein reconstructing the data from the encrypted shards comprises: retrieving encrypted shards referenced by the metadata from the decentralized storage nodes; decrypting the encrypted shards using one or more decryption keys derived from the DID; reconstructing a data object by assembling at least a subset of the decrypted shards; and presenting the reconstructed data object to authorized entities. ### Claim 2 (depends on 1) The computing system of claim 1, wherein the processing system is further configured to encrypt each data shard using an encryption key uniquely derived from the DID. ### Claim 3 (depends on 1) The computing system of claim 1, wherein cryptographic links between event records are verified using a Merkle tree structure. ### Claim 4 (depends on 1) The computing system of claim 1, wherein the processing system is further configured to embed cryptographically enforceable non-transferability rules directly into the smart contract to prevent unauthorized token transfer. ### Claim 5 (depends on 1) The computing system of claim 1, wherein the processing system is further configured to detect unauthorized attempts to modify the hierarchical source chain structure and automatically generate cryptographically authenticated security anomaly alerts. ### Claim 6 (depends on 1) The computing system of claim 1, wherein the hierarchical source chain structure supports branching structures, each branch representing cryptographically verifiable relationships between parent events and one or more sub-events. ### Claim 7 (depends on 1) The computing system of claim 1, wherein the decentralized data storage system dynamically adjusts data retrieval performance by intelligently routing incoming retrieval requests based upon real-time node availability or network performance metrics. ### Claim 8 (depends on 1) The computing system of claim 1, wherein the processing system is further configured to generate and maintain cryptographically secured audit logs within the metadata for regulatory compliance and transaction verification. ### Claim 9 (depends on 1) The computing system of claim 1, wherein the smart contract enforces predefined conditions for accessing the identity-based token, wherein the predefined conditions are cryptographically linked to the DID. ### Claim 10 (depends on 1) The computing system of claim 1, wherein the decentralized data storage system provides data redundancy by automatically replicating encrypted data shards across geographically dispersed storage nodes. ### Claim 11 (depends on 1) The computing system of claim 1, wherein the processing system is further configured to dynamically adjust physical storage distribution of encrypted data shards based on monitored system usage patterns or real-time decentralized storage node conditions to enhance performance or fault tolerance. ### Claim 12 (depends on 1) The computing system of claim 1, wherein the processing system is further configured to verify cryptographic provenance data associated with the metadata prior to granting access to the hierarchical source chain structure or event details. ### Claim 13 (depends on 1) The computing system of claim 1, wherein the processing system is further configured to generate a graphical visualization of the hierarchical source chain structure for interactive display via an authenticated user interface, wherein the visualization shows cryptographic verification status, timestamped events, and event relationships. ### Claim 14 (depends on 1) The computing system of claim 1, wherein the metadata embedded within the identity-based token includes compliance-related data structured explicitly to satisfy regulatory auditing and verification requirements. ### Claim 15 (depends on 1) The computing system of claim 1, wherein the processing system is further configured to integrate the identity-based token and hierarchical source chain structure with external third-party platforms via an application programming interface (API), enabling secure external access and query-based retrieval. ### Claim 16 (depends on 1) The computing system of claim 1, wherein the decentralized data storage system uses cryptographically enforced access controls restricting the reconstruction and retrieval of encrypted data shards exclusively to entities authorized according to access permissions defined within the smart contract. ### Claim 17 (depends on 1) The computing system of claim 1, wherein the processing system is further configured to implement role-based access control (RBAC) within the authenticated interface, wherein RBAC defines multiple permission levels enabling differentiated access to identity-based tokens and hierarchical event data. ### Claim 18 A computer-implemented method for source chain management with identity-based tokens and enhanced security, the method comprising: receiving, from an entity, an input comprising a decentralized identifier (DID) uniquely associated with the entity; invoking a smart contract deployed on a distributed ledger to mint a non-transferable identity-based token linked permanently to the DID, wherein the token cannot be transferred to another DID; generating metadata for the identity-based token comprising: a cryptographic reference to a hierarchical source chain structure stored within a decentralized data storage system; and cryptographic verification data configured to validate integrity of the metadata and the hierarchical source chain structure; storing the metadata and a link to the identity-based token in the decentralized data storage system, wherein the decentralized data storage system partitions data into a plurality of encrypted data shards, and distributes each encrypted data shard across decentralized storage nodes; memorializing an event associated with the entity by: recording granular event details comprising a timestamp, a comprehensive log documenting specific data changes, and an origin identifier of the event; and appending the granular event details into the hierarchical source chain structure stored within the decentralized data storage system; verifying integrity of the hierarchical source chain structure by validating cryptographic links between event records; and providing authorized access through an authenticated interface to reconstruct data from encrypted shards stored in the decentralized data storage system, wherein reconstructing the data from the encrypted shards comprises: retrieving encrypted shards referenced by the metadata from the decentralized storage nodes; decrypting the encrypted shards using one or more decryption keys derived from the DID; reconstructing a data object by assembling at least a subset of the decrypted shards; and presenting the reconstructed data object to authorized entities. ### Claim 19 (depends on 18) The method of claim 18, further comprising embedding cryptographically enforceable non-transferability rules directly into the smart contract to prevent unauthorized token transfer. ### Claim 20 A non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processing system in a computing device to perform operations for source chain management with identity-based tokens and enhanced security, the operations comprising: receiving, from an entity, an input comprising a decentralized identifier (DID) uniquely associated with the entity; invoking a smart contract deployed on a distributed ledger to mint a non-transferable identity-based token linked permanently to the DID, wherein the token cannot be transferred to another DID; generating metadata for the identity-based token comprising: a cryptographic reference to a hierarchical source chain structure stored within a decentralized data storage system; and cryptographic verification data configured to validate integrity of the metadata and the hierarchical source chain structure; storing the metadata and a link to the identity-based token in the decentralized data storage system, wherein the decentralized data storage system partitions data into a plurality of encrypted data shards, and distributes each encrypted data shard across decentralized storage nodes; memorializing an event associated with the entity by: recording granular event details comprising a timestamp, a comprehensive log documenting specific data changes, and an origin identifier of the event; and appending the granular event details into the hierarchical source chain structure stored within the decentralized data storage system; verifying integrity of the hierarchical source chain structure by validating cryptographic links between event records; and providing authorized access through an authenticated interface to reconstruct data from encrypted shards stored in the decentralized data storage system, wherein reconstructing the data from the encrypted shards comprises: retrieving encrypted shards referenced by the metadata from the decentralized storage nodes; decrypting the encrypted shards using one or more decryption keys derived from the DID; reconstructing a data object by assembling at least a subset of the decrypted shards; and presenting the reconstructed data object to authorized entities.