Method and system for identifying type of account while maintaining anonymity in blockchain transactions

Abstract

A method for account type registration of a blockchain wallet includes receiving, by a receiver of a processing server, a public key of a cryptographic key pair of a blockchain wallet associated with a blockchain; receiving, by a receiver of the processing server, an account identifier of the transaction account; identifying, by a processor of the processing server, an account type of the transaction account; and storing in a data entry at least the public key and an identifier associated with the identified account type.

Description

(19) State Intellectual Property Office (12) Invention Patent Application (10) Application Publication Number (43) Application Publication Date (21) Application Number 202480035997.6 (22) Application Date 2024.05.28 (30) Priority Data 18 / 208,939 2023.06.13 US (85) PCT International Application Entering National Phase Date 2025.11.28 (86) PCT International Application Application Data PCT / US2024 / 031234 2024.05.28 (87) PCT International Application Publication Data WO2024 / 258588 EN 2024.12.19 (71) Applicant Mastercard International Company Address USA (72) Inventors J.S. Kumarwater P.B. Bagoul R. Kanwal (74) Patent Agency China Council for the Promotion of International Trade Patent & Trademark Office Co., Ltd. 11038 Patent Attorney Gao Xin (51) Int.Cl. G06Q 20 / 36 (2012.01) G06Q 20 / 02 (2012.01) G06Q 20 / 38 (2012.01) G06Q 20 / 40 (2012.01) H04L 9 / 32 (2006.01) H04L 9 / 00 (2022.01) (54) Invention Title Method and System for Identifying Account Types While Maintaining Anonymity in Blockchain Transactions (57) Abstract A method for registering account types for a blockchain wallet includes: receiving a public key of a cryptographic key pair of a blockchain wallet associated with the blockchain by a receiver of a processing server; receiving an account identifier of a transaction account by a receiver of a processing server; identifying the account type of the transaction account by a processor of a processing server; and storing at least the public key and the identifier associated with the identified account type in a data entry. Claims (2 pages), Description (13 pages), Drawings (7 pages), CN 121729704 A, 2026.03.24, CN 1 21 72 97 04 A 1. A method for registering account types for a blockchain wallet, comprising: receiving a public key of a cryptographic key pair of a blockchain wallet associated with a blockchain by a receiving device of a processing server; receiving an account identifier of a transaction account by the receiving device of the processing server; identifying an account type of the transaction account by the processing server; and storing at least the public key and an identifier associated with the identified account type in a data entry. 2. The method of claim 1, wherein the data entry is a blockchain data value, and the blockchain data value is stored in a second blockchain separate from the blockchain.3. The method of claim 1, further comprising: identifying one or more sanctions imposed on the transaction account by the processing server, wherein the data entry further includes one or more identifiers associated with the one or more sanctions. 4. The method of claim 3, further comprising: receiving transaction data of a new blockchain transaction by a receiving device of the processing server, the transaction data including at least the public key and a second public key; identifying a second data entry including the second public key by the processing server; and storing at least one of the one or more identifiers in the second data entry by the processing server. 5. The method of claim 4, wherein the new blockchain transaction is subject to the one or more sanctions. 6. The method of claim 4, further comprising: updating the second data entry by the processing server based on the one or more sanctions imposed on the transaction account. 7. The method of claim 4, further comprising: generating transaction notification information by the processing server based on the data of the new blockchain transaction; and transmitting the transaction notification message to a regulatory entity by a transmission device of the processing server. 8. The method of claim 1, further comprising: generating a hash value by the processing server using a one-way hash algorithm to hash the account identifier, wherein the data entry further includes the generated hash value. 9. The method of claim 1, wherein the account identifier is part of a payment account. 10. The method of claim 1, wherein the account type is one of an individual or an entity. 11. A system for registering account types for a blockchain wallet, comprising: a blockchain; and a processing server configured to: receive a public key of a cryptographic key pair of a blockchain wallet associated with the blockchain; receive an account identifier of a transaction account; identify the account type of the transaction account; and store at least the public key and an identifier associated with the identified account type in a data entry. 12. The system of claim 11, wherein the data entry is a blockchain data value, and the blockchain data value is stored in a second blockchain separate from the blockchain. 13. The system of claim 11, wherein the processing server is configured to identify one or more sanctions imposed on the transaction account, and the data entry further includes one or more identifiers associated with the one or more sanctions.14. The system of claim 13, wherein the processing server is configured to: receive transaction data of a new blockchain transaction, the transaction data including at least the public key and a second public key; identify a second data entry including the second public key; and store at least one of the one or more identifiers in the second data entry. 15. The system of claim 14, wherein the new blockchain transaction is subject to the one or more sanctions. 16. The system of claim 14, wherein the new blockchain transaction is subject to the one or more sanctions, and the processing server is configured to reject the new blockchain transaction. 17. The system of claim 14, wherein the new blockchain transaction is subject to the one or more sanctions, the processing server is configured to generate transaction notification information based on data from the new blockchain transaction, and a transmission device of the processing server is configured to transmit the transaction notification message to a regulatory entity. 18. The system of claim 11, wherein the processing server is configured to generate a hash value by hashing the account identifier using a one-way hash algorithm, and the data entry further includes the generated hash value. 19. The system of claim 11, wherein the account identifier is part of a payment account. 20. The system of claim 11, wherein the account type is one of an individual or entity. Claims 2 / 2 Page 3 CN 121729704 A Method and System for Identifying Account Types While Maintaining Anonymity in Blockchain Transactions

[0001] Cross-Reference to Related Applications

[0002] This application claims the benefit and priority of U.S. Provisional Application No. 18 / 208,939, filed June 13, 2023. The entire disclosure of the above application is incorporated herein by reference. Technical Field

[0003] This disclosure relates to, for example, the marking of blockchain accounts associated with individuals or entities, and more specifically, the identification of account types by marking blockchain wallets using associated transaction accounts. Background Art

[0004] Blockchain was initially developed as a way to process transactions and exchange cryptocurrencies using a system that has both decentralization and anonymity. The decentralization of blockchain networks can provide great difficulty in controlling the blockchain or enabling fraudulent transactions to be successfully confirmed and added to the blockchain. Because blockchain transfers currency between wallets without requiring any proof of identity from the wallet owner, blockchain transactions can traditionally be conducted between two anonymous parties. These advantages over traditional transaction systems using fiat currency have led to a degree of popularity for cryptocurrencies using blockchain transactions.

[0005] The anonymity of blockchain wallet ownership allows individuals or entities to participate in transactions without providing proof of identity.In some cases, individuals or entities may be subject to sanctions imposed by regulatory bodies such as governments, payment processors, or other entities. The anonymity of blockchain wallets may allow individuals or entities subject to such sanctions to freely transact on the blockchain without recourse. Therefore, there is a need for technical solutions to identify the account type of a blockchain wallet for regulatory purposes without sacrificing anonymity. Summary of the Invention

[0006] This disclosure provides a description of a system and method for registering account types for blockchain wallets. When a blockchain wallet is registered, the owner provides a portion of a transaction account for a transaction account issued to the owner. This portion of the transaction account is used to identify the account type, such as ownership of an individual or entity. The blockchain wallet is marked for the identified account type in a data entry, which may be stored in a lookup table or a sidechain of the relevant blockchain. This mark can then be used in future transactions for purposes such as ensuring compliance with applicable regulations. In cases where an individual or entity may be subject to sanctions, a portion of the transaction account can be used to identify such sanctions, wherein an associated mark can be stored together with an account type mark for use in ensuring compliance with such sanctions in future blockchain transactions. Therefore, individuals or entities can remain compliant without providing proof of identity, thereby maintaining the anonymity provided by the blockchain.

[0007] The currency according to this disclosure is legal tender, and the cryptocurrency according to this disclosure is legal cryptocurrency.

[0008] A method for registering account types for a blockchain wallet includes: receiving, by a receiver of a processing server, a public key of a cryptographic key pair of a blockchain wallet associated with the blockchain; receiving, by the receiver of the processing server, an account identifier of a transaction account; identifying, by a processor of the processing server, an account type of the transaction account; and storing, in a data entry, at least the public key and an identifier associated with the identified account type.

[0009] A system for registering account types for a blockchain wallet includes: a blockchain; and a processing server, the server including a receiver and a processor, the receiver receiving, the public key of a cryptographic key pair of a blockchain wallet associated with the blockchain and an account identifier of a transaction account, the processor identifying, the account type of the transaction account, and storing, in a data entry, at least the public key and an identifier associated with the identified account type.

[0010] The scope of this disclosure will be best understood from the following detailed description of exemplary embodiments when read in conjunction with the accompanying drawings. The drawings include the following figures:

[0011] FIG1 illustrates a block diagram of an advanced system architecture for account type registration for a blockchain wallet according to an exemplary embodiment.

[0012] FIG2 illustrates a block diagram of a processing server in the system of FIG1 for account type registration for a blockchain wallet according to an exemplary embodiment.

[0013] Figures 3A and 3B illustrate flowcharts of a process for registering account types for a blockchain wallet in the system of Figure 1 according to an exemplary embodiment.

[0014] Figure 4 illustrates a flowchart of a process for determining whether a blockchain transaction is subject to one or more sanctions in system 100 according to an exemplary embodiment.

[0015] Figure 5 illustrates a flowchart of an exemplary method for registering account types for a blockchain wallet according to an exemplary embodiment.

[0016] Figure 6 illustrates a block diagram of a computer system architecture according to an exemplary embodiment.

[0017] Further applicability of this disclosure will become clear from the detailed description provided below. It should be understood that the detailed description of exemplary embodiments is intended for illustrative purposes only and is therefore not intended to necessarily limit the scope of this disclosure. Detailed Description

[0018] System for Registering Account Types for Blockchain Wallets

[0019] Figure 1 illustrates a system 100 for registering account types for blockchain wallets, where blockchain wallets may be tagged accordingly for regulatory purposes and to comply with applicable sanctions. System 100 may include a processing server 102. The processing server 102, which will be discussed in more detail below, can be configured to register account types for blockchain wallets and identify and manage tokens used for account types and imposed sanctions.

[0020] System 100 may also include a blockchain network 104. Blockchain network 104 may include multiple blockchain nodes 106. Each blockchain node 106 may be a computer system, as shown in FIG. 5, which will be discussed in more detail below, and is configured to perform functions related to the processing and management of the blockchain, including generating blockchain data values, verifying proposed blockchain transactions, verifying digital signatures, generating new blocks, verifying new blocks, and maintaining a copy of the blockchain. In some embodiments, the processing server 102 may be a blockchain node 106.

[0021] The blockchain may be a distributed ledger that includes at least multiple blocks. Each block may include at least a block header and one or more data values. Each block header may include at least a timestamp, a block reference value, and a data reference value. The timestamp may be the time when the block header was generated and may be represented using any suitable method (e.g., UNIX timestamp, DateTime, etc.). A block reference value can be a value that references an earlier block in the blockchain (e.g., based on a timestamp). In some embodiments, a block reference value in the block header can be a reference to the block header of the most recently added block preceding the corresponding block. In an exemplary embodiment, a block reference value can be a hash value generated by hashing the block header of the most recently added block. Similarly, a data reference value can be a reference to one or more data values ​​stored in a block that includes a block header.In an exemplary embodiment, the data reference value may be a hash value generated by hashing one or more data values. For example, the block reference value may be the root of a Merkle tree generated using one or more data values.

[0022] Using block reference values ​​and data reference values ​​in each block header can make the blockchain immutable. Any attempt to modify a data value would require generating a new data reference value for that block, which would require generating new block reference values ​​for subsequent blocks, further requiring the generation of new block reference values ​​in each subsequent block. This needs to be performed and updated in each individual blockchain node 106 in the blockchain network 104 before generating a new block and adding a new block to the blockchain, so that the change becomes permanent. Computational and communication constraints can make such modifications extremely difficult (if not impossible), thus making the blockchain immutable.

[0023] In some embodiments, the blockchain may be used to store information about blockchain transactions conducted between two different blockchain wallets. A blockchain wallet may include the private key of a cryptographic key pair, which is used to generate a digital signature authorizing a payment for a blockchain transaction, wherein the digital signature can be verified by the blockchain network 104 using the public key of the cryptographic key pair. In some cases, the term "blockchain wallet" may specifically refer to the private key. In other cases, the term "blockchain wallet" may refer to a computing device (e.g., computing device 108, etc.) that stores the private key for use in blockchain transactions. For example, each computing device may have its own private key for the corresponding cryptographic key pair and may act as a blockchain wallet for transactions on the blockchain associated with the blockchain network. The computing device may be any type of device suitable for storing and using a blockchain wallet, such as a desktop computer, laptop, notebook computer, tablet computer, cellular phone, smartphone, smartwatch, smart TV, wearable computing device, implantable computing device, etc.

