doc: Update asmap-data repository rule for file inclusion
What the developer wrote
Authored by Fabian Jahr
doc: Update asmap-data repository rule for file inclusion
What changed, and why it matters
This commit only updates a documentation file describing how asmap-data files are accepted into a related repository. It changes the rule from needing 5+ participants with a matching majority result to needing a result hash signed by 5+ participants. There is no code change and no direct security impact on Bitcoin Core itself.
No security action required. Review as a normal documentation update if relevant to project governance documentation.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies doc/asmap-data.md, a markdown documentation file. It updates the inclusion criteria for ASMap data files in the asmap-data repository. The change is procedural/governance wording: replacing ‘5 or more participants’ and ‘majority received the same result’ with ‘result hash observed by the most participants is signed by 5 participants or more’. No source code, build scripts, tests, or runtime behavior is affected.
Changed components
doc/asmap-data.mdInspect captured patch +3 / −3
diff --git a/doc/asmap-data.md b/doc/asmap-data.md
index 09e2f95c..e3035e58 100644
--- a/doc/asmap-data.md
+++ b/doc/asmap-data.md
@@ -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
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.