Skip to content

Commit

Permalink
fix README links
Browse files Browse the repository at this point in the history
Signed-off-by: Dave Huseby <[email protected]>
  • Loading branch information
dhuseby committed Apr 7, 2024
1 parent 47e0c70 commit 8df1723
Showing 1 changed file with 14 additions and 11 deletions.
25 changes: 14 additions & 11 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ specifications linked above.
A VLAD is intended to replace public keys as identifiers in distributed systems
by combinind a random nonce (i.e. number used once) and a CID for a WASM
verification script designed to run in an implementation of the web assembly
cryptographic constructs (WACC) VM. The nonce in the Vlad can be random but in
cryptographic constructs [WACC VM][WACC]. The nonce in the Vlad can be random but in
some use cases the bytes inside the nonce are a [Multisig][MULTISIG] digital signature
over the CID part of the VLAD. Digital signatures are random enough to serve
the purposes of making the VLAD unique while also cryptographically linking the
Expand All @@ -30,18 +30,21 @@ feature for linking VLADs to provenance logs.
Briefly, the reasons why distributed systems should use VLADs instead of public
key identifiers is because key material is subject to compromise and rotation.
Distributed systems that rely on public key identifiers (e.g. web-of-trust, all
other decentralized identity systems) are brittle because whenever keys change
the links between the systems break. Public keys are typically used because
they are random enough to number a seemingly infinite number of things without
running out and they are also a cryptographic commitment to a validation
function that can be used to verify the data they are identifying. VLADs have
both of these properties but are not derived from key material and are
therefore not subject to compromise or rotation. That makes them much more
resilient and stable distributed system links over long spans of time.
other decentralized identity systems) are brittle and the resulting distributed
system does not meet the preconditions for a metastable network to emerge.
Whenever keys change, the links between the nodes break. Public keys are
typically used because they are random enough to number a seemingly infinite
number of things without running out and they are also a cryptographic
commitment to a validation function that can be used to verify the data they
are identifying. VLADs have both of these properties but are not derived from
key material and are therefore not subject to compromise or rotation. That
makes them much more resilient and stable distributed system links over long
spans of time.

[CRYPTID]: https://cryptid.tech/
[PROVENANCE]: https://github.com/cryptidtech/provenance-specifications/
[MULTIFORMATS]: https://github.com/multiformats/multiformats
[MULTIFORMATS]: https://github.com/multiformats/multiformats/
[CID]: https://docs.ipfs.tech/concepts/content-addressing/
[VLAD]: https://github.com/cryptidtech/blob/main/specifications/vlad.md
[MULTISIG]: https://github.com/cryptidtech/multisig
[WACC]: https://github.com/cryptidtech/wacc/
[MULTISIG]: https://github.com/cryptidtech/multisig/

0 comments on commit 8df1723

Please sign in to comment.