[0024] Where applicable, each blockchain data value stored in the blockchain may correspond to a blockchain transaction or other data storage. A blockchain transaction may include at least: a digital signature of the sender of the currency (e.g., computing device 108) generated using the sender's private key; a blockchain address of the recipient of the currency (e.g., another computing device 108) generated using the recipient's public key; and the amount of blockchain currency transferred or other data being stored. In some blockchain transactions, the transaction may also include one or more blockchain addresses of the sender currently storing the blockchain currency (e.g., a digital signature proving its access to such currency), and an address generated using the sender's public key for any changes retained by the sender.The address to which cryptocurrency that can be used in future transactions has been sent is called an "output" address because each address was previously used to capture the output of previous blockchain transactions; it is also called an "unused transaction" because currency was sent to that address in a previous transaction and that currency has not yet been used. In some cases, blockchain transactions may also include the sender's public key, which the entity uses to verify the transaction. For conventional processing of blockchain transactions, such data can be provided by the sender or receiver to the blockchain node 106 in the blockchain network 104. The node can use the public key in the sender's wallet's cryptographic key pair to verify the digital signature and also to verify the sender's access to the funds (e.g., unused transactions have not been spent and were sent to an address associated with the sender's wallet). This process is called "confirmation" of the transaction, and the blockchain transaction is then included in a new block. In conventional blockchain implementations, a new block can be verified by the other blockchain nodes 106 in the blockchain network 104 before being added to the blockchain and distributed to all blockchain nodes 106 in the blockchain network 104. Even when blockchain data values ​​cannot be associated with blockchain transactions but are associated with other types of data storage, the blockchain data values ​​may still include or otherwise involve the verification of digital signatures.

[0025] In system 100, computing device 108 may create new blockchain wallets for use with the blockchain associated with blockchain network 104. The blockchain wallets may be used by computing device 108 to receive or transfer cryptocurrency or other value transferred via the blockchain or otherwise retained in ownership. In system 100, any transactions involving a user, such as those conducted using a new blockchain wallet, may be subject to one or more regulations established by one or more regulatory entities 112. Regulatory entity 112 may be any entity that establishes regulations concerning the transfer or use of cryptocurrency, participation in blockchain transactions, or other regulations that may affect users participating in the blockchain associated with blockchain network 104. Examples of regulatory entities 112 may include, for example, governments, financial institutions, law enforcement agencies, standards organizations, etc. In an exemplary embodiment, regulatory entity 112 may impose one or more regulations applicable to blockchain transactions depending on whether the participants in the transaction are individuals or entities.

[0026] To identify the account type of a user of a new blockchain account, the processing server 102 may utilize a transaction account issued to the user. In system 100, users of computing device 108 may have transaction accounts pre-issued by issuing institution 110. Issuing institution 110 may be any entity that issues transaction accounts to users for use when sending or receiving currency, including fiat currencies such as credit card accounts, lending accounts, etc.Issuing institution 110 may be a financial institution such as an issuing bank or other suitable entity. As part of creating a transaction account, the user may provide proof of identity to issuing institution 110, which enables issuing institution 110 to identify whether the user is an individual or an entity, and in some cases, to identify a more specific type of individual or entity. Issuing institution 110 may issue a transaction account to computer device 108 and, as part of issuing the transaction account, generate and issue a transaction account number, also known as a payment account, uniquely associated with the transaction account.

[0027] When computing device 108 creates a new blockchain account, computing device 108 may register the new blockchain account with processing server 102. For registration, computing device 108 may provide an identifier associated with the new blockchain account and at least a portion of the transaction account number. The identifier may be a public key or other value unique to the new blockchain account and may be used for its identification. A portion of the transaction account number may include the first four digits of the transaction account number, or other portions that may be used by processing server 102 to identify the account type of computing device 108, as described below. Computing device 108 may use any suitable communication network and method to provide registration data to processing server 102. For example, computing device 108 may submit data to processing server 102 via a webpage or an application that transmits data directly to processing server 102, such as via the Internet.

[0028] Processing server 102 may receive registration data and may use a portion of the transaction account to identify the account type of a new blockchain account, wherein the account type may be an individual or an entity, indicating whether the user operating, owning, or otherwise associated with the new blockchain account is an individual or an entity. For example, an individual account type indicates that the blockchain account is an individual blockchain account owned by an entity, while an entity account type indicates that the blockchain account is operated by one or more users on behalf of an entity such as a business, company, organization, government, etc. In some embodiments, processing server 102 may use any suitable communication network and method to electronically transmit a portion of the transaction account to issuing authority 110, wherein issuing authority 110 may identify the account type of the associated transaction account and provide the account type back to processing server 102. In other embodiments, a portion of the transaction account may indicate the account type of computing device 108. For example, when the transaction account is issued for a user of computing device 108, issuing authority 110 may identify the user's account type and provide the transaction account such that the account type is reflected in the transaction account. For example, one or more digits, letters, and / or symbols in a transaction account can reflect the user's account type, such as a "4" in the fifth position indicating an individual, while a "5" in the fifth position indicates an entity. In such embodiments, the processing server 102 can identify the user's account type for a new blockchain wallet by recognizing values ​​in appropriate positions within a portion of the transaction account.As another example, a specific pattern of alphanumeric characters and / or symbols within a transaction account can indicate the account type. In this embodiment, processing server 102 can identify the account type of a user of a new blockchain wallet by recognizing a pattern of alphanumeric characters and / or symbols in a portion of the transaction account. In other embodiments, computing device 108 can submit the account type indication along with registration data to processing server 102. In such embodiments, processing server can use any suitable communication network and method to electronically transmit the account type indication along with a portion of the transaction account to issuing institution 110, where issuing institution 110 can confirm and / or correct the account type of the associated transaction account and provide the confirmed and / or correct account type back to processing server 102.

[0029] Once the account type of the new blockchain wallet is identified, processing server 102 can accordingly tag the new blockchain wallet. This tag indicates the account type of the new blockchain wallet. The tag can be stored in a location such that it can be accessed as needed, such as when attempting a new blockchain transaction involving the new blockchain wallet as a participant. In some embodiments, the processing server 102 may store a tag in a data entry that also includes the public key of the new blockchain wallet in a lookup table, such as in the storage or database of the processing server 102, which may be stored in any suitable system-accessible storage. In other embodiments, a sidechain may be used, which may be separate from but associated with the blockchain and operated by the blockchain network 104 or a separate blockchain network 104. In such embodiments, the public key and account type tag may be stored in a new blockchain data entry added to the sidechain using conventional systems and methods. In embodiments using a lookup table, the tag stored in the data entry in the lookup table may be updated if the account type of the new blockchain wallet changes. In a later embodiment, when the account type of the blockchain wallet changes, a new blockchain data entry may be added to the sidechain including the updated tag and public key, the latest blockchain data entry including the public key being available to identify the current account type of the new blockchain wallet.

