background gif

Rosario construction · Ceremony overview

How Rosario works

Rosario is the interactive proof method behind ENI6MA authorization. You prove you know the map by picking the right zones under fresh entropy, not by typing a reusable password onto the channel.

Jump to formal section

~8 min overview · ~5 min formalContinue: Ambiguity by design

What Rosario is

Think challenge → respond → envelope → burn → verdict. A prover and verifier share a compiled private relationship. Each round presents a fresh public challenge geometry. The prover answers with membership-only witnesses. The verifier accepts without the secret map appearing on the channel.

Challenge · witness · burn · twin verdict

Follow the five-stage flow: fresh challenge, local private map, bearing witnesses on the public channel, burn nonce, twin verdict. The eavesdropper watches only the channel strip; the private map never leaves the vault. Takeaway: membership is proven once, then authority dies at burn.

Roles: Peggy, Victor, Eve

Peggy

The prover. Holds the private map locally, does membership work, never publishes φ.

Victor

The verifier. Checks the matched twin outcome for this event: accept or reject without learning the map.

Eve

The observer. Sees only the channel: challenges, bearings, verdicts. Recording is not learning.

Round anatomy (model, not manufacturing recipe)

Information-flow language only. This is a mental model, not a manufacturing guide, not a claim chart, not a patent figure clone.

  1. 1. Fresh challenge geometry

    Each round presents a new public layout. Yesterday’s answers do not authorize today.

  2. 2. Private map stays local

    The sealed relationship lives inside the twins. It is never typed onto the channel as a reusable password.

  3. 3. Bearing witnesses only

    The prover answers with membership evidence (public bearings) not with the legend that produced them.

  4. 4. Twin check

    The verifier twin checks that the work matches the sealed relationship for this event.

  5. 5. Nonce burn

    Freshness is spent before the verdict sticks. Replay dies at the ledger, not at wishful thinking.

What crosses the channel vs what never does

May cross the channel

  • Public challenge C and freshness tags
  • Bearing witnesses
  • Request-bound envelope material
  • Allow / deny verdict residue

Never on the channel

  • Private map φ
  • The sealed twin relationship itself
  • Reusable ambient authorizers (password / bearer token style)
  • Manifold manufacturing recipes: those are not this page

Why observers stay confused about which secret fits: Ambiguity by design. Why identity deploys as a matched pair: Identity in twin circuits.

Vs normal crypto: ITS authorization vs engineering crypto

Rosario’s authorization claim targets empty mutual information on the transcript under stated axioms. Engineering may still use BLAKE3, AEAD, or TLS for integrity and transport. Say it once: not everything in the stack is information-theoretic.

If someone records the channel

Eve sees challenges, bearings, and verdicts, not φ. Recording is not learning under the model. Why observers stay confused about which secret fits: Ambiguity by design.

Relation to product Gate order

The eight-stage Gate order is where ceremony meets enforcement: reserve, bind, burn, validate. The proof method is Rosario; shipping checks live on Security. Stack and binaries: Engineering stack.

Formal objects and Channel Zero claim

Private morphism φ, public challenge C, bearing witnesses, freshness tau / nonce (notation). The Channel Zero claim:

Rosario transcript leakage

Read as: Given the public challenge, Rosario's observable ceremony transcript reveals no mutual information about the hidden state.

Arguments

X
: hidden state: private morphism, selected zones, and local knowledge
O
: observable bearings and public transcript emitted during the ceremony
C
: public challenge geometry for the event
\tau
: freshness tick or nonce binding the ceremony to one session
\phi
: private morphism that stays off-channel

Operators

I
: mutual information
\mid
: conditioning on the challenge
= 0
: zero observer-effective leakage in the model

Significance: This turns the Rosario ceremony into a transcript-leakage statement: the prover acts, but the public record does not become a reusable credential.

Computational contrast: Rosario is judged by transcript leakage and session binding, not by the cost of recovering a reusable key from the public record.

References:Channel ZeroSession binding

Public foliation wheels

Read concentric wheels as public foliation layers around a private map that never enters the channel. Outer rings are challenge and witness structure; the core stays sealed. Takeaway: ceremony geometry is public while membership knowledge stays local.

  • P1

    Private map sealed: authorization without exporting φ.

  • P2

    Uniform public symbols: no frequency compass on the transcript.

  • P3

    Empty mutual information about the secret given the challenge.

  • P4

    Freshness and burn: spent nonces do not return.

Full pillar language: Axioms, theorems, and bounds. Papers: Rosario–Wang Formalism. Scope: Claims.

Demo note: in-browser ceremony UIs may be visual demo only, shipping proofs run against compiled twins. Try Demos.