Skip to content

docs: update for permissionless settlement (drop operator staking)#26

Open
grimnote wants to merge 2 commits into
mainfrom
docs/permissionless-architecture-update
Open

docs: update for permissionless settlement (drop operator staking)#26
grimnote wants to merge 2 commits into
mainfrom
docs/permissionless-architecture-update

Conversation

@grimnote

Copy link
Copy Markdown
Contributor

What

Update the docs to match the protocol's permissionless-settlement architecture. The on-chain operator stack — OperatorRegistry, OperatorSlashingManager, FeeManager, TaskExecutor, CCTPHandler, and the whole orchestration package — was deleted. Settlement is now permissionless: anyone calls CCTPV2EscrowReceiver.settle(message, attestation), secured by Circle's CCTP attestation verified on-chain. "Operators" are now permissionless relayers (no registration, staking, slashing, exclusive claim window, fees, or unbonding); the coordinator is a lightweight burn-notification inbox.

How this was produced

A 21-page audit (one reviewer per page) found every claim falsified by the new architecture and drafted corrections; a second pass applied them, keeping the build compiling. 21 files changed, +491 / −958 — a net deletion of stale operator content.

  • Major rewrites: RunOperator, CoordinatorNetwork, Security, Contracts (removed the Orchestration contract table + GOV-token row + TOC entry), Risk, rss/RssWhatIs.
  • Targeted fixes: Overview, MentalModel, Architecture, Economics, Resilience, Status, CrossChain, GasPerformance, Governance, McpServer, RecourseModule, research/OpenProblems, research/AgenticComposition, rss/RssConformance, rss/RssLicensing.
  • Deliberately kept (still accurate): Recourse LP "staking" of capital; EigenLayer restaking framed as an optional future deep-backstop; zero protocol fee.

Verification

All CI gates pass locally: prettier --check ., eslint, tsc + vite build (1653 modules), vitest. Residual-term grep confirms the only remaining staking/slashing/exclusive window mentions are Recourse LP capital or negations ("no exclusive window").

Follow-up: Codex polish (docs only)

This PR fixes accuracy. Prose polish — smoothing the seams left by the deletions, normalizing "relayer" terminology, tightening the rewritten paragraphs, auditing StatusBadge status="spec" usage — is handed to Codex via CODEX-DOCS-POLISH.md (included here). That brief defines a separate, prose-only polish PR that must not change any facts and must keep all CI gates green.

🤖 Generated with Claude Code

grimnote and others added 2 commits June 27, 2026 18:14
Align the docs with the protocol's permissionless-settle architecture: the
on-chain operator stack (OperatorRegistry, OperatorSlashingManager, FeeManager,
TaskExecutor, CCTPHandler, the orchestration package) was deleted; settlement is
permissionless via CCTPV2EscrowReceiver.settle(message, attestation), secured by
Circle's CCTP attestation verified on-chain. 'Operators' are now permissionless
relayers (no registration, staking, slashing, exclusive claim window, fees, or
unbonding); the coordinator is a lightweight burn-notification inbox.

21 pages updated. Major rewrites: RunOperator, CoordinatorNetwork, Security,
Contracts (removed the Orchestration contract table + GOV-token row), Risk,
RssWhatIs. Targeted fixes across Overview, MentalModel, Architecture, Economics,
Resilience, Status, CrossChain, GasPerformance, Governance, McpServer,
RecourseModule, research/*, rss/*. Recourse LP 'staking' and EigenLayer-restaking-
as-future are retained (still accurate).

tsc + vite build + eslint + prettier + vitest all green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Brief for the Codex docs-only polish PR: smooth the seams left by the
architecture-accuracy deletions, normalize 'relayer' terminology, tighten the
rewritten prose, and audit StatusBadge 'spec' usage — without changing any
facts. Includes the canonical architecture context and the CI acceptance gates.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@grimnote grimnote requested review from a team, 0xkkkn and VladVelik as code owners June 27, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant