📅 Original date posted:2014-04-10
📝 Original message:Checkpoints will go away, eventually.
On 04/10/2014 02:34 PM, Jesus Cea wrote:
> On 10/04/14 18:59, Pieter Wuille wrote:
>> It's important to
>> note that this is a strict reduction in security: we're now trusting
>> that the longest chain (with most proof of work) commits to a valid
>> UTXO set (at some point in the past).
>
> AFAIK, current bitcoin code code already set blockchain checkpoints from
> time to time. It is a garanteed that a longer chain starting before the
> checkpoint is not going to be accepted suddently. See
> <https://bitcointalk.org/index.php?topic=194078.0>;.
>
> Could be perfectly valid to store only unspend wallets before last
> checkpoint, if during the blockchain download the node did all the checks.
>
> Would be interesting, of course, to be able to verify "unspend wallet
> accounting" having only that checkpoint data (the merkle tree can do
> that, I guess). So you could detect a data corruption or manipulation in
> your local harddisk.
>
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
>
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
Mark Friedenbach [ARCHIVE] /
npub1r3…48d0u
2023-06-07 15:18:33
in reply to nevent1q…dv2a
Author Public Key
npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0uSeen on
wss://relay.noswhere.comPublished at
2023-06-07 15:18:33Event JSON
{
"id": "48fb323238750e7b4b4090ced35858177157de2bec2ba111230541db56c66d87",
"pubkey": "1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069",
"created_at": 1686151113,
"kind": 1,
"tags": [
[
"e",
"aae8a2dedee78eef571f285fef23331d89c84b104c87b098618414541001d13e",
"",
"root"
],
[
"e",
"c1614bebbfd6520c256e14df3b8ea41184e016cfdb3b179f938bfc207dcef2dc",
"",
"reply"
],
[
"p",
"8952c8c5fef0b368e5ac788aa0c3927f870221385927091e3379a181bc0700ee"
]
],
"content": "📅 Original date posted:2014-04-10\n📝 Original message:Checkpoints will go away, eventually.\n\nOn 04/10/2014 02:34 PM, Jesus Cea wrote:\n\u003e On 10/04/14 18:59, Pieter Wuille wrote:\n\u003e\u003e It's important to\n\u003e\u003e note that this is a strict reduction in security: we're now trusting\n\u003e\u003e that the longest chain (with most proof of work) commits to a valid\n\u003e\u003e UTXO set (at some point in the past).\n\u003e \n\u003e AFAIK, current bitcoin code code already set blockchain checkpoints from\n\u003e time to time. It is a garanteed that a longer chain starting before the\n\u003e checkpoint is not going to be accepted suddently. See\n\u003e \u003chttps://bitcointalk.org/index.php?topic=194078.0\u003e.\n\u003e \n\u003e Could be perfectly valid to store only unspend wallets before last\n\u003e checkpoint, if during the blockchain download the node did all the checks.\n\u003e \n\u003e Would be interesting, of course, to be able to verify \"unspend wallet\n\u003e accounting\" having only that checkpoint data (the merkle tree can do\n\u003e that, I guess). So you could detect a data corruption or manipulation in\n\u003e your local harddisk.\n\u003e \n\u003e \n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e Put Bad Developers to Shame\n\u003e Dominate Development with Jenkins Continuous Integration\n\u003e Continuously Automate Build, Test \u0026 Deployment \n\u003e Start a new project now. Try Jenkins in the cloud.\n\u003e http://p.sf.net/sfu/13600_Cloudbees\n\u003e \n\u003e \n\u003e \n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e",
"sig": "32aea3e197e844e8e9b356f6520306144867fc9ef3fc3028e3f4fde76ebdd47d31016fcd35b15d7c13338ea1488c2aa6ddbc63fab7a7c5821389ac787c37333a"
}