Decentralized Registry Tools
On-chain or peer-verified name/asset registries.
Partial overlap. Executables are pushed into the cluster's own content-addressed store and referenced by BLAKE3 digest, optionally with a signed publisher attestation that hosts can require. It is a per-cluster store, not a public registry. Container images are pulled from ordinary registries by digest.
What a decentralized registry actually is
A registry maps names to something authoritative -- a domain to an IP, a name to an owner, a package name to its publisher. Decentralizing it (ENS for names, or a package registry with signed, peer-verifiable entries) means no single company can unilaterally reassign, censor, or delete an entry; verification happens against a shared, tamper-evident record instead of trusting one operator's database.
On-chain or peer-verified name/asset registries. Partial overlap. Executables are pushed into the cluster's own content-addressed store and referenced by BLAKE3 digest, optionally with a signed publisher attestation that hosts can require. It is a per-cluster store, not a public registry. Container images are pulled from ordinary registries by digest.