@metalabel/dfos-protocol

Cryptographic identity and content proof — Ed25519 signed chains, content-addressed CIDs, W3C DIDs. The protocol knows about keys and document hashes. It doesn't know about posts, profiles, or any application concept.

Install

npm install @metalabel/dfos-protocol

Usage

// Chain verification
import { verifyContentChain, verifyIdentityChain } from '@metalabel/dfos-protocol/chain';
// Crypto primitives
import { createJws, dagCborCanonicalEncode, verifyJws } from '@metalabel/dfos-protocol/crypto';
// Merkle trees
import { buildMerkleTree, verifyMerkleProof } from '@metalabel/dfos-protocol/merkle';

Subpath Exports

Export	Description
`@metalabel/dfos-protocol/chain`	Identity and content chain signing, verification, beacons, countersigns
`@metalabel/dfos-protocol/crypto`	Ed25519, JWS, JWT, dag-cbor, base64url, ID generation
`@metalabel/dfos-protocol/merkle`	SHA-256 binary merkle tree, inclusion proofs

Specifications

Document	Description
PROTOCOL.md	Core protocol — chains, signatures, verification, test vectors
DID-METHOD.md	W3C DID method specification for `did:dfos`
CONTENT-MODEL.md	Standard content schemas (post, profile, manifest)

Examples

The examples/ directory contains deterministic reference chain fixtures that can be independently verified by any Ed25519 + dag-cbor implementation:

identity-genesis.json — single create operation
identity-rotation.json — genesis + key rotation
identity-delete.json — genesis + delete (terminal)
content-lifecycle.json — create + update (with both documents)
content-delete.json — create + delete

License

MIT