The wallet-scoped portfolio pillar. Obsidian unifies application state across the Trinity and exposes server-enforced shield, burn, and ascension actions in one privacy-oriented surface.
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.
Obsidian aggregates your entire Forge Ecosystem position in one place: ForgeMinerNFT holdings and tier status (ZKP-369), SFD token balance and transaction history (ZKP-216), and Resonance score and event history (ZKP-432). The aggregated portfolio is private by default — accessing the full view requires a wallet-owner signature scoped to the portfolio read action. Unauthenticated requests receive a redacted public view.
From Obsidian, wallet owners can execute all three major token actions in a unified interface: Shield converts a public SFD balance to a Groth16-verified shielded position; Burn permanently destroys SFD (for governance or protocol actions); and Ascension burns the exact required SFD amount to upgrade a ForgeMinerNFT from Tier 3→6, Tier 6→9, or Tier 3→9 in a single atomic operation.
ForgeMiner operators who run physical or virtual compute devices can register and manage those devices through Obsidian. Registered devices are associated with the operator's ForgeMinerNFT and appear in the Obsidian compute-device panel. Device registration is wallet-scoped and operator-only — third parties cannot register devices against an address they do not control.