Skip to content

feat(verification): add KBF transparent audits - #969

Open
alexanderludwig wants to merge 17 commits into
mainfrom
feat/kbf-verification
Open

feat(verification): add KBF transparent audits#969
alexanderludwig wants to merge 17 commits into
mainfrom
feat/kbf-verification

Conversation

@alexanderludwig

@alexanderludwig alexanderludwig commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

What

Adds KBF-based transparent model verification as an independent feature branch on top of contracts-update-all.

This PR includes:

  • AntseedVerification bundle submission, verifier rewards, and distinct active verdict tracking per agent and service.
  • AntseedVerificationPointsPolicy with a separate model-verification category, two-verifier minimum corroboration, seller-only penalties, retraction handling, and owner remediation.
  • ConfigureVerification.s.sol, which transfers the existing 10% verification emission bucket from VERIFICATION_WALLET to the verification contract and leaves points enforcement unregistered by default for shadow mode.
  • @antseed/fingerprints KBF probe, scoring, reference, consensus, and evidence primitives.
  • Node verification storage and authenticated evidence capture.
  • antseed verifier CLI workflows for reference generation, audits, evidence publication, submission, status, reward claims, and resumable operation.
  • Protocol documentation and changelog updates for the independent verification rollout.

This branch has no wash-trading contract or deployment dependency. Wash trading remains isolated in PR #895 as a sibling branch on the same contracts-update-all foundation.

VPR-side interpretation is intentionally excluded here. On-chain attestation enrichment, lifecycle scoring, and default-router behavior are isolated on the stacked codex/vpr-verification-consumer branch.

Why

Transparent audits need to collect evidence and reward approved verifiers before they affect seller routing or recognized-usage points. Separating the verification core from its points-policy adapter allows the network to operate in shadow mode, observe results, and activate enforcement only through an explicit policy-registry registration.

The corroboration model prevents one verifier from unilaterally penalizing a seller, while per-service retractions and owner remediation keep active verdict counters consistent during disputes or verifier compromise.

Testing

  • cd packages/contracts && forge build
  • cd packages/contracts && forge test — 39 suites, 804 tests passed
  • Verification contract tests — 43 tests passed
  • pnpm --filter=@antseed/fingerprints run typecheck
  • pnpm --filter=@antseed/fingerprints run test — 95 tests passed
  • Targeted Node verification and storage tests passed
  • After VPR extraction: pnpm --filter=@antseed/node run build
  • After VPR extraction: 24 focused Node tests passed
  • pnpm run build
  • pnpm run typecheck
  • pnpm run test
  • git diff --check
  • Verified the branch diff contains no wash-trading or desktop changes

Checklist

  • pnpm run build passes
  • pnpm run test passes
  • Breaking changes documented

@alexanderludwig
alexanderludwig changed the base branch from contracts-update-all to main August 28, 2026 11:43
@alexanderludwig
alexanderludwig force-pushed the feat/kbf-verification branch 2 times, most recently from 1e373e2 to 99f4108 Compare August 31, 2026 20:04
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