Go-Friendly: Leverages Red Hat’s FIPS-validated Go for regulated components.
No Regressions: Internal DAG/zkDID still use modern crypto (Ed25519).
FIPS Readiness: Flip `--fips-mode` to switch to ECDSA P-256/SHA-256 for compliance.
Zero Bloat: STROBE and other experimental features are compile-time optional.
FIPS mode: Only NIST-approved algorithms (ECDSA P-256, SHA-256).
Innovation dies,
Corruption thrives,
And people never see the full benefit of digital public goods.
B1[DIDs with Transparency]
B2[Ed25519 + Dilithium]
B3[VDF Anti-Sybil]
↓
Protocol RPC API
↓
Payment Channel Manager + zkProver
↓
DAG Consensus with VDF Finality
↓
SMT State Storage + MerkleLog Audit
Triggers compute on DAG node (e.g., image classifier WASM)
Result → signed and stored in DAG
Access → governed by SMT policy (e.g., only followers can see)
Audit logs → shown to user, cannot be tampered with
No AWS usage needed
Networking: We argue that Neogrid's use of Libp2p with zk-namespaced overlay nets provides stronger security guarantees than AWS VPC's logical segmentation by cryptographically enforcing every network hop.