Visualize how the Forge Ecosystem fits together — the six pillars, the Harmonic Trinity token standards, and the flows that connect identity, fuel, and reputation.
Live application state and user actions are enforced by the Express service and its PostgreSQL database. The Solidity contracts deployed to Sepolia are reference implementations, not the live runtime execution path.
The Forge Ecosystem is composed of six interlocking pillars, each with a distinct role. Calyx (Entry Vector) handles project onboarding and IDO launches. ForgeGATE (Security Layer) runs audit and certification. Obsidian (Wallet-Scoped Portfolio) unifies application portfolio and protocol actions. SignalForgeDAO (Governance Engine) manages proposals and treasury. ForgeMiner (Infrastructure License) anchors identity and storage. Crucible (Liquidity Layer) provides server-enforced swaps, LP management, and a local bridge simulation. The diagrams show data flows, API boundaries, and how the pillars share the Harmonic Trinity token layer.
The Trinity diagrams trace how value and state move across the three token standards. ZKP-369 (identity) determines what activities are available to a participant. Those activities generate ZKP-432 Resonance (reputation) and ZKP-216 SFD (tokens). Accumulated SFD is burned to ascend the ZKP-369 tier, and Resonance gates the highest ascension tier and determines DAO voting weight. The diagrams annotate each flow with its runtime enforcement mechanism or deployed contract reference.
The architecture diagrams distinguish the live runtime (PostgreSQL + Express) from the deployed Sepolia contract references. The five Solidity contracts — PoseidonVerifier, ZKP216SFD, ZKP369ForgeMiner, ZKP432Resonance, and HarmonicAscension — are shown with their deployment addresses as references. Live application state and user actions are enforced by the Express service and its PostgreSQL database. The Solidity contracts deployed to Sepolia are reference implementations, not the live runtime execution path.
Spoofing: a forged ZK proof submitted to claim ForgeMiner (ZKP-369) storage rewards without holding data is rejected because every Groth16 proof is verified per challenge epoch by the live service; session hijacking during validator challenge-response is mitigated by SIWE nonce-based sign-in with server-side nonce rotation and rejection of stale challenges. Tampering: a validator altering chunk hashes post-commit to fake Merkle storage-proof integrity is caught because the runtime stores the Merkle commitment and re-verifies per-chunk paths; DB-level tampering with ForgeGATE audit scores is detected because scores are deterministic (SHA-256 of contractAddress + id), so a re-run reproduces the identical value.
Repudiation: a voter denying a cast SignalForgeDAO vote can be checked against the voterAddress and blockTimestamp persisted in PostgreSQL; normal application routes do not expose vote mutation, but the operator still controls the database. A validator disputing a slash can inspect the challengeId, slashBlock, slashReason, and Explorer audit trail. Information Disclosure: cross-user ZKP-216 balance leakage via enumeration is prevented because balance endpoints require an explicit address parameter with no unscoped global dump; raw Calyx KYC documents are never persisted server-side — only an attestation boolean is stored.
Denial of Service: flooding the ZK proof-generation endpoint with oversized circuit inputs to exhaust CPU is mitigated by a 10 req/min per-IP rate limit, 30-second job timeouts, and rejection of oversized inputs; a Crucible swap storm designed to drain a liquidity pool and manipulate oracle pricing is mitigated by per-address swap rate limits, server-enforced slippage tolerance, and a pool-depth floor. Elevation of Privilege: an unauthenticated PATCH attempting to self-approve an unreviewed Calyx project is blocked by a CALYX_TRANSITIONS allowlist and a mandatory KYC gate; a governance attack that accumulates ZKP-432 resonance to force through a malicious DAO treasury spend is mitigated by a 33% quorum plus 51% approval threshold, a 48-hour treasury time-lock, and non-transferable, earned-only resonance.