[WIP] 3072-bit MuHash based hash_serialized#10434
[WIP] 3072-bit MuHash based hash_serialized#10434sipa wants to merge 4 commits intobitcoin:masterfrom
Conversation
paveljanik
left a comment
paveljanik
left a comment
There was a problem hiding this comment.
Release notes entry needed.
src/crypto/muhash.cpp
Outdated
There was a problem hiding this comment.
Copyright header missing
src/test/crypto_tests.cpp
Outdated
src/test/crypto_tests.cpp
Outdated
src/test/crypto_tests.cpp
Outdated
sipa
force-pushed
the
muhash
branch
3 times, most recently
from
7940961 to
791b3ac
Compare
|
@sipa - did this POC of chainstate only sync: Worked well - syncs as fast at you can download chainstate db (30mins for 2.8gig chainstate). Network was the bottleneck. Or guess could compute hash by downloading every block! Then no security loss. But 150Gig download - so still 8hrs for 40Mbit connection. (think the hashing would take about 1 hour but in parallel with download). |
|
Closing as stale. |
4 participants
This implements a 3072-bit MuHash discussed on https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014337.html as a replacement for the hash_serialized field in
gettxoutsetinfo.This is an order-independent hash, allowing it to be computed either by iterating over the UTXO set in non-sorted order. It also supports incremental addition and deletion of entries from the hash, allowing it to be updated on the fly for each block. Neither of these approaches is currently implemented.