Jorge Timón [ARCHIVE] on Nostr: 📅 Original date posted:2011-11-23 🗒️ Summary of this message: A proposed ...
📅 Original date posted:2011-11-23
🗒️ Summary of this message: A proposed system for blockchain timestamp cheating is debunked by stating that the probability of mining a block is 100% and requires actual hashing power.
📝 Original message:2011/11/23, Andy Parkins <andyparkins at gmail.com>:
> On 2011 November 23 Wednesday, Jorge Timón wrote:
>> 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?
>
> (1) The "probability of mining a block" is old-think. The probability of
> mining a block is 100% in my system. Instead, it becomes "the probability
> of
> your block being the hardest" and that requires actual hashing power
> regardless of the timestamp you write on the block. I could write that my
> block was generated next year; but I can't fake the hashing power it needs
> to
> generate one year's worth of hashes.
Well, I meant "the probability of your block being the hardest".
What a miner can do is hash the block (cheating the timestamp) for 2
more minutes than the rest of the people and then send it to the other
nodes. Nodes cannot possibly know when did you hashed the block only
by looking at their clock when they receive it, because there's also
network latency.
> (2) For the network clock; see util.cpp:GetAdjustedTime().
1) This is part of the satoshi client but not the protocol. A miner
can rewrite this part of the code and there won't be anything in the
chain that contradicts the protocol.
2) I haven't read the code but I'm pretty sure that's not a perfect
decentralized clock.
I will be more specific. Where's the network clock in the chain (in
the protocol)?
--
Jorge Timón
Published at
2023-06-07 02:41:40Event JSON
{
"id": "8e5fa82820bc19966728170fd5ab222e9fac62f19b127816af3a9c963cea99b1",
"pubkey": "498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84",
"created_at": 1686105700,
"kind": 1,
"tags": [
[
"e",
"2046d4dc725b4ce8920d2c47249dd7dad0c6e38daddd7a5e99f03e9b24dd8e66",
"",
"root"
],
[
"e",
"9f063dface52f2074bddbde265701f9fd5ebe0a879691d94260dda74a22203d0",
"",
"reply"
],
[
"p",
"99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59"
]
],
"content": "📅 Original date posted:2011-11-23\n🗒️ Summary of this message: A proposed system for blockchain timestamp cheating is debunked by stating that the probability of mining a block is 100% and requires actual hashing power.\n📝 Original message:2011/11/23, Andy Parkins \u003candyparkins at gmail.com\u003e:\n\u003e On 2011 November 23 Wednesday, Jorge Timón wrote:\n\u003e\u003e With the current system, the timestamp can also be cheated, but miners\n\u003e\u003e have no direct incentive to do it. With your system, they increase\n\u003e\u003e their probability of mining a block by putting a false timestamp.\n\u003e\u003e Also, where's the network clock you're talking about? Isn't it the\n\u003e\u003e timestamps in the blockchain?\n\u003e\n\u003e (1) The \"probability of mining a block\" is old-think. The probability of\n\u003e mining a block is 100% in my system. Instead, it becomes \"the probability\n\u003e of\n\u003e your block being the hardest\" and that requires actual hashing power\n\u003e regardless of the timestamp you write on the block. I could write that my\n\u003e block was generated next year; but I can't fake the hashing power it needs\n\u003e to\n\u003e generate one year's worth of hashes.\n\nWell, I meant \"the probability of your block being the hardest\".\nWhat a miner can do is hash the block (cheating the timestamp) for 2\nmore minutes than the rest of the people and then send it to the other\nnodes. Nodes cannot possibly know when did you hashed the block only\nby looking at their clock when they receive it, because there's also\nnetwork latency.\n\n\u003e (2) For the network clock; see util.cpp:GetAdjustedTime().\n\n1) This is part of the satoshi client but not the protocol. A miner\ncan rewrite this part of the code and there won't be anything in the\nchain that contradicts the protocol.\n\n2) I haven't read the code but I'm pretty sure that's not a perfect\ndecentralized clock.\n\nI will be more specific. Where's the network clock in the chain (in\nthe protocol)?\n\n-- \nJorge Timón",
"sig": "b47c9352c57e37b96b05f0e54144282ade42a3eb826c3feb17a57e2ab178849bb51b7468f688d0c8cb9b8659bde5728464f03ccd49b9d6b422f3dc25dfd7eba7"
}