This document specifies the lottery that assigns per-slot sequencing authority in the Permissionless Channel Sequencing Proposal: VIII Gives a lottery description that:
- (a) reuses channel notes as sequencing weight
- (b) does not disclose L1 leaders’ identities
It also surveys the academic and industry literature against the design’s open problems (section 5).
Labels E1-E6 refer to the seeded experiments summarized in section 3.
Summary of the recommendation
The proposed lottery reuses the L1’s own leader-election machinery with the minimum modification that publicness requires:
- eligibility is the L1’s aged-note rule applied verbatim; participation is an explicit declaration
- the winning condition is the L1’s own probability function evaluated per note
- the ticket is the L1’s ticket with the secret key removed and a changed domain tag
This construction is preferred over the alternatives at multiple layers:
- implicit all-notes participation, because passive stake taxes throughput and conscripts depositors (experiment E6, section 3)
- VRF or ZK tickets, because both add cryptographic machinery the platform does not have, while the public ticket costs only one hash and keeps winners attributable (which links to punishment, see section 4)
-Any custom aging window, because only the L1’s exact snapshot discipline preserves the grinding argument the L1 already relies on
A slot win authorizes the full channel block, transfers and corrective reversals included, with the aged withdrawal release proposed as the one holder-authorized, slot-free operation (propose substrate amendment, section 4).
Winner privacy is an non-goal for channel sequencing: attribution is what makes two-sided incentives possible, and the anonymity requirement (as said above) is met cryptographically, and note-identity and network-layer residuals stated in 2.5.
1. Requirements, Constraints
- Weight = channel notes.
- Sequencing weight is the channel’s deposited notes, per the substrate introduced by Channel Participation in PoS (Mantle specification, v1.9.0)
- CHANNEL_DEPOSIT and CHANNEL_TRANSFER each consume their inputs and create new notes (a new NoteId; the note’s aging restarts), while CHANNEL_WITHDRAW keeps the NoteId of the notes it releases and never resets aging
- A deposited note therefore ages inside the channel before it can play, which the 2.1 rule relies on
- No L1 leadership disclosure.
-Participating in or winning the channel lottery must reveal nothing about L1 leader elections, whose privacy the Proof of Leadership (PoL) design protects deliberately
- L1 minimalism.
- The L1 validates channel operations against simple public rules; it hosts no dispute logic.
- Exits follow the aged-withdrawal design described in Proposal VIII: a withdrawal preparation transfer resets note age, the note ages to maturity, and the release is checked by the L1 against age alone.
- Per-channel rate.
- Each channel configures its lottery rate f (the fraction of slots that produce a block), bounded by the analysis in 2.6.
- Existing cost classes.
- Validation must stay inside the platform’s existing gas classes (gas cost analysis) no proof systems beyond those already deployed
2. Design
2.1 Eligibility: aged channel notes using L1’s rule
A note may play slots of epoch N if both
- It exists, unspent now
- It was present in the ledger snapshot taken at the first slot of epoch N-1.
This is reused from the L1 PoL (Cryptarchia protocol: the Eligible Leader Notes Commitment, C_LEAD; Proof of Leadership: membership in ledger_AGED and ledger_LATEST), applied to channel notes without alteration.
The channel ticket (2.4) is computed from public data (so its grindable inputs are the note identifier and the channel identifier).
-
The epoch randomness eta for epoch N is determined roughly 60% of the way through epoch N-1; the snapshot precedes that determination by 4.5 days under current constants (an epoch is 648,000 one-second slots, exactly 7.5 days).
-
The inputs for the lottery is therefore committed before the randomness it will be evaluated against exists
- Re-shaping a note requires spending it, which restarts the aging wait, so grinding is structurally one epoch behind.
- Any shorter or custom aging window would break this ordering and re-open grinding!