Skip to content

History / Home

Revisions

  • Say which main the wiki was last checked against: 2b4ce3c

    @RunTimeAdmin RunTimeAdmin committed Nov 3, 2026
  • Correct what a review of the status prose found

    @RunTimeAdmin RunTimeAdmin committed Nov 3, 2026
  • Describe the event index, the adversarial slash drill and what the checker proposes

    @RunTimeAdmin RunTimeAdmin committed Nov 3, 2026
  • Describe SDK 1.0.0-alpha.15: the MCP trust server, evidence roots and the new reads 28 replacements on 20 pages, each asserted to match once: - The SDK pages describe 1.0.0-alpha.15, published to npm on 3 November 2026, with what is new since alpha.14: sigvara-mcp, the evidence-root functions and the verifier reads for a trust check. - MCP Gated Tools gains a section on the other direction, sigvara-mcp: its tools, the gate's rule without the proof, why the proof tools need an audience the agent can check, and which addresses to pay. - Verifier Functions no longer says the SDK leaves Merkle proofs to the oracle; the evidence pages name the SDK functions and the MCP tool. - SDK tests: 300 in 16 files, with mcp.test.ts and evidence.test.ts described. - Home names main b6baabd. Checks: 5,785 source links and 4,611 anchors resolve in main b6baabd, 86 internal links resolve; 0 CR bytes; no long dash in new text; all 532 Mermaid blocks parse and the changed one renders. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Nov 3, 2026
  • Correct seven points a review of the prose found A separate read of the previous commit against main 700a3ee checked about 350 claims and found these, now fixed on 23 pages: - SplitAuthorityFork skips twelve tests, not seven, on the four pages that still said seven. - The tag arc-testnet-2026-11-02b is on the commit that records the upgrade, not on 76bbc97, whose contract sources it shares; the steps say to tag the commit that records the implementation. - A payer's signed outcome replaces a token holder's only when the payer's is the transaction's only paying leg. - A 409 carries heldOutcomeHash only when the outcome held is one the payer signed; a token holder's held outcome gives only sameOutcome: false. - The explorer asks verifyEvidence about the payments the finalized root covers, not every payment listed. - Eight "(on main)" labels removed where the testnet has run the same code since 26 or 28 October. - The Development-and-Testing diagram shows payers and CounterAudit the way the other two architecture diagrams do. Checks: 5,779 source links and 4,607 anchors resolve in main 700a3ee, 81 internal links resolve, 0 CR bytes, no long dash in new text, all 532 Mermaid blocks parse and the changed one renders. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Nov 2, 2026
  • Describe the 40 merges since 29 October, and bring the counts to 2 November Prose and counts for #112 to #152, 416 replacements on 64 pages, each asserted to match once: - Slashing: 75% burned and 25% to the victim, nothing to the committee (ADR 0007), VictimIsCommittee, the two-field SlashExecuted, and a reporter credit from before 2 November still claimable. The 3 October drill stays as the record of the earlier split. - Oracle bond: an operator's exit time is fixed when it starts to leave (unbondingClaimableAt), with the old rule for an exit started before the field existed. - Testnet: identity and reputation on fdce1a7, staking on 25c2d59, the oracle bond on 76bbc97, all verified on the explorer and reproduced by the build tagged arc-testnet-2026-11-02b. Ten claims that the testnet lagged main, false since 26 October, are corrected. - Handover: the known-Safe checks, SAFE_FACTORY and SAFE_CREATION_CALL, and the reconciliation report the renounce requires. - Builds and checks: check-bytecode, check-authz and the authorisation matrix, and the CI lists. - Oracle: payer-signed outcomes (ADR 0006), GET /outcomes and the import between operators, the 409 body, the checker judging a proposal by the evidence it was made on, state backups and restore drills, and the CounterAudit relay off in production. Both operators run cf76691. - SDK 1.0.0-alpha.14: atomicNonceStore, the gate's instances and profile settings, and signPaymentOutcome and verifyPaymentOutcome. - Site: the explorer, the epochs page and the labelled simulation. - Counts: 724 contract tests in 32 files (712 run without a fork URL, 12 skip), 852 oracle, 233 SDK in 14 files. Checks: 5,779 source links and 4,607 anchors resolve in main 700a3ee, and the 81 internal links resolve; 0 CR bytes; no long dash in new text; all 532 Mermaid blocks parse and the 19 changed ones render with no error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Nov 2, 2026
  • Describe the handover checks of #110, the nonce-store tests of #111, and the new counts The renounce phase now takes neither the Safe nor the timelock on trust: phases 3 and 5 refuse a timelock whose code is not the TimelockController phase 2 deploys (the metadata solc appends is ignored) or that the deployer did not create, and a Safe that is an EIP-7702 delegated account. Phase 5 refuses a Safe that cannot be asked for its threshold unless CONFIRM_UNINSPECTABLE_SAFE vouches for it. Governance and Upgrades gets the four new errors with what to do about each, and Deployment Strategies the variable and the extended list. The Gate pages say that the SDK README now shows a Redis NonceStore, and the SDK testing page says what the two-gate tests show. Counts: 699 contract tests (692 run, 7 skip) and 206 SDK tests. Home names main 17cccb8. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Oct 30, 2026
  • 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>

    @RunTimeAdmin RunTimeAdmin committed Oct 29, 2026
  • 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>

    @RunTimeAdmin RunTimeAdmin committed Oct 29, 2026
  • Say that the pages were last checked against main ff0fa68 The text and the source links now follow the same commit, and the line says the SDK pages describe 1.0.0-alpha.11. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Oct 29, 2026
  • Say that the pages were last checked against main 652beca The text and the source links now follow the same commit, and the line says which SDK version the SDK pages describe. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Oct 28, 2026
  • Say that the pages were last checked against main 457fa9e The text and the source links now follow the same commit. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Oct 28, 2026
  • Describe the bound on upholding a dispute and say what the testnet runs On main an uphold is refused with DisputeResolutionExpired once the dispute can be expired, so the admin's ruling and the expiry never overlap. ADR 0005's note on re-filing is added to the slashing and unbonding pages. The Arc testnet proxies run the contracts as of fdce1a7, so they take the bound at their next upgrade. Every page that said they run the contracts on main now says so with that exception. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Oct 28, 2026
  • Say which commit the source links on the home page follow The anchors moved to main 457fa9e in the commits above. The line about the last check still names the commit the text was audited against, 638650f, and now adds the one the links follow. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Oct 28, 2026
  • Point the home page at main 638650f Main now holds the 26 October documentation, the site pull request and two changes the wiki does not link to (a test-harness fix and an SDK lockfile bump). The source links were checked against a fresh export of that commit: 5,761 links, 4,599 anchors and 80 internal links, 0 problems. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Oct 27, 2026
  • Say that the testnet proxies run the contracts on main since 26 October 2026 The four Arc testnet proxies were upgraded in place on 26 October 2026, so about 30 pages that said the testnet still runs the 21 September implementations, "(main only)", or "the testnet predates this" were wrong. - The page header notes say the testnet has run the contracts on main since the upgrade and keep the one thing an upgrade cannot change: role administrators are written when a proxy is initialised, so the testnet's admin still grants the slasher, committee and staking-core roles and the timelocked grants do not apply there. - The "(main only)" markers on the guardian pause, the admin ruling, the veto and the lapse are gone. - The signer registry is live on the testnet, but neither operator has named a signer. - The two proposals pending at the upgrade have finalized, and a proposal made before the upgrade reads zero in the two new PendingScore fields. - The VPS deployments fetch one pinned commit, not main; both testnet oracles run fdce1a7. - Test counts match the README (693 contract tests, 686 run, 19 invariants in five campaigns, 760 oracle tests, 168 SDK tests); seven pages still carried the 22 October numbers. - The slash drill is described with testnet faucet tokens. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Oct 27, 2026
  • Point the home page at main 2da02b7 Main now carries the README and docs changes the wiki's line links were mapped to, so the links and the code they cite agree. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

    @RunTimeAdmin RunTimeAdmin committed Oct 23, 2026
  • 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>

    @RunTimeAdmin RunTimeAdmin committed Oct 23, 2026
  • 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>

    @RunTimeAdmin RunTimeAdmin committed Oct 23, 2026
  • 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.

    @RunTimeAdmin RunTimeAdmin committed Oct 7, 2026
  • Initial Home page

    @RunTimeAdmin RunTimeAdmin committed Sep 22, 2026