Skip to main content

System Overview

This section situates the platform in its operating context and describes the major containers and their responsibilities at a glance. The design is intentionally web3‑first: there is no traditional web2 backend in the reader request path. Frontends interact directly with on‑chain modules and decentralized storage, aided by identity providers and content delivery infrastructure that preserve a familiar, low‑latency experience.

Containers and responsibilities​

Frontends

  • Three clients deliver the core experience: Reader (content discovery and consumption), Creator/Journalist (publishing, licensing, earnings), and Investigator (bounties, secure exchanges, resolution). Clients verify on‑chain entitlements locally and retrieve content from CDN/Walrus.

On‑Chain

  • Purpose‑built modules on Sui in Move: Kiosk policies for content licensing and royalties; entitlement objects for access; bounty escrow for deposits, payouts, and slashing; pseudonymous reputation objects for durable accountability.

Storage & Delivery

  • Media is stored on Walrus and fetched via aggregator endpoints; a CDN serves as primary delivery with Walrus fallback. DNS provides domain resolution without introducing a central backend.

Identity

  • Users authenticate with wallets or through zkLogin, and sponsored transactions remove gas barriers to onboarding while preserving user control.

AI Oracles

  • Confidential computation runs inside AWS Nitro Enclaves (Nautilus‑style) to produce attested results; privacy‑preserving analytics may use Seal; zkTLS proves properties of TLS sessions. Receipts are anchored on Sui and consumed by on‑chain logic where required (for example, market resolution or reputation updates).

User-Specific System Views​

The platform serves three distinct user types with different technical architectures:

Reader System Architecture​

Readers experience a web2-like interface with web3 benefits hidden beneath:

Journalist System Architecture​

Journalists interact with blockchain directly for content monetization:

Source System Architecture​

Sources operate through maximum privacy and security layers:

Interaction summary​

  • Readers operate through zkLogin and sponsored transactions for frictionless access, with entitlements verified client-side
  • Journalists use wallets directly to manage content NFTs, configure royalties, and create investigation bounties
  • Sources access the platform anonymously through Tor, submitting encrypted materials via Seal's threshold encryption
  • Identity providers enable seamless login and gas‑less transactions without placing a web2 backend in the content path
  • AI Oracles enrich decisioning by emitting verifiable receipts consumed on‑chain; they do not sit in the hot path for standard reads