Corrections should leave a trail.
Degrees of Satoshi does not silently overwrite a released result or materially change a historical claim without recording what changed and why.
Public research correction intake is open. Submit factual corrections through the structured correction form. Use review issue #1 for methodological review. Both routes are public; do not put private security, personal or sensitive information there.
What the public intake will require
A useful report should identify the affected URL or release, quote the disputed claim or field, link the strongest available evidence and explain the proposed correction. Reports receive a severity, public-safe summary, disposition and target version. Inspect the complete public research repository.
How changes are classified
- Methodology and graph rerunAny anchor or terminal membership, direction rule, threshold meaning, equal-path rule, chain snapshot or graph-population change requires a new methodology version and graph rerun.
- Data or package correctionAn exporter, schema, checksum, citation or chart correction that changes released bytes without changing graph results requires a new package version.
- Editorial correctionA wording, source-link or accessibility correction that leaves results intact is recorded in version history and any affected rendered artifact is regenerated.
- RetractionIf a flaw invalidates the central result or private data enters a public artifact, promotion stops, a tombstone and reason remain, and replacement bytes receive a new immutable version.
Private reports
Private security or privacy reports will not be copied into a public response log. A separate private channel must be established before the project claims it can safely receive those reports.
Current release status
The Bitcoin address-graph report is a frozen aggregate release candidate. Its public page currently records no corrections and does not claim independent review. The public repository and review issue are live; archival deposit and DOI assignment remain pending.
Public record requirements
For an archived release, Git tag, archival metadata, DOI metadata, checksums, version history and the public response log must agree. Archived bytes are never silently replaced.