[0030] When a blockchain node 106 in the blockchain network 104 receives a new blockchain transaction that includes the new blockchain wallet as a participant, the blockchain node 106 may identify the account type tag of the new blockchain wallet in the sidechain or lookup table. Blockchain node 106 can then ensure that the new blockchain transaction complies with any applicable regulations based on the account type. For example, if an individual is restricted to a maximum transaction amount, then during the confirmation process of a new blockchain transaction, if the account type flag of the new blockchain wallet indicates that the user is an individual, blockchain node 106 can ensure that the transaction amount of the new blockchain transaction is within the maximum amount.Therefore, compliance with applicable regulations based on account type can be ensured without directly identifying the user of the new blockchain wallet or obtaining the full transaction account.

[0031] In some embodiments, the tag can be used to ensure compliance with any sanctions imposed on participants in the blockchain associated with blockchain network 104. In such embodiments, processing server 102 can identify when sanctions have been imposed on the blockchain wallet. In some cases, when sanctions are imposed or when the sanctions status changes, regulatory entity 112 or other entity imposing sanctions can electronically transmit data about sanctions and the identifier of the blockchain wallet to processing server 102. In other cases, processing server 102 can request sanctions data of the blockchain wallet from regulatory entity 112 or other entity imposing sanctions, such as by providing the public key of the blockchain wallet and receiving sanctions data in response. In some cases, a portion of the transaction account can be used to identify the user of the blockchain wallet for identifying any sanctions that will be applied to the blockchain wallet or transactions involving the blockchain wallet.

[0032] Once sanctions data is received, processing server 102 can identify and / or generate one or more sanctions tags to ensure compliance with sanctions and store one or more sanctions tags in the data entries of the blockchain wallet in a lookup table or sidechain. Sanctions markers can then be used in future blockchain transactions involving a blockchain wallet as a participant. For example, blockchain node 106 can identify all sanctions markers in the latest data entries of the blockchain wallet of computing device 108 and ensure compliance with the identified sanctions markers in new blockchain transactions involving the blockchain wallet of computing device 108. In some cases, sanctions may restrict transaction amounts, transaction participants, transaction frequency, transaction time and / or transaction dates, or may require reporting of transaction activity, wherein blockchain node 106 or processing server 102 can ensure such reporting based on sanctions markers to comply with applicable sanctions.

[0033] In some embodiments, if a blockchain wallet participates in a blockchain transaction with another blockchain wallet that has one or more sanctions markers, the blockchain wallet may be marked for its relationship with the blockchain wallet that has one or more sanctions markers. For example, if an unsanctioned blockchain wallet receives cryptocurrency from a sanctioned blockchain wallet, the unsanctioned blockchain wallet may be marked for transaction reporting, such as to monitor the unsanctioned blockchain wallet's participation in potentially unauthorized activities. Specification page 5 / 13 8 CN 121729704 A

[0034] In some embodiments, hashed transaction accounts can be identified using the methods discussed above. For example, computing device 108 can hash transaction accounts issued by issuing institution 110 to its users, for example, instead of transmitting a portion of the transaction account to processing server 102.The resulting hash value can be transmitted to processing server 102 to identify the account type and any applicable sanctions, in order to identify the appropriate token in the data entry where the public key of the blockchain wallet to be stored in computing device 108 is located. In an exemplary embodiment, a one-way hash algorithm such as Message Digest 5 (MD5) and Secure Hash Algorithms (SHA) 1 and 2, as two examples, can be used to make the transaction account unobtainable from the hash value. In such cases, processing server 102 can use the hashed transaction account without obtaining or using the actual transaction account, thereby maintaining the anonymity of the user of computing device 108. Issuing authority 110 and regulatory entity 112 can hash the transaction account themselves using the same one-way hash algorithm. Thus, processing server 102 can use the hashed transaction account to request account type data or sanctions data, wherein issuing authority 110 and regulatory entity 112 may use the hash value to identify the account type or sanctions data as appropriate.

[0035] The methods and systems discussed herein provide account type registration for blockchain wallets. By identifying account types and storing appropriate tags in sidechains or lookup tables, blockchain wallets can comply with any applicable regulations in future blockchain transactions or other activities. Account type tags can be identified and established using only a portion of the transaction account without identifying users of new blockchain wallets, enabling proactive compliance without sacrificing the anonymity traditionally provided by blockchains. Therefore, additional functionality can be introduced into blockchains without compromising their existing advantages.

[0036] Processing Server

[0037] Figure 2 illustrates an embodiment of the processing server 102 in the system 100 of Figure 1. It will be clear to those skilled in the art that the embodiment of the processing server 102 illustrated in Figure 2 is provided as an example only and is not an exhaustive list of all possible configurations of the processing server 102 that perform the functions discussed herein. For example, the computer system 500 illustrated in Figure 5 and discussed in more detail below may be a suitable configuration for the processing server 102. In some cases, other components of system 100, such as blockchain node 106, computing device 108, issuing authority 110, and regulatory entity 112, may include the components shown in Figure 2 and discussed below.

[0038] The processing server 102 may include a receiving device 202. The receiving device 202 may be configured to receive data on one or more networks via one or more network protocols. In some cases, the receiving device 202 may be configured to receive data from the blockchain node 106, computing device 108, issuing authority 110, regulatory entity 112 and other systems and entities via one or more communication methods such as radio frequency, local area network, wireless local area network, cellular communication network, Bluetooth, Internet, etc.In some embodiments, receiving device 202 may include multiple devices, such as different receiving devices for receiving data on different networks, such as a first receiving device for receiving data via a local area network and a second receiving device for receiving data via the Internet. Receiving device 202 may receive electronically transmitted data signals, wherein data may be superimposed or otherwise encoded on the data signals, and obtain the data signals by decoding, parsing, reading, or other methods. In some cases, receiving device 202 may include a parsing module for parsing the received data signals to obtain the data superimposed thereon. For example, receiving device 202 may include a parser program configured to receive the received data signals and convert them into usable inputs executed by a processing device for implementing the functions of the methods and systems described herein.

