melroy89/registry
1
Fork 0
forked from Flowee/registry
Code Pull Requests Activity

Add trust inherited from authchain

Browse Source
This commit is contained in:
TomZ
2025-04-11 18:14:47 +02:00
parent c57fd2ddca
commit 7c455754db
4 changed files with 82 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/trust
+22 -4
View File
@@ -53,14 +53,32 @@ The file is very simple name/value pairs in standard unix line-endings.
Fields are read from top to bottom, you can mention the same field various
times such that the item is processed in order.
* trust=ultimate
The trust level is given. none, marginal, good, high, ultimate
* trust=good
The trust level is given. absent, marginal, good, high
* domain=bitcoincash.org
Provides the source of the metadata in dns form.
* category=deadbeef0124
* category=deadbeef0124
A 64 character, hex-encoded token category. Which will then inherit
the most recently set trust.
* authbase=deadbeef0124
* authbase=deadbeef0124
A 64 character, hex-encoded authbase (txid). Which will then inherit
the most recently set trust. Allowing for all metadata files indicated
by it to likewise inherit this trust.
Trust levels
+---+---+
|Level|Description|
+---+---+
| absent | Trust has been violated, this is likely a scam or spam. |
| marginal | [Default] No trust could be established |
| good | Minimal checking has been done, likely an honest party |
| high | The party is trusted by the registry owner |
| ultimate | We know that the content comes from the party they say they are.|
Notice that the ultimate trust is really only used to describe confidence
level of the metadata file being published by who they say they are. Or
really if you are publishing your own metadata on your own registry this
way.