decentralized transitive trust of code #1487

New issue

Open

opened 2026-08-19 15:45:57 +02:00 by kiara · 0 comments

kiara commented

2026-08-19 15:45:57 +02:00

Owner

As a hosting provider,
I want to have a system to trust code,
so that i may hedge risks without having to read everything myself.

implementation notes

the idea would be that people could (transitively) trust other people and their (future) published work
currently fediversity uses an allow-list of repos (see #1090 / #1097, #1178 / #1180)
repositories / sealed flakes (validated seal) - tho the principles here should work agnostic from nix
revisions
signers
signatures
keys
web of trust
publishing URLs as feed of versions
second feed of parties that have checked and accepted revisions
prevent DoS on download
query list of signatories
threshold signatures (e.g. trusted by >1 parties) and anchoring: want trusted person from banking sector or universities
similar problem to trusting of nix caches
certificate authorities like with TLS
trust decentralized

**As** a hosting provider, **I want** to have a system to trust code, **so that** i may hedge risks without having to read everything myself. ### implementation notes - the idea would be that people could (transitively) trust other people and their (future) published work - currently fediversity uses an allow-list of repos (see #1090 / #1097, #1178 / #1180) - repositories / sealed flakes (validated seal) - tho the principles here should work agnostic from nix - revisions - signers - signatures - keys - web of trust - publishing URLs as feed of versions - second feed of parties that have checked and accepted revisions - prevent DoS on download - query list of signatories - threshold signatures (e.g. trusted by >1 parties) and anchoring: want trusted person from banking sector or universities - similar problem to trusting of nix caches - certificate authorities like with TLS - trust decentralized

Rows
Columns