[0039] Receiving device 202 may be configured to receive data signals electronically transmitted by blockchain node 106, which may be superimposed or otherwise encoded with blockchain data entries, blockchain transactions, public keys, account tagging requests, etc. The receiving device 202 may also be configured to receive data signals electronically transmitted by the computing device 108, which may be superimposed or otherwise encoded with registration data such as new blockchain wallets, public keys, portions of transaction accounts, hashed transaction accounts, new blockchain transactions, etc. The receiving device 202 may also be configured to receive data signals electronically transmitted by the issuing authority 110 and / or regulatory entity 112, which may be superimposed or otherwise encoded with account type data, sanctions data, sanctions updates, etc.

[0040] The processing server 102 may also include a communication module 204. The communication module 204 may be configured to transfer data between modules, engines, databases, memory, and other components of the processing server 102 for use in performing the functions discussed herein. The communication module 204 may be comprised of, include, one or more communication types, and utilize various communication methods for communication within the computing device. For example, the communication module 204 may include a bus, contact pin connectors, wires, etc. In some embodiments, the communication module 204 may also be configured to communicate between internal components of the processing server 102 and external components such as externally connected databases, display devices, input devices, etc. The processing server 102 may also include a processing device. The processing device may be configured to perform the functions of the processing server 102 discussed herein, as will be apparent to those skilled in the art. In some embodiments, the processing device may include a plurality of engines and / or modules specifically configured to perform one or more functions of the processing device, and / or consist of a plurality of engines and / or modules specifically configured to perform one or more functions of the processing device, such as a query module 216, a generation module 218, a verification module 220, etc.As used herein, the term "module" can be software or hardware specifically programmed to receive input, perform one or more processes using the input, and provide output. Based on this disclosure, the inputs, outputs, and processes performed by various modules will be apparent to those skilled in the art.

[0041] The processing server 102 may also include an account database 206. The account database 206 may be configured to store one or more account profiles 208 using a suitable data storage format and schema. The account database 206 may be a relational database that utilizes a structured query language to store, identify, modify, update, access, etc., structured datasets stored therein. Each account profile 208 may be a structured dataset configured to store data associated with a blockchain wallet. The account profile 208 may include, for example, the public key of the cryptographic key pair of the associated blockchain wallet, account type flags and one or more sanctions flags (if applicable), a portion of the transaction account number, a hashed transaction account number, etc. In some embodiments, the account database 206 may be a lookup table accessible to the processing server 102 and one or more systems outside the processing server 102, such as a blockchain node 106, a regulatory entity 112, etc. In some embodiments, the account database 206 may be a sidechain that can be accessed by the processing server 102 and one or more systems outside the processing server 102, such as blockchain node 106, regulatory entity 112, etc.

[0042] The processing server 102 may also include blockchain data 210. Blockchain data 210 may include any data entry 212 associated with the blockchain network 104, such as a copy of the blockchain associated with the blockchain network 104, and / or data associated with a sidechain, such as the account database 206 as described above.

[0043] The processing server 102 may also include a memory 214. The memory 214 may be configured to store data for use by the processing server 102 when performing functions discussed herein, such as public and private keys, symmetric keys, etc. The memory 214 may be configured to store data using suitable data formatting methods and patterns, and may be any suitable type of memory such as read-only memory, random access memory, etc. The memory 214 may include, for example, cryptographic keys and algorithms, communication protocols and standards, data formatting standards and protocols, program code for modules and applications for processing devices, and other data, as will be clear to those skilled in the art, suitable for processing server 102 in performing the functions disclosed herein. In some embodiments, the memory 214 may consist of or otherwise include a relational database, which utilizes a structured query language to store, identify, modify, update, access, etc., structured datasets stored therein.The memory 214 may be configured to store, for example, cryptographic keys, cryptographic key pairs, cryptographic algorithms, encryption algorithms, communication information, data formatting rules, network identifiers, transaction history, blockchain wallet data, account tag data, sanctions data, etc.

[0044] The processing server 102 may include a query module 216. The query module 216 may be configured to perform a query on a database to identify information. The query module 216 may receive one or more data values ​​or query strings and may perform the query string on a specified database, such as the account database 206 of the processing server 102, based on them to identify the information stored therein. The query module 216 may then output the identified information to the appropriate engine or module of the processing server 102 as needed. For example, the query module 216 may perform a query on the account database 206 to identify the account profile 208 associated with the blockchain wallet of the new blockchain transaction to identify the tags stored therein for the new blockchain transaction.

[0045] The processing server 102 may also include a generation module 218. The generation module 218 may be configured to generate data for use by the processing server 102 when performing the functions discussed herein. The generation module 218 may receive instructions as input, generate data based on the instructions, and output the generated data to one or more modules of the processing server 102. For example, the generation module 218 may be configured to generate data messages, notification messages, data entries, blockchain data entries, sanctions messages, transaction reports, etc. For example, the processing server 102 may generate a transaction notification message for a received blockchain transaction to a regulatory entity 112 and / or an issuing authority 110, wherein one or more blockchain accounts involved in the blockchain transaction are subject to one or more sanctions.

[0046] The processing server 102 may also include a verification module 220. The verification module 220 may be configured to perform verification for the processing server 102 as part of the functions discussed herein. The verification module 220 may receive instructions as input (which may also include data to be used when performing verification), perform the requested verification, and output the verification results to other modules or engines of the processing server. For example, verification module 220 may be configured to verify compliance with applicable sanctions as a result of account type and / or sanction markers. Processing server 102 may approve or reject blockchain transactions based on the verification results. For example, if a blockchain transaction includes a transaction account subject to one or more sanctions, and the blockchain transaction does not comply with one or more sanctions, processing server 102 may reject the blockchain transaction or otherwise prevent the blockchain transaction from being submitted to blockchain network 104 for confirmation.

[0047] Processing server 102 may also include transmission device 222. Transmission device 222 may be configured to transmit data over one or more networks via one or more network protocols.In some cases, transmission device 222 may be configured to transmit data to blockchain node 106, computing device 108, issuing authority 110, regulatory entity 112, and other entities via one or more communication methods, local area network, wireless local area network, cellular communication, Bluetooth, radio frequency, Internet, etc. In some embodiments, transmission device 222 may include multiple devices, such as different transmission devices for transmitting data on different networks, such as a first transmission device for transmitting data via a local area network and a second transmission device for transmitting data via the Internet. Transmission device 222 may electronically transmit data signals with overlaid data that can be parsed by a receiving computing device. In some cases, transmission device 222 may include one or more modules for overlaying, encoding, or otherwise formatting data into data signals suitable for transmission.

