About SettlementWitness
SettlementWitness is an MCP server published by nutstrut in the Blockchain category: deterministic verification gate for agent execution and x402 settlement.
Recent commit activity is the strongest signal that reported issues will get attention.
Install
git clone https://github.com/nutstrut/default-settlement-verifierThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about SettlementWitness
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
5 checks have not been run yet.
README
DefaultVerifier — SAR Verification Infrastructure
SAR (Settlement Attestation Receipt) is a verification protocol that produces cryptographically signed receipts proving whether an AI agent completed a task according to its specification.
DefaultVerifier is a live SAR verifier implementation with a public receipt registry, metrics API, and explorer.
If it matters—Verify it.
Architecture
Understand the SAR stack and verification model:
Example Response
{ "witness": "SettlementWitness", "witness_version": "v0", "task_id": "example", "verifier_endpoint": "https://defaultverifier.com/verify", "witness_timestamp": "2026-01-01T00:00:00Z", "receipt_id": "...", "receipt_v0_1": { "task_id_hash": "sha256:...", "verdict": "PASS", "confidence": 1.0, "reason_code": "SPEC_MATCH", "ts": "...", "verifier_kid": "...", "counterparty": "0xABC...", "receipt_id": "sha256:...", "sig": "base64url:..." },
"_ext": { "agent_id": "0x123:demo" } }
Notes
receipt_v0_1is the signed canonical receipt payload used by this implementation- when
counterpartyis present, it is included in signature scope and inreceipt_idderivation - legacy receipts (
sar-prod-ed25519-01andsar-prod-ed25519-02) remain valid and do not includecounterpartyin signature scope - this behavior is implemented and publicly verifiable via the live receipt and key endpoints
SAR Compatibility: This implementation follows SAR verification semantics, with an extended signed payload when counterparty is present.
Demo
Run a full end-to-end verification in ~2 minutes: DEMO.md
Quick Start
1. Create a receipt
curl -X POST https://defaultverifier.com/settlement-witness
-H 'content-type: application/json'
-d '{
"task_id":"quickstart-001",
"spec":{"goal":"demo"},
"output":{"goal":"demo"},
"counterparty":"0x1234567890abcdef1234567890abcdef12345678"
}'
2. Fetch the receipt
curl https://defaultverifier.com/settlement-witness/receipt/<receipt_id>
Note: use the receipt_id inside receipt_v0_1
3. Verify locally (Node)
cd examples/node-verify node verify.js receipt.json jwks.json
Examples
Node.js verification example: examples/node-verify/
Python verification example: examples/verify_receipt_python.py
Usage: python3 examples/verify_receipt_python.py <receipt_id>
API Endpoints
Create Receipt
POST /settlement-witness
Submits a task verification request and returns a signed SAR receipt.
Retrieve Receipt
GET /settlement-witness/receipt/{receipt_id}
Note: Use the receipt_id inside receipt_v0_1 (sha256:...) for retrieval.
Returns a previously issued receipt.
Wallet Receipt Explorer
GET /settlement-witness/receipts?wallet={address}
Returns recent receipts associated with a wallet address.
The public explorer is available at:
https://defaultverifier.com/explorer
This interface allows browsing recent receipts and wallet-indexed delivery history.
Public Verification Keys
https://defaultverifier.com/.well-known/jwks.json
Alternative (SAR protocol reference): https://defaultverifier.com/.well-known/sar-keys.json
Used to verify Ed25519 signatures for receipts.
Key Registry
https://defaultverifier.com/.well-known/sar-keys.json
Registry of verifier public keys referenced by verifier_kid.
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.