Hello BGIN - My name is Christian - I go by the moniker flaxscrip on many platforms. I live in the south-eastern United States and have been working on non-financial crypto solutions since 2015. My current focus is on the intersection of identity + decentralization + zero knowledge. Over the last 3 years I’ve been focused on the development of an identity platform named Archon.
**
Archon** is a peer-to-peer, open-source decentralized identity protocol implementing the did:cid method. Identities are content-addressed and self-certifying: no server, registry, or company can alter, revoke, or rent your DID without holding your keys.
Four properties that matter for cybersecurity governance
Peer-to-peer. Nodes synchronize over Hyperswarm and IPFS. No central infrastructure, no DNS dependency, no service provider lock-in. Any participant runs their own Gatekeeper (validation) and Keymaster (key management) on commodity hardware — a Raspberry Pi suffices.
Open. MIT-licensed reference implementation in TypeScript, with native Python (Keymaster) and Rust (Gatekeeper) flavors. Conforms to W3C DID Core 1.0, W3C VC Data Model v2, and W3C JWE for credential encryption. Universal Resolver–compatible.
Free. DID creation is instantaneous and zero-cost — the identifier is the content hash of a canonicalized creation operation pinned to IPFS. Updates can be local-only or registered to a registry of the controller’s choice; the user pays only when they want stronger finality.
Blockchain-agnostic. Per-DID registry selection at creation: Hyperswarm (P2P gossip, eventual consistency, free), Bitcoin (strong finality, batch-anchored, ≈$0.001 per batch), Feathercoin (cheap settlement), or local-only (private testbeds). Registries mix freely within a single ecosystem, and a DID can migrate between tiers without identity loss. We are looking into mediating with the ZCash network as well.
What this gives a cybersecurity audience
A sovereign identity layer that does not rely on any single chain, government, or company. Cryptographic provenance for every operation (Ed25519 / secp256k1 signing, content-addressed binding). Deterministic, independently-reproducible resolution: each Gatekeeper materializes the current DID document from the registry’s update chain locally — no consensus dependency for read paths. Time-travel resolution lets verifiers check credentials issued under prior key states without trusting the issuer’s current state.
Code: github.com/archetech/archon (MIT) ·
Spec: archetech.com/protocol.html