QuotableSatoshi on Nostr: For our timestamp network, we implement the proof-of-work by incrementing a nonce in ...
For our timestamp network, we implement the proof-of-work by incrementing a nonce in the block until a value is found that gives the block's hash the required zero bits. Once the CPU effort has been expended to make it satisfy the proof-of-work, the block cannot be changed without redoing the work. As later blocks are chained after it, the work to change the block would include redoing all the blocks after it.
Published at
2024-09-13 12:21:02Event JSON
{
"id": "0fcc3e9169a7ec994117279a99a7f089a8ea773b3d3960fe8bbe12968d34902f",
"pubkey": "87570647ca3b7549e66cb6c4bb8d197f5bc91de73b58eb1ade78c8ddd5fec7eb",
"created_at": 1726230062,
"kind": 1,
"tags": [],
"content": "For our timestamp network, we implement the proof-of-work by incrementing a nonce in the block until a value is found that gives the block's hash the required zero bits. Once the CPU effort has been expended to make it satisfy the proof-of-work, the block cannot be changed without redoing the work. As later blocks are chained after it, the work to change the block would include redoing all the blocks after it.",
"sig": "cc3eeb612c4f4b09049e4cab78ac41881ca103431efab016264ba4863595ace362531e9365043bebd7b40d048c83535921481d1c192d45fe6f1144ea3a6a8021"
}