From 489854a9caeb9073c4ec7565e46954d3063e8db1 Mon Sep 17 00:00:00 2001 From: memosr Date: Sun, 7 Jun 2026 13:44:03 +0300 Subject: [PATCH] docs(specs): challenger description mentions challenge as well as nullify MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The challenger.mdx frontmatter description said the challenger "submits dispute transactions on L1 to nullify them", but the spec body documents two distinct transaction types: - nullify() — referenced at lines 26 and 57 - challenge() — referenced at lines 148-149 The challenge() path is a first-class part of the challenger role, not a secondary action. Omitting it from the description misleads anyone reading the page header or navigating from a sidebar preview into thinking nullification is the only mechanism. Updated the description to mention both paths. --- docs/base-chain/specs/protocol/proofs/challenger.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/base-chain/specs/protocol/proofs/challenger.mdx b/docs/base-chain/specs/protocol/proofs/challenger.mdx index 4262e8a10..90dbdd691 100644 --- a/docs/base-chain/specs/protocol/proofs/challenger.mdx +++ b/docs/base-chain/specs/protocol/proofs/challenger.mdx @@ -1,6 +1,6 @@ --- title: "Challenger" -description: "Specification of the challenger, an offchain service that detects invalid AggregateVerifier games and submits dispute transactions on L1 to nullify them." +description: "Specification of the challenger, an offchain service that detects invalid AggregateVerifier games and submits dispute transactions on L1 to challenge or nullify them." --- The challenger is an offchain service that protects the proof system by independently checking