Methods for Securely Adding Data to a Blockchain Using Dynamic Time Quanta and Version Authentication
Devices can be configured to implement distributed ledgers capable of immutably recording ledger entries that have validated version identifiers. The devices can include network interfaces, memory and processors. Processors can be configured to obtain ledger entries including version identifiers and version authenticator values, determine software versions that correspond to version identifiers, determine that version identifiers are valid based on version authenticator values, obtain challenges using cryptographic systems, wherein challenges are based on ledger entries, and/or broadcast blocks that incorporate ledger entries to securely add blocks to distributed ledgers. Blocks can be capable of being validated by using cryptographic systems to obtain proofs based on challenges.
1 . A device configured to implement a distributed ledger capable of immutably recording a hash chain, the device comprising:
a network interface;
memory; and
a processor, the processor configured to:
obtain a ledger entry, the ledger entry comprising:
a hash chain; and
an event;
obtain a challenge using a cryptographic system, wherein the challenge is based on the hash chain and the event; and
broadcast a block that incorporates the ledger entry to securely add the block to a distributed ledger, wherein the block is capable of being validated by using a cryptographic system to obtain a proof based on the challenge.
2 . The device of claim 1 , wherein the proof is generated based on an iterative process.
3 . The device of claim 1 , wherein the challenge is further based on a hardness value.
4 . The device of claim 1 , wherein the challenge is further based on a hardness value and wherein the hardness value is modified based on an occurrence of at least one collision associated with the event.
5 . The device of claim 1 , wherein the challenge is further based on a hardness value and wherein the hardness value is modified based on a number of ledger closings.
6 . The device of claim 1 , wherein the challenge is further based on a hardness value and wherein the hardness value is modified based on a change in system time.
7 . The device of claim 1 , wherein the challenge is further based on a hardness value and wherein the hardness value is modified based on an absence of at least one collision associated with the event.
8 . The device of claim 1 , wherein the hash chain is used for a Proof of History computation.
9 . The device of claim 1 , wherein the hash chain is used to create a relative order between recorded events, wherein the recorded events comprise the event.