Verfication of provided pruned database #28887

1. 
   shufps commented at 8:05 am on November 16, 2023: none

   Please describe the feature you’d like to see added.

   If I understood it right, the risk of using a pruned database from someone is that the UTXOs could be manipulated.

   It would easily be possible to create a UTXO checksum that is compared with other nodes to find out if it is valid or not - instead of downloading the entire chain.

   Is your feature related to a problem, if so please describe it.

   Downloading the entire chain takes a long time.

   Problem is getting bigger and bigger over time and there just should be some easy and fast verification mechanism.

   Describe the solution you’d like

   Implement something that can deterministically hash the UTXOs and compare it with other nodes.

   Describe any alternatives you’ve considered

   No response

   Please leave any additional context

   IMHO there is no technical reason why this shouldn’t work - it just wasn’t implemented.

2. shufps added the label Feature on Nov 16, 2023
3. 
   maflcko commented at 8:19 am on November 16, 2023: member

   Are you aware of assumeutxo?
4. 
   shufps commented at 8:31 am on November 16, 2023: none

   Are you aware of assumeutxo?

   Didn’t know it. Thx a lot!

   Bootstrapping from an UTXO snapshot is even better than just validating the UTXOs and actually it’s been common practice in several crypto currencies for a long time, so why not in bitcoin too :man_shrugging:

5. 
   maflcko commented at 8:34 am on November 16, 2023: member

   Ok, closing for now. Let us know if you have any other questions.

   Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange or the #bitcoin IRC channel on Libera Chat.

6. maflcko closed this on Nov 16, 2023

   ---

7. bitcoin locked this on Nov 15, 2024

Contributors
shufps maflcko

Labels
Feature