# US 12,015,697 B2 · Network topology > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,015,697 B2 - Document ID: US12015697B2 - Status: Granted - Kind: B2 - Application number: 17/708,925 - Filed: 2022-03-30 - Published: 2022-07-14 - Granted: 2024-06-18 - Earliest claimed: 2016-10-03 - Assignees: Visa International Service Association - Applicants: Visa International Service Association - Inventors: Ajith Thekadath; Suman Mukherjee - Web page: https://patentgrep.com/patent/US12015697B2 ## CPC - H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates} - H04L 9/3221: {interactive zero-knowledge proofs} - 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 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)} - H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)} - H04L 63/123: {received data contents, e.g. message integrity} - H04L 63/126: {the source of the received data} - H04W 12/069: using certificates or pre-shared keys - H04W 12/08: Access security - H04W 12/106: Packet or message integrity - G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A network topology is provided that includes multiple data centers for building blockchain blocks. The data centers can process different subgroups of blocks, and then send updates to one another with information about new blocks. Additionally, some data centers may protect sensitive block body information, and instead may only share block headers. ## Claims ### Claim 1 A method comprising: creating, by a first data center computer, a first record in a first database, the first record including a first digital asset and a first record identifier; transmitting, by the first data center computer, a first message to a second data center computer, the first message indicating that the first record was created, the first message including the first record identifier but not the first digital asset, wherein the second data center computer creates a second record in a second database, the second record including the first record identifier and not the first digital asset, and wherein the second data center computer does not receive the first digital asset; receiving, by the first data center computer, a second message from the second data center computer, the second message indicating that a third record was created by the second data center computer, the second message including a third record identifier of the third record but not a second digital asset of the third record, and wherein the first data center computer does not receive the second digital asset; and creating, by the first data center computer, a fourth record in the first database, the fourth record including the third record identifier and not the second digital asset. ### Claim 2 (depends on 1) The method of claim 1, wherein the first record identifier is a first hash, the third record identifier is a third hash, and further comprising: generating, by the first data center computer, the first hash based on the first digital asset, wherein the second data center computer generates the third hash based on the second digital asset and the first hash. ### Claim 3 (depends on 1) The method of claim 1, wherein the first record identifier identifies the first record but does not provide any information about the first digital asset. ### Claim 4 (depends on 1) The method of claim 1, wherein the first digital asset is received only by the first data center computer, and the second digital asset is received only by the second data center computer. ### Claim 5 (depends on 1) The method of claim 1, wherein the first database and the second database have common record identifiers but in different sequences. ### Claim 6 (depends on 1) The method of claim 1, wherein the first database and the second database have a matching set of record identifiers in a matching sequence. ### Claim 7 A first data center computer comprising: a processor; and a non-transitory computer readable medium comprising code executable by the processor, for implementing a method comprising: creating a first record in a first database, the first record including a first digital asset and a first record identifier; transmitting a first message to a second data center computer, the first message indicating that the first record was created, the first message including the first record identifier but not the first digital asset, wherein the second data center computer creates a second record in a second database, the second record including the first record identifier and not the first digital asset, and wherein the second data center computer does not receive the first digital asset; receiving a second message from the second data center computer, the second message indicating that a third record was created by the second data center computer, the second message including a third record identifier of the third record but not a second digital asset of the third record, and wherein the first data center computer does not receive the second digital asset; and creating a fourth record in the first database, the fourth record including the third record identifier and not the second digital asset. ### Claim 8 (depends on 7) The first data center computer of claim 7, wherein the method further comprises: generating, by the first data center computer, the first record identifier based on the first digital asset, wherein the second data center computer generates the third record identifier based on the second digital asset and the first record identifier. ### Claim 9 (depends on 7) The first data center computer of claim 7, wherein the first digital asset comprises information regarding a transfer of value from a sending entity to a recipient entity. ### Claim 10 (depends on 7) The first data center computer of claim 7, further comprising: receiving, by the first data center computer, a first digital asset transfer request comprising the first digital asset, wherein first the digital asset transfer request is received by the first data center computer from a routing computer, wherein the second data center computer received a second digital asset transfer request comprising the second digital asset. ### Claim 11 (depends on 7) The first data center computer of claim 7, wherein the first database includes a first blockchain, the second database includes is a second blockchain, the first record is a first block including a first block header and a first block body, the first block body includes the first digital asset, the first block header includes the first record identifier, the second record is a second block including a second block header, the second block header is the same as the first block header, the third record is a third block including a third block header and a third block body, the third block header includes the third record identifier, the third block body includes the second digital asset, the fourth record is a fourth block including a fourth block header, and the fourth block header is the same as the third block header. ### Claim 12 A method comprising: receiving, by a second data center computer, a first message from a first data center computer, the first message indicating that a first record was created at a first database by the first data center computer, the first message including a first record identifier of the first record but not a first digital asset of the first record, and wherein the second data center computer does not receive the first digital asset; creating, by the second data center computer, a second record in a second database, the second record including the first record identifier and not the first digital asset creating, by the second data center computer, a third record in the second database, the third record including a third record identifier and a second digital asset; and transmitting, by the second data center computer, a second message to the first data center computer, the second message indicating that the third record was created, the second message including the third record identifier of the third record but not the second digital asset of the third record, wherein the first data center computer creates a fourth record in the first database, the fourth record including the third record identifier and not the second digital asset, and wherein the first data center computer does not receive the second digital asset. ### Claim 13 (depends on 12) The method of claim 12, wherein the first data center computer generates the first record identifier based on the first digital asset, and further comprising: generating, by the second data center computer, the third record identifier based on the second digital asset and the first record identifier. ### Claim 14 (depends on 12) The method of claim 12, wherein the first record identifier is a first hash, and the third record identifier is a second hash. ### Claim 15 (depends on 12) The method of claim 12, wherein the first record identifier identifies the first record but does not provide any information about the first digital asset, and the third record identifier identifies the third record but does not provide any information about the second digital asset. ### Claim 16 (depends on 12) The method of claim 12, wherein the first digital asset is received by the first data center computer in a first transfer request, and further comprising: receiving, by the second data center computer from a routing computer, a second transfer request comprising the second digital asset, wherein the second transfer request is not received by the first data center computer, wherein the first database and the second database do not have a matching set of digital assets. ### Claim 17 (depends on 12) The method of claim 12, wherein the first database and the second database have common record identifiers but in different sequences. ### Claim 18 (depends on 12) The method of claim 12, wherein the first database and the second database have a matching set of record identifiers in a matching sequence. ### Claim 19 (depends on 12) The method of claim 12, wherein the first database includes a first blockchain, the second database includes is a second blockchain, the first record is a first block including a first block header and a first block body, the first block body includes the first digital asset, the first block header includes the first record identifier, the second record is a second block including a second block header, the second block header is the same as the first block header, the third record is a third block including a third block header and a third block body, the third block header includes the third record identifier, the third block body includes the second digital asset, the fourth record is a fourth block including a fourth block header, and the fourth block header is the same as the third block header. ### Claim 20 (depends on 12) The method of claim 12, wherein the first digital asset comprises information regarding a first transfer of value from a first sending entity to a first recipient entity, and the second digital asset comprises information regarding a second transfer of value from a second sending entity to a second recipient entity.