📅 Original date posted:2011-11-23
🗒️ Summary of this message: Proposed system for generating the most difficult block, but concerns raised about miners cheating the timestamp and lack of network clock.
📝 Original message:With the current system, the timestamp can also be cheated, but miners
have no direct incentive to do it. With your system, they increase
their probability of mining a block by putting a false timestamp.
Also, where's the network clock you're talking about? Isn't it the
timestamps in the blockchain?
2011/11/23, Andy Parkins <andyparkins at gmail.com>:
> On 2011 November 23 Wednesday, Jorge Timón wrote:
>> 2011/11/23, Andy Parkins <andyparkins at gmail.com>:
>> > Let's abandon the idea of a target difficulty. Instead, every node just
>> >
>> > generates the most difficulty block it can. Simultaneously, every node
>> > is listening for "the most difficult block generated before time T";
>> > with T being
>> > picked to be the block generation rate (10 minutes).
>>
>> A miner could try to obtain more difficulty out of time and cheat its
>> reported datetime (T).
>
> Just as with the current system.
>
> The defence is that on receipt of a block, its timestamp is checked against
> the node's own clock and averaged network clock. Blocks out of that band
> are
> rejected.
>
>
> Andy
> --
> Dr Andy Parkins
> andyparkins at gmail.com
>
--
Jorge Timón
Jorge Timón [ARCHIVE] /
npub1fx…cl2d8
2023-06-07 02:41:07
in reply to nevent1q…gywg
Author Public Key
npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8Published at
2023-06-07 02:41:07Event JSON
{
"id": "cdc8f9a70d5dd858b263f72b500acd171b0d7dcba38286bd9d672bf70a704cc4",
"pubkey": "498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84",
"created_at": 1686105667,
"kind": 1,
"tags": [
[
"e",
"2046d4dc725b4ce8920d2c47249dd7dad0c6e38daddd7a5e99f03e9b24dd8e66",
"",
"root"
],
[
"e",
"9d2d915d9ded664d358be3f451b4029f74067931cb7eaf607bdb08ebb0761f75",
"",
"reply"
],
[
"p",
"99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59"
]
],
"content": "📅 Original date posted:2011-11-23\n🗒️ Summary of this message: Proposed system for generating the most difficult block, but concerns raised about miners cheating the timestamp and lack of network clock.\n📝 Original message:With the current system, the timestamp can also be cheated, but miners\nhave no direct incentive to do it. With your system, they increase\ntheir probability of mining a block by putting a false timestamp.\nAlso, where's the network clock you're talking about? Isn't it the\ntimestamps in the blockchain?\n\n\n\n2011/11/23, Andy Parkins \u003candyparkins at gmail.com\u003e:\n\u003e On 2011 November 23 Wednesday, Jorge Timón wrote:\n\u003e\u003e 2011/11/23, Andy Parkins \u003candyparkins at gmail.com\u003e:\n\u003e\u003e \u003e Let's abandon the idea of a target difficulty. Instead, every node just\n\u003e\u003e \u003e\n\u003e\u003e \u003e generates the most difficulty block it can. Simultaneously, every node\n\u003e\u003e \u003e is listening for \"the most difficult block generated before time T\";\n\u003e\u003e \u003e with T being\n\u003e\u003e \u003e picked to be the block generation rate (10 minutes).\n\u003e\u003e\n\u003e\u003e A miner could try to obtain more difficulty out of time and cheat its\n\u003e\u003e reported datetime (T).\n\u003e\n\u003e Just as with the current system.\n\u003e\n\u003e The defence is that on receipt of a block, its timestamp is checked against\n\u003e the node's own clock and averaged network clock. Blocks out of that band\n\u003e are\n\u003e rejected.\n\u003e\n\u003e\n\u003e Andy\n\u003e --\n\u003e Dr Andy Parkins\n\u003e andyparkins at gmail.com\n\u003e\n\n\n-- \nJorge Timón",
"sig": "805e9e091618b8e3f09c7ce478121e03bad8cbc46b28dd84fe7d974104c73b6c8c89c3f50e60bd3f2e8893a3a6a8074bb7f0dd336ba74118c27b4100680af965"
}