aere-network/aere-node
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

registries/README.md: the hosts the files were read from are separate hosts, all operated by the Foundation today (the text said 'independently operated')

Browse Source
This commit is contained in:
Aere Network 2026-10-05 17:49:18 +03:00
parent 1fa2ed0f46
commit 1c6d583f6a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
registries/README.md
View File

@ -51,10 +51,10 @@ c6601ae5159875a090066946991517c9a38e5d6206da76b018c0917e1ca6f12f manifest-18082
## Provenance
Fetched from the running fleet and cross-checked so that these are the bytes the network validates
against, not a local rebuild. Each of the three files was read from three independent validator hosts
against, not a local rebuild. Each of the three files was read from three separate validator hosts
and produced the **same** sha256 on all three. A registry is only meaningful if it is the one the
chain was signed against; a fingerprint that agrees across three independently operated hosts is that
evidence. The digests above are those agreed fingerprints. `manifest-18082816.json` and `hibrid-10.properties`, added 2026-09-10, were read from inside the running node containers, on the paths the nodes actually load, on four independent hosts (the archive node and three validators), with the same sha256 on all four.
chain was signed against; a fingerprint that agrees across three separate hosts (all operated by the Foundation today) is that
evidence. The digests above are those agreed fingerprints. `manifest-18082816.json` and `hibrid-10.properties`, added 2026-09-10, were read from inside the running node containers, on the paths the nodes actually load, on four separate hosts (the archive node and three validators), with the same sha256 on all four.
## How a node uses them