Blockchain architecture with record security

1. A method comprising:

receiving, by a validation node from an acceptance node, a transaction record for a transaction conducted between the acceptance node and a user, the transaction record including at least information related to the user and transaction details;

identifying, based on the information related to the user, a blockchain associated with the transaction conducted between the acceptance node and the user;

appending the transaction record to the blockchain;

generating a signature by:

generating a first hash of at least a portion of the information related to the user;

generating a second hash of at least a portion of the transaction details;

combining the first hash and the second hash into a text string,

wherein combining the first hash and the second hash comprises concatenating the first hash and the second hash;

hashing the text string to form a third hash, the third hash being a derivative of the text string; and

signing the derivative of the text string, using a private key associated with the validation node to form the signature;

attaching the signature to the transaction record that is appended to the blockchain to update the blockchain, wherein the blockchain is a ledger storing information regarding transactions conducted between one or more acceptance nodes and the user; and

sending, to the one or more acceptance nodes that are associated with one or more resource providers computers, the updated blockchain;

verifying, by the one or more resource providers computers, verify the a second transaction with the user based on the information stored in the updated blockchain;

determining, by the one or more resource provider computers, determine a level of risk associated with the second transaction; and

determining, by the one or more resource provider computers, detcrminc whether to conduct the second transaction based on the determined level of risk.

2. The method of claim 1 , wherein the acceptance node is a computer operated by a resource provider.

3. The method of claim 1 , wherein the private key is an RSA encryption key.

4. The method of claim 1 , wherein the blockchain comprises a plurality of nodes, and wherein the plurality of nodes includes at least a plurality of acceptance nodes.

5. The method of claim 1 , wherein the blockchain comprises a plurality of nodes, and wherein the plurality of nodes includes at least a plurality of validation nodes.

6. The method according to claim 1 , further comprising, after receiving the transaction record from the acceptance node, determining that the acceptance node is authorized to participate in a blockchain network.

7. The method according to claim 1 , wherein the blockchain associated with the transaction conducted between the acceptance node and the user is identified based on an electronic identifier.

8. The method of claim 1 , further comprising determining whether the acceptance node is authorized to participate in a blockchain network prior to appending the transaction record to the blockchain.

9. The method of claim 1 , wherein the first hash of at least a portion of the user information comprises an electronic identifier.

10. The method of claim 1 , further comprising distributing the blockchain to a client device associated with the user.

11. A system comprising:

a validation node server comprising:

one or more processors; and

a memory including instructions that, when executed by the one or more processors, cause the validation node server to:

receive, from an acceptance node server, a transaction information for a transaction conducted between the acceptance node server and a user, the transaction information including at least user information and transaction details;

identify, based on the user information, a blockchain associated with the transaction;

generate a transaction record based at least in part on the transaction information;

append the transaction record to the blockchain;

generate a signature by:

generating a first hash of at least a portion of the user information;

generating a second hash of at least a portion of the transaction details;

combining the first hash and the second hash into a text string,

wherein combining the first hash and the second hash comprises concatenating the first hash and the second hash;

hashing the text string to form a third hash, the third hash being a derivative of the text string; and

signing the derivative of the text string, using a private key associated with the validation node server to form the signature; and

attach the signature to the transaction record that is appended the blockchain to update the blockchain,

wherein the blockchain is a ledger storing information regarding transactions conducted between one or more acceptance nodes and the user; and

send to the one or more acceptance nodes that are associated with one or more resource providers computers, the updated blockchain; and

the one or more resource provider computers each comprising a processor and a memory including instructions that, when executed by the processor, cause the one or more resource provider computers to:

verify a second transaction with the user based on the information stored in the updated blockchain;

determine a level of risk associated with the second transaction; and

determine whether to conduct the second transaction based on the determined level of risk.

12. The system of claim 11 , wherein the instructions further cause the validation node server to distribute a public key within a blockchain network.

13. The system of claim 11 , wherein the instructions further cause the validation node server to determine whether the acceptance node server is authorized to participate in a blockchain network prior to appending the transaction record to the blockchain.

14. The system of claim 11 , wherein the first hash of at least a portion of the user information comprises an electronic identifier.

15. The system of claim 11 , wherein the instructions further cause the validation node server to distribute the blockchain to a client device associated with the user.

16. The system of claim 11 , wherein the acceptance node server is a computer operated by a resource provider.

17. The system of claim 11 , wherein the private key is an RSA encryption key.

18. The system of claim 11 , wherein the blockchain comprises a plurality of nodes, and wherein the plurality of nodes includes at least a plurality of acceptance nodes.

19. The system of claim 11 , wherein the blockchain comprises a plurality of nodes, and wherein the plurality of nodes includes at least a plurality of validation nodes.