cryptogera/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2026-03-16 16:32:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge bitcoin/bitcoin#34751: doc: Update asmap-data repository rule for file inclusion

Browse Source 
8bc62ce173dd492ca862a692a88d526d406e0eb3 doc: Update asmap-data repository rule for file inclusion (Fabian Jahr)

Pull request description:

  This updates the decision rule for file inclusion in the asmap-data repository after a collaborative run following discussion in the latest run: https://github.com/bitcoin-core/asmap-data/issues/44

  The change is small but does a few things:
  - No minimum number of participants recommended anymore
  - Minimum number of matches set to 5 (which was previously the number of recommended min participants)
  - The result that is taken does not need to see a match between the majority of participants, it only needs to have the most matches
  - Participants that saw a match should sign for it

  I also thought about adding an explicit tie-breaker if there are two results with the same number of matches but since both results are equally valid I think it won't be needed (?)

ACKs for top commit:
  hodlinator:
    ACK 8bc62ce173dd492ca862a692a88d526d406e0eb3
  luisschwab:
    ACK 8bc62ce173dd492ca862a692a88d526d406e0eb3
  janb84:
    Concept ACK 8bc62ce173dd492ca862a692a88d526d406e0eb3

Tree-SHA512: 439ba1275662122e226aa472dd96fa8ed0e1af3e91d695c711e082d7ba182883e1174f954d2531cdf7e05bdbeab5ef088f8bcbd39c7124afe82baf2026ed391b
This commit is contained in:
merge-script 2026-03-10 14:32:34 +00:00
commit 48f26e2040
No known key found for this signature in database
GPG Key ID: 2EEB9F5CC09526C1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/asmap-data.md
View File

@ -41,9 +41,9 @@ To overcome this, multiple users can start the download process at the exact
same time which leads to a high likelihood that their downloaded data will be
similar enough that they receive the same output at the end of the process.
This process is regularly coordinated at the [asmap-data](https://github.com/asmap/asmap-data)
project. If enough participants have joined the effort (5 or more is recommended) and a majority of the
participants have received the same result, the resulting ASMap file is added
to the repository for public use. Files will not be merged to the repository
project. If the result hash that was observed by the most participants is signed
by 5 participants or more, the resulting ASMap file is added to the repository for
public use. Files will not be merged to the repository
without at least two additional reviewers confirming that the process described
above was followed as expected and that the encoding step yielded the same
file hash. New files are created on an ongoing basis but without any central planning