[0048] Transmission device 222 may be configured to electronically transmit data signals to blockchain node 106, which may be overlaid or otherwise encoded with blockchain data, blockchain data entries, account tokens, sanctions data, new blockchain transactions, etc. The transmission device 222 may also be configured to electronically transmit data signals to the computing device 108, which may be superimposed or otherwise encoded with data requests, sanctions data, notification messages, hash data, etc. The transmission device 222 may also be configured to electronically transmit data signals to the issuing authority 110 and / or the regulatory entity 112, which may be superimposed or otherwise encoded with account type requests, sanctions data requests, a portion of a transaction account, a hashed transaction account, report data, etc.

[0049] Process for Account Type Registration for Blockchain Wallets

[0050] Figures 3A and 3B illustrate the process of registering account types and sanctions data for a new blockchain wallet in the system 100 of Figure 1.

[0051] In step 302, the issuing authority 110 may issue a transaction account to the user of the computing device 108. As part of issuing the transaction account, the issuing authority 110 may generate a transaction account for the transaction account, which may be provided to the computing device 108 using a suitable communication network and method. In step 304, computing device 108 may receive the transaction account of the transaction account. In step 306, computing device 108 may generate a new blockchain wallet. The generation of the new blockchain wallet may include generating a new cryptographic key pair, which includes a public key and a private key. In step 308, computing device 108 may register the new blockchain wallet with processing server 102. As part of the registration, computing device 108 may hash the transaction account and electronically transmit at least the public key and the hashed transaction account to processing server 102 using a suitable communication network and method.In some embodiments, computing device 108 may transmit a portion of a transaction account, rather than a hashed transaction account, for example, a portion of a transaction account sufficient to identify the account type. In step 310, receiving device 202 of processing server 102 may receive a public key and a hashed transaction account and / or a portion of a transaction account from processing server 102.

[0052] In step 312, transmitting device 222 of processing server 102 may electronically transmit an account type request to issuing institution 110 using a suitable communication network and method. The account type request may include at least a hashed transaction account and / or a portion of a transaction account. In step 314, issuing institution 110 may receive a hashed transaction account and / or a portion of a transaction account from processing server 102. In step 316, issuing institution 110 may identify a transaction account matching the hashed transaction account and / or a portion of a transaction account, and then identify the account type of the transaction account as an individual or entity. In step 318, issuing institution 110 may electronically transmit the account type to processing server 102 using a suitable communication network and method. In step 320, the receiving device 202 of the processing server 102 may receive the account type from the issuing structure 110.

[0053] In step 322, the transmitting device 222 of the processing server 102 may electronically transmit a request for sanctions data to the regulatory entity 112. The request for sanctions data may include a hashed transaction account and / or a portion of a transaction account. In step 324, the regulatory entity 112 may receive the sanctions data request from the processing server 102. In step 326, the regulatory entity 112 may identify a transaction account that matches the hashed transaction account and / or a portion of a transaction account, and identify any sanctions that have been imposed on the user of the transaction account. In step 328, the regulatory entity 112 may electronically transmit data regarding the identified sanctions to the processing server 102 using a suitable communication network and method.

[0054] In step 330, the receiving device 202 of the processing server 102 may receive sanctions data from the regulatory entity 112. In step 332, the generation module 218 of the processing server 102 generates a new data entry for the new blockchain wallet. This new data entry includes at least the public key of the new blockchain wallet, an account type tag based on account type data received from the issuing institution 110, and one or more sanctions tags based on sanctions data received from the regulatory entity 112. In some cases, the new data entry may further include a hashed transaction account and / or a portion thereof. In step 334, the processing server 102 stores the data entry. In some embodiments, the data entry may be an account profile 208, stored as a lookup table in the account database 206, which the blockchain node 106 and / or regulatory entity 112 can use to ensure the compliance of future blockchain transactions involving the new blockchain wallet.In other embodiments, the data entry may be a blockchain data entry stored in a blockchain sidechain, which may be added to the sidechain by the processing server 102 or the blockchain node 106 using conventional systems and methods. Account type tags and sanctions tags can then be used for compliance in future blockchain transactions.

[0055] Process for Account Type Registration for Blockchain Wallets

[0056] Figure 4 illustrates the process of determining that a blockchain transaction is subject to one or more sanctions in the system 100 of Figure 1.

[0057] In step 350, computing device 108 may conduct a blockchain transaction with one or more second parties. In step 352, computing device 108 may transmit transaction data of the blockchain transaction to processing server 102. The transaction data may include at least the public key of computing device 108 and a second public key associated with the second party of the blockchain transaction.

[0058] In step 354, receiving device 202 of processing server 102 may receive the transaction data of the blockchain transaction. In step 356, processing server 102 identifies a data entry (e.g., account profile 208) associated with the public key of computing device 108, and in step 358, determines, based on the data entry (e.g., account profile 208), whether the transaction account of computing device 108 is subject to one or more sanctions. If processing server 102 determines that the transaction account of computing device 108 is subject to one or more sanctions, then in step 360, processing server 102 may identify a second data entry (e.g., second account profile 208) associated with the second public key associated with the second party to the blockchain transaction.

[0059] In step 362, processing server 102 may update the second data entry (e.g., second account profile 208) associated with the second public key associated with the second party to the blockchain transaction based on one or more sanctions in the data entry associated with the transaction account of computing device 108. For example, processing server 102 may create an entry in the second data entry that identifies the transaction account, public key, or other suitable transaction account identifier of computing device 108. In another embodiment, processing server 102 may generate a tag in the second data entry that identifies the second data entry as associated with a data entry related to computing device 108, for example, a party subject to one or more sanctions. In this way, account database 206 may identify known affiliates or any party transacting with one or more sanctioned transaction accounts.

[0060] In step 364, processing server 102 may generate a transaction notification message. The transaction notification message notifies one or more third parties (e.g., issuing authority 110 and / or regulatory entity 112) of the one or more sanctioned transaction accounts and blockchain transactions.In step 366, processing server 102 transmits a transaction notification message to issuing institution 110 and / or regulatory entity 112, which receive the transaction notification message in steps 368 and 370, respectively.

[0061] Exemplary Method for Account Type Registration for Blockchain Wallets

[0062] As illustrated in Figure 5, a method 400 for registering the account type of a new blockchain wallet user using an associated transaction account is shown.

[0063] In step 402, a public key may be received by a receiver (e.g., receiving device 202) of the processing server (e.g., processing server 102), wherein the public key is the public key of the cryptographic key pair of the blockchain wallet associated with the blockchain. In step 404, an account identifier of the transaction account may be received by the receiver of the processing server. In step 406, the transaction type of the transaction account may be identified by a processor of the processing server (e.g., query module 216). In step 408, at least the public key and an identifier associated with the identified account type may be stored in a data entry (e.g., account profile 208).

