Describe 1.0.0-alpha.12 and bring the SDK test count to 201
The agent's blind signChallenge is gone in 1.0.0-alpha.12 (pull request 107,
released by 108). A call does not compile in TypeScript, and in JavaScript it
throws an error that names signChallengeFor.
The pages that describe the SDK now say 1.0.0-alpha.12 and list the removal as
new since alpha.11. Where a page said that signChallenge signs whatever it is
handed, it now says that the method is removed and that alpha.9 has only it.
The exported function signChallenge(payload, secretKey) is unchanged and stays
where a page shows it. The class diagrams drop the method, and the sequence
diagrams and the flowchart that showed an agent calling it show
signChallengeFor(payload, audience) instead. The Home page names main 3e8faed.
The SDK suite is 201 tests, not 197: 193 run and 8 skip without a live
deployment, in 13 files, measured with CI=1 on a clean export of main 3e8faed.
Six pages carried the old number.
62 replacements on 24 pages. 20 diagrams changed; all 532 still parse and the
20 render without an error or a clipped label.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Make the line numbers in the link labels match the anchors again
59 source links had a label whose line numbers no longer matched the anchor
that the previous commit moved. The label now takes the anchor's range. Only
the text between the square brackets of a link changed: the URLs are
byte-identical and everything outside the labels is unchanged.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Move the source-link anchors from main 58d6b27 to 3e8faed
Main moved by three commits: the test counts (ecc3dfa), the removal of the
agent's blind signChallenge (9c38a44) and the 1.0.0-alpha.12 release (3e8faed).
59 line anchors on 16 pages moved: 37 into packages/sdk/src/agent.ts, 20 into
packages/sdk/README.md and 2 into docs/ai-frameworks.md.
Only the digits of an anchor changed. With every anchor replaced by #L, the old
and new text of each page is identical, and the line endings are unchanged.
Four ranges (eight anchors) have a first or last line that changed in the move:
two in agent.ts, whose last line, the return of the removed method, is now the
end of the stub that throws, and two in README.md, whose last line is the test
count paragraph reworded on 29 October. They keep pointing at the same part of
the file.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Describe the three merged changes and bring the test counts to 29 October
Pull requests 103, 104 and 105 change what the pages say.
The oracle answers 202 with durable false for a flag, a resolve and a link when
the state file cannot be written, as it already did for an attestation, and
counts them in sigvara_oracle_writes_not_durable_total. The monitoring, API,
flag and deployment pages say so.
The renounce phase refuses a timelock with a delay under 48 hours, one the Safe
cannot propose to or cancel on, one that not everyone can execute on or that the
Safe or the deployer administers, a timelock address with no code, and a Safe
with a threshold under 2. Governance and Deployment Strategies list the errors
and what to do about each. The deploy script now records the block it starts at
as deployBlock, and the role replay starts there.
The attestation page says why one confirmation is enough on Arc, as Arc's
documentation states it, and why the scan keeps six. The pages that describe the
alpha.9 key leak say that a key that was ever logged or serialized should be
treated as exposed and rotated.
Test counts follow main 58d6b27: 698 contract tests (691 run without a fork
URL), 784 oracle and 197 SDK. The Home page names 58d6b27.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Say that the SDK pages describe 1.0.0-alpha.11 and that the audience is required
alpha.11 reached npm on 29 October 2026 from main ff0fa68, and its tarball hash matches a local
pack of that commit. verifySignature now requires the expected audience: a call without it throws,
and a v1 payload is always refused. The opening paragraph of each SDK page names the version it
describes and says what is new since alpha.10. The pages that treated the audience as optional
("if an expected audience is provided", "audience?") no longer do, in the text and in seven
diagrams (all 532 diagrams parse and the eight changed ones render). The SDK test count follows
the new tests: 197 in 13 files, 8 of which skip, measured with CI=1 on a clean copy of ff0fa68.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Drop the unreleased marks from the SDK pages
alpha.10 is on npm, so the marks that called its changes unreleased come off 14 pages (112
edits). Where a mark carried a contrast with alpha.9, the contrast stays without the word
unreleased ("alpha.9 has only signChallenge"). Where a sentence said "on main" only to set a
behaviour apart from the npm release, those words go. The not_active lists read as they did
before the marks went in: unbonded (or bonded below the minimum stake in force now),
suspended, or slashed. The two notes on the future-date refusal now say that alpha.9 still
accepts a payload dated ahead.
All 532 Mermaid blocks still parse, and the three that changed render.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Bring the wiki in line with main 1e5d833 and fix two diagrams
An oversize request body is answered 413 now, and the API Reference said the oracle drops the connection.
The test counts and invariant suites moved: 665 contract tests, 19 invariants in five suites, 760 oracle
tests, and CI typechecks the SDK's tests. The Home page names the commit it was checked against.
Key Management and Rotation: a subgraph and one of its nodes were both called Tests, which current Mermaid
refuses to render ('Setting Tests as parent of Tests would create a cycle'). The node is IdentityTests now.
SDK Overview and Setup: a node and a subgraph were both called Contracts, so the node's label was lost.
The edge points at the subgraph, which carries the label.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Make each source link's label show the lines its anchor points at
A label such as verifier.ts:15-209 was written from the tree the wiki was generated from, and the anchor
behind it was moved to main later, so the two disagreed on 3,871 links. With an anchor, the label now takes
the anchor's range (the wiki writes 'to the end of the file' as one past the last line, so the label is
clamped to the file). A label with numbers and no anchor linked the whole file and claimed a range nothing
backed, so 414 of those lose their numbers. Link targets are untouched.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Bring the wiki in line with the code on main
Rewrote the prose of 74 of the 75 pages against main at d8e44c2, and marked
what the Arc testnet proxies, which still run the September 2026
implementations, do differently. Each page was read again against the code
by an independent reviewer, and every finding was checked before it was
applied.
Notable corrections: the admin, not the committee, rules on disputes and an
upheld ruling waits for the challenge deadline; a slash nobody executes can
be lapsed by anyone 14 days after its deadline; the outcome in an evidence
leaf is not on chain; meetsThreshold ignores status and bond; the archived
SVR sale and vesting contracts are not the mainnet design; SDK changes
after alpha.9 are marked as unreleased.
Also fixed four Mermaid diagrams that did not parse. All 532 diagrams now
parse, and every source link resolves against main.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Fix dead source links and move line anchors to main
1,755 source links carried a stray Sigvara-main/ path segment and returned 404; the segment is removed. Two links were malformed by hand (a space inside packages/sdk, a stray character inside test/E2E.t.sol) and are repaired.
The line anchors were taken from the tree the wiki was generated from (main at f852051, 2 October 2026). Each one is now mapped to the current main through the git diff: 3,788 land on the same code they started on, 312 sit on code that changed and are approximate, 413 pointed at code that no longer exists and become plain file links, and 488 are in files that did not change. No prose is changed in this commit.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Publish the repository wiki, edited for a reader rather than a generator
73 pages generated from the source tree at f852051, plus a landing page and a
sidebar. Three changes were needed before any of it was fit to publish.
5,591 citation links pointed at `file://` paths, which resolve to nothing on a
wiki. Repointed at the repository, line ranges intact, so every claim on a
generated page can be checked against the code it came from. That turns the
densest thing about these pages into the most useful.
124 placeholder lines reading "[No sources needed since this section provides
general guidance]" are generator scaffolding and are gone.
One claim was misleading rather than wrong: System Overview said payment
scanning is off by default, which is true of the shipped default and not of this
deployment, where it has been on since 3 October. Now says both.
Flattened from nine nested sections into page names, since wiki pages are
addressed by name. No collisions, and the generator never cross-linked pages, so
nothing broke: 75 pages, zero broken internal links.
The landing page is written rather than generated. It leads with what the
protocol is, the six factors and their caps, what has actually been proven on a
live deployment, and what has not — no audit, admin rights still on a deployer
EOA, both operators run by the same party. It also says these pages are derived
and that the code and `docs/` win where they disagree, because a generated wiki
drifts and readers should know which half to trust.
The `.qoder/repowiki/knowledge` tree is deliberately not published: ten pages of
tool-internal notes carrying `kind:` and `scope:` frontmatter and source paths
prefixed `Sigvara-main/`, written for a machine rather than a reader.