QUANTUMPROOF BLOCKCHAIN

1 - 12 . (canceled)

13 . A method of maintaining a blockchain, comprising:

maintaining a public key file configured to store one or more public keys used in a plurality of blockchain transactions, each of the one or more public keys associated with a respective one of one or more corresponding addresses of one or more users;

receiving a plurality of blockchain transactions, wherein the one or more users verified each of the plurality of blockchain transactions by;

searching the public key file for a respective public key used to generate a respective blockchain transaction;

verifying the respective blockchain transaction based at least in part on the respective public key, wherein the respective public key is not stored with the verified blockchain transaction.

14 . The method of claim 13 , further comprising:

maintaining a blockchain hash table comprising a plurality of public keys and corresponding hash values, wherein each public key of the plurality of public keys is fixed and associated with a single user; and

for each blockchain transaction:

determining a public key used to generate the blockchain transaction; and

associating, in the blockchain hash table, the blockchain transaction with the public key.

15 . The method of claim 14 , further comprising;

determining that a blockchain transaction comprises malicious activity;

determining a public key used to generate the blockchain transaction; and

associating, in the blockchain hash table, the malicious activity with the public key.

16 . The method of claim 15 , wherein the malicious activity relates to a bitcoin transaction.

17 . The method of claim 15 , wherein the malicious activity is a Distributed Denial of Service (DDoS) attack or an eclipse attack.

18 . The method of claim 13 , wherein each of the one or more public keys is associated with a public key infrastructure (PKI) certificate.

19 . The method of claim 13 , wherein each of the one or more public keys is a Rainbow public key.

20 . The method of claim 13 , wherein at least one of the plurality of blockchain transactions is a financial transaction.

21 . A method of maintaining a blockchain, comprising:

receiving a first one or more blockchain transactions, wherein the first one or more blockchain transactions store one or more public keys used to generate the first one or more blockchain transactions; and

receiving a second one or more blockchain transactions, wherein the second one or more blockchain transactions involve the one or more public keys, wherein the second one or more blockchain transactions were verified by one or more users referring to the first one or more blockchain transactions and the second one or more blockchain transactions do not store the one or more public keys.

22 . The method of claim 13 , further comprising:

maintaining a blockchain hash table comprising a plurality of public keys and corresponding hash values, wherein each public key of the plurality of public keys is fixed and associated with a single user; and

for each blockchain transaction:

determining a public key used to generate the blockchain transaction; and

associating, in the blockchain hash table, the blockchain transaction with the public key.

23 . The method of claim 22 , further comprising;

determining that a blockchain transaction comprises malicious activity;

determining a public key used to generate the blockchain transaction; and

associating, in the blockchain hash table, the malicious activity with the public key.

24 . The method of claim 23 , wherein the malicious activity relates to a bitcoin transaction.

25 . The method of claim 23 , wherein the malicious activity is a Distributed Denial of Service (DDoS) attack or an eclipse attack.

26 . The method of claim 21 , wherein each of the one or more public keys is associated with a public key infrastructure (PKI) certificate.

27 . The method of claim 21 , wherein at least one of the one or more public keys is a Rainbow public key.

28 . The method of claim 13 , wherein at least one of the second one or more blockchain transactions is a financial transaction.

29 . A system for maintaining a blockchain, the system comprising:

one or more processors;

a non-transitory, computer-readable storage medium in operable communication with at least one processor of the one or more processors, wherein the computer-readable storage medium contains one or more programming instructions that, when executed, cause the processor to:

maintain a public key file configured to store one or more public keys used in a plurality of blockchain transactions, each of the one or more public keys associated with a respective one of one or more corresponding addresses of one or more users;

receive a plurality of blockchain transactions, wherein the one or more users verified each of the plurality of blockchain transactions by;

searching the public key file for a respective public key used to generate a respective blockchain transaction;

verifying the respective blockchain transaction based at least in part on the respective public key, wherein the respective public key is not stored with the verified blockchain transaction.

30 . The system of claim 29 , wherein the instructions, when executed, further cause the one or more processors to:

maintain a blockchain hash table comprising a plurality of public keys and corresponding hash values, wherein each public key of the plurality of public keys is fixed and associated with a single user; and

for each blockchain transaction:

determine a public key used to generate the blockchain transaction; and

associate, in the blockchain hash table, the blockchain transaction with the public key.

31 . The system of claim 29 , wherein the instructions, when executed, further cause the one or more processors to:

maintain a public key infrastructure comprising a plurality of certificates, wherein each certificate of the plurality of certificates is fixed and associated with a single user;

receive a plurality of blockchain transactions; and

for each blockchain transaction:

determine a certificate used to generate the blockchain transaction; and

associate the blockchain transaction with the certificate.

32 . The system of claim 29 , wherein at least one of the plurality of blockchain transactions is a financial transaction.