[0064] In one embodiment, the data entry may be a blockchain data value, and the blockchain data value may be stored in a second blockchain separate from the blockchain. In some embodiments, method 400 may further include identifying one or more sanctions imposed on a transaction account by a processor of the processing server, wherein the data entry may further include one or more identifiers associated with one or more sanctions. In a further embodiment, method 400 may further include: receiving transaction data of a new blockchain transaction by a receiver of the processing server, the transaction data including at least a public key and a second public key; identifying a second data entry including the second public key by a processor of the processing server; and storing at least one of one or more identifiers in the second data entry by a processor of the processing server.

[0065] In a further embodiment, the new blockchain transaction may be subject to one or more sanctions. If it is determined that the new blockchain transaction is subject to one or more sanctions, the processor of the processing server may reject the new blockchain transaction or otherwise prevent the new blockchain transaction from being submitted to the blockchain network 104 for confirmation. Furthermore, if it is determined that a new blockchain transaction is subject to one or more sanctions, the processor of the processing server may generate a transaction notification message based on the data of the new blockchain transaction and transmit the transaction notification message to regulatory entity 112 and / or issuing authority 110 (e.g., via transmission device 222).

[0066] In one embodiment, method 400 may further include generating a hash value by the processor of the processing server using a one-way hash algorithm to hash an account identifier, wherein the data entry may further include the generated hash value. In some embodiments, the account identifier may be part of a payment account. In one embodiment, the account type may be either an individual or an entity.

[0067] Computer System Architecture Specification 10 / 13 pages 13 CN 121729704 A

[0068] FIG6 illustrates a computer system 500, wherein embodiments of the present disclosure or portions thereof may be implemented as computer-readable code. For example, a processing server 102, a blockchain node 106, a computing device 108, an issuing authority 110, a regulatory entity 112 may be implemented in the computer system 500 using hardware, a non-transient computer-readable medium on which instructions are stored, and a combination thereof, and may be implemented in one or more computer systems or other processing systems. The hardware may embody modules and components for implementing the methods of FIG3A, FIG3B, FIG4 and FIG5.

[0069] If programmable logic is used, such logic may be executed on a commercial processing platform configured by executable software code to become a dedicated computer or dedicated device (e.g., a programmable logic array, an application-specific integrated circuit, etc.). It will be understood by those skilled in the art that embodiments of the disclosed subject matter can be implemented in various computer system configurations, including multi-core multiprocessor systems, minicomputers, mainframe computers, linked or clustered computers with distributed capabilities, and ubiquitous computers or microcomputers that can be embedded in virtually any device. For example, at least one processor device and memory can be used to implement the embodiments described above.

[0070] The processor unit or device discussed herein can be a single processor, multiple processors, or a combination thereof. A processor device may have one or more processor “cores.” The terms “computer program medium,” “non-transient computer-readable medium,” and “computer-usable medium” discussed herein are generally used to refer to tangible media such as removable storage unit 518, removable storage unit 522, and hard disks mounted in hard disk drive 512.

[0071] Various embodiments of the present disclosure have been described according to the example computer system 500. After reading this description, those skilled in the art will understand how to implement the present disclosure using other computer systems and / or computing architectures. Although operations may be described as sequential processes, some operations may actually be performed in parallel, concurrently, and / or in a distributed environment, and the program code may be stored locally or remotely for access by a single-processor or multi-processor machine. Furthermore, in some embodiments, the order of operations may be rearranged without departing from the spirit of the subject matter of this disclosure.

[0072] Processor device 504 may be a dedicated or general-purpose processor device specifically configured to perform the functions discussed herein. Processor device 504 may be connected to communication infrastructure 506 such as a bus, message queue, network, multi-core messaging scheme, etc.The network can be any network suitable for performing the functions disclosed herein, and may include a local area network (LAN), a wide area network (WAN), a wireless network (e.g., WiFi), a mobile communication network, a satellite network, the Internet, fiber optic, coaxial cable, infrared, radio frequency (RF), or any combination thereof. Other suitable network types and configurations will be apparent to those skilled in the art. The computer system 500 may also include a main memory 508 (e.g., random access memory, read-only memory, etc.) and may also include secondary memory 510. The secondary memory 510 may include a hard disk drive 512 such as a floppy disk drive, a magnetic tape drive, an optical disk drive, flash memory, etc., and a removable storage drive 514.

[0073] The removable storage drive 514 may read from and / or write to the removable storage unit 518 in a well-known manner. The removable storage unit 518 may include removable storage media read from and written to by the removable storage drive 514. For example, if the removable storage drive 514 is a floppy disk drive or a universal serial bus port, the removable storage unit 518 may be a floppy disk or a portable flash drive, respectively. In one embodiment, removable storage unit 518 may be a non-transient computer-readable recording medium.

[0074] In some embodiments, secondary storage 510 may include alternative means for allowing computer programs or other instructions to be loaded into computer system 500, such as removable storage unit 522 and interface 520. Examples of such means may include program cartridges and cartridge interfaces (e.g., found in video game systems), removable storage chips (e.g., EEPROM, PROM, etc.) and associated slots, and other removable storage units 522 and interfaces 520 that are clear to those skilled in the art.

[0075] Data stored in computer system 500 (e.g., in main memory 508 and / or secondary storage 510) may be stored on any type of suitable computer-readable medium such as optical storage (e.g., optical disc, digital versatile optical disc, Blu-ray disc, etc.) or magnetic tape storage (e.g., hard disk drive). Data can be configured in any suitable database configuration, such as a relational database, a structured query language (SQL) database, a distributed database, an object database, etc. The appropriate configuration and storage type will be clear to those skilled in the art.

[0076] The computer system 500 may also include a communication interface 524. The communication interface 524 may be configured to allow software and data to be transferred between the computer system 500 and external devices. Exemplary communication interface 524 may include a modem, a network interface (e.g., an Ethernet card), a communication port, a PCMCIA slot, and cards, etc.Software and data transmitted via communication interface 524 may be in the form of signals, which may be electronic signals, electromagnetic signals, optical signals, or other signals that are clear to those skilled in the art. Signals may be propagated via communication path 526, which may be configured to carry signals and may be implemented using wires, cables, optical fibers, telephone lines, cellular telephone links, radio frequency links, etc.

