The content pipeline. On-chain we store only a content commitment (never plaintext), the level, the authorizing editors, and the published cast id — the §18/§33 audit log.
Contract statusNot configured (seed preview)
On-duty editor0xc3c3…c3c3
Your roleMember
On-chain contracts are not configured. Set NEXT_PUBLIC_MEDIA_GOVERNANCE and NEXT_PUBLIC_EDITORIAL_REGISTRY to enable live reads and write actions. The content below is illustrative seed data.
Submit a draft — only the keccak256 commitment of your content goes on-chain; plaintext stays off-chain until publish.
Connect a wallet on Base (with contracts configured) to submit.
Submission queue
Community-submitted drafts. An L1 community submission needs just 1-of-5 editor authorize (curation already passed); L2 submissions still need the L2 threshold.