obscura-primary-sources-2026-05-13

Obscura primary sources

Reviewed: 2026-05-13 UTC

Core project framing

• https://github.com/obscura-finance
  • Organization profile page with the clearest short-form statement of Obscura as a verifiable reputation layer for DeFi and a phased roadmap from centralized MVP to decentralized oracle and prover networks.
• https://raw.githubusercontent.com/obscura-finance/.github/main/profile/README.md
  • Canonical profile README; useful for the high-level pitch around privacy-preserving social trading, ZK proofs, TEEs, decentralized oracles, and the Horizen-backed roadmap.
• https://medium.com/@obscuraprotocol/announcing-obscura-building-the-verifiable-reputation-layer-for-defi-741de78578d8
  • Announcement post that frames the original product thesis and the early AWS Nitro Enclaves-based architecture language.

Technical architecture and implementation docs

• https://github.com/obscura-finance/documentation
  • Main documentation repository.
• https://raw.githubusercontent.com/obscura-finance/documentation/main/README.md
  • Best table-of-contents source for Obscura’s service decomposition: Sentinel, Citadel, Conductor, Alchemist, on-chain verification, B2B APIs, and supported exchanges.
• https://raw.githubusercontent.com/obscura-finance/documentation/main/01_PRIVACY_ARCHITECTURE_OVERVIEW.md
  • Strongest short document for the core analytical split between credential protection, ZK performance verification, data isolation, and future decentralized attestation.
• https://raw.githubusercontent.com/obscura-finance/documentation/main/03_ZK_IMPLEMENTATION.md
  • Most concrete technical source for the proving layer: Noir circuits, BN254, Honk, Poseidon-based commitments, queue-based PnL accounting, 10-trade batch limits, and deployed Horizen testnet verifier / protocol contracts.
• https://raw.githubusercontent.com/obscura-finance/documentation/main/06_PROTOCOL_WHITEPAPER.md
  • Best source for distinguishing what exists now from roadmap claims; explicitly says Sentinel is still a single FastAPI service and Alchemist is still a single prover while DON / MPC / prover-market layers remain future phases.
• https://raw.githubusercontent.com/obscura-finance/documentation/main/07_B2B_INTEGRATION_GUIDE.md
  • Shows Obscura is not only a proof layer but also a white-label copy-trading control plane with pools, signals, subscriptions, queueing, risk modes, and tenant isolation.

Whitepaper artifact

• https://drive.google.com/file/d/11idbG1itLzy922oIIy_d9BXlnVlgQEAY/view?usp=sharing
  • Linked full PDF whitepaper artifact referenced from official materials.

Main takeaways from this pass

• Obscura is most useful as a comparison point when split into five layers: exchange-data ingestion, credential custody, ZK proof generation, on-chain reputation anchoring, and downstream copy-trading distribution.
• The strongest reusable mechanism is not generic zk reputation; it is proof-backed trading reputation built from private offchain exchange activity and exposed as a more portable onchain record.
• The docs are unusually explicit about present-versus-future architecture, which helps avoid flattening roadmap rhetoric into already-deployed decentralization. Today’s stack still relies on centralized Sentinel ingestion and a single Alchemist prover.
• The confidential-compute layer has already changed over time. Early public materials emphasize AWS Nitro Enclaves, while the later technical docs say the current Citadel production stack runs on Nillion nilCC with AMD SEV-SNP after earlier Nitro and Evervault phases.
• The B2B guide materially changes how Obscura should be categorized: it is not just a trader-profile or score protocol, but a multi-tenant execution and distribution rail for white-label copy trading.
• Obscura belongs in comparisons with Nomis, Omnid, OpenRank, and Orange on the reputation side, but it also needs comparison against social/copy-trading infrastructure because its reputation output is directly tied to follower execution and pool administration.