[0077] Computer system 500 may further include display interface 502. Display interface 502 may be configured to allow data to be transmitted between computer system 500 and external display 530. Exemplary display interface 502 may include High Definition Multimedia Interface (HDMI), Digital Video Interface (DVI), Video Graphics Array (VGA), etc. Display 530 may be any suitable type of display for displaying data transmitted via display interface 502 of computer system 500, including cathode ray tube (CRT) displays, liquid crystal displays (LCDs), light-emitting diode (LED) displays, capacitive touch displays, thin-film transistor (TFT) displays, etc.

[0078] Computer program media and computer-usable media may refer to memory, such as main memory 508 and auxiliary memory 510, which may be memory semiconductors (e.g., DRAM, etc.). These computer program products may be means for providing software to computer system 500. Computer programs (e.g., computer control logic) may be stored in main memory 508 and / or auxiliary memory 510. Computer programs may also be received via communication interface 524. When such computer programs are executed, they enable computer system 500 to implement the methods discussed herein. Specifically, when computer programs are executed, they enable processor device 504 to implement the methods shown in Figures 3A, 3B, 4, and 5 discussed herein. Thus, such computer programs may represent a controller of computer system 500. In the case of implementing this disclosure using software, the software may be stored in the computer program product and loaded into computer system 500 using removable storage drive 514, interface 520, and hard disk drive 512 or communication interface 524.

[0079] The processor device 504 may include one or more modules or engines configured to perform the functions of the computer system 500. Each module or engine may be implemented using hardware, and in some cases, may also utilize software, such as program code and / or programs corresponding to those stored in main memory 508 or secondary memory 510. In such cases, the program code may be compiled by the processor device 504 (e.g., by a compilation module or engine) before being executed by the hardware of the computer system 500. For example, the program code may be source code written in a programming language that is translated into a lower-level language such as assembly language or machine code for execution by the processor device 504 and / or any additional hardware components of the computer system 500.The compilation process may include lexical analysis, preprocessing, parsing, semantic analysis, syntax-guided translation, code generation, code optimization, and any other techniques applicable to translating program code into a lower-level language suitable for controlling computer system 500 to perform the functions disclosed herein. It will be clear to those skilled in the art that such processes result in computer system 500 being a specially configured computer system 500 that is uniquely programmed to perform the functions described above.

[0080] Among other features, the technology consistent with this disclosure provides systems and methods for registering account types for blockchain wallets. While various exemplary embodiments of the disclosed systems and methods have been described above, it should be understood that these embodiments are presented for illustrative purposes only and are not intended to be limiting. They are not exhaustive and do not limit the disclosure to the exact forms disclosed. Modifications and variations are possible based on the foregoing teachings, or may be obtained by practicing this disclosure without departing from its breadth and scope. (Pages 12 / 13, CN 121729704 A) Instruction manual, page 13 / 13, 16 CN 121729704 A, Figure 1; Instruction manual, Figure 1 / 7, page 17 CN 121729704 A, Figure 2; Instruction manual, Figure 2 / 7, page 18 CN 121729704 A, Figure 3A; Instruction manual, Figure 3 / 7, page 19 CN 121729704 A, Figure 3B; Instruction manual, Figure 4 / 7, page 20 CN 121729704 A, Figure 4; Instruction manual, Figure 5 / 7, page 21 CN 121729704 A, Figure 5; Instruction manual, Figure 6 / 7, page 22 CN 121729704 A, Figure 6; Instruction manual, Figure 7 / 7, page 23 CN 121729704 A.

Claims

1. A method for registering account types for a blockchain wallet, comprising: The receiving device of the processing server receives the public key of the cryptographic key pair of the blockchain wallet associated with the blockchain; The receiving device of the processing server receives the account identifier of the transaction account; The processing server identifies the account type of the transaction account, and; The data entry stores at least the public key and an identifier associated with the identified account type.

2. The method according to claim 1, wherein The data entry is a blockchain data value, and The blockchain data value is stored in a second blockchain separate from the blockchain.

3. The method of claim 1, further comprising: The processing server identifies one or more sanctions imposed on the transaction account, wherein The data entry further includes one or more identifiers associated with the one or more sanctions.

4. The method of claim 3, further comprising: The receiving device of the processing server receives transaction data of a new blockchain transaction, and the transaction data includes at least the public key and the second public key; The processing server identifies a second data entry including the second public key; and The processing server stores at least one of the one or more identifiers in the second data entry.

5. The method of claim 4, wherein the new blockchain transaction is subject to one or more of the sanctions.

6. The method according to claim 4, further comprising: The processing server updates the second data entry based on the one or more sanctions imposed on the transaction account.

7. The method according to claim 4, wherein the method further comprises: The processing server generates transaction notification information based on the data from the new blockchain transactions; as well as The transaction notification message is transmitted from the processing server's transmission device to the regulatory entity.

8. The method of claim 1, further comprising: The processing server generates a hash value by hashing the account identifier using a one-way hash algorithm, wherein... The data entry further includes the generated hash value.

9. The method of claim 1, wherein the account identifier is part of a payment account.

10. The method of claim 1, wherein the account type is one of an individual or an entity.

11. A system for registering account types for blockchain wallets, comprising: Blockchain; as well as Processing server, the processing server being configured as follows: Receive the public key of the cryptographic key pair of the blockchain wallet associated with the blockchain. Receive the account identifier of the transaction account. processor Identify the account type of the transaction account, and The data entry stores at least the public key and an identifier associated with the identified account type.

12. The system of claim 11, wherein... The data entry is a blockchain data value, and The blockchain data value is stored in a second blockchain that is separate from the blockchain.

13. The system of claim 11, wherein... The processing server is configured to identify one or more sanctions imposed on the trading account, and The data entry further includes one or more identifiers associated with the one or more sanctions.

14. The system of claim 13, wherein the processing server is configured to: Receive transaction data for new blockchain transactions, wherein the transaction data includes at least the public key and the second public key. Identify the second data entry including the second public key, and At least one of the one or more identifiers is stored in the second data entry.

15. The system of claim 14, wherein the new blockchain transaction is subject to one or more of the sanctions.

16. The system of claim 14, wherein the new blockchain transaction is subject to one or more of the sanctions, and The processing server is configured to reject the new blockchain transaction.

17. The system of claim 14, wherein the new blockchain transaction is subject to one or more of the sanctions. The processing server is configured to generate transaction notification information based on the data of the new blockchain transactions, and The transmission device of the processing server is configured to transmit the transaction notification message to the regulatory entity.

18. The system of claim 11, wherein... The processing server is configured to generate a hash value by hashing the account identifier using a one-way hash algorithm, and The data entry further includes the generated hash value.

19. The system of claim 11, wherein the account identifier is part of a payment account.

20. The system of claim 11, wherein the account type is one of an individual or an entity.

Images