bitcoin-stratigraphy

by app.replit.bitcoin-stratigraphy-dashboard--charlesstrogish

Submit ZK Proof

proof.submit

PURPOSE & BOUNDARIES: Submit and register a new Groth16 zk-SNARK proof with its five public signals, then attempt a Nostr NIP-78 attestation; this changes proof registry state, but does not append a proof to a Merkle tree. USAGE GUIDELINES: Use proof.submit strictly for registering new attestations, and use proof.verify instead when validating an existing proof without state mutation. Use proof.get_by_hash for retained submissions or proof.ground for a Bitcoin-tip receipt. BEHAVIOR & CONSEQUENCES: Costs 250 sats via HTTP L402 without valid credentials; malformed inputs fail validation, invalid proofs are reported, and Nostr publication status may fail separately.

Input Schema

TableJSON Schema

Name	Required	Description
`proof`	Yes	Groth16/Poseidon BN254 proof coordinates for non-interactive validation: piA and piC are three decimal-string projective coordinates each, and piB is three pairs of decimal-string extension-field coordinates; for example, piA ['1','2','1'].
`publicSignals`	Yes	Five ordered public inputs—blockHeight, thermodynamicHash, timestamp, valuationSat, and snapshotDigest—that must align with the submitted proof coordinates. Constraints: minItems: 5; maxItems: 5. Example: ["920000","1","1789776000000","12583","1"].
`snapshotDigest`	No	Decimal field digest or IPFS CID that must equal publicSignals[4] when supplied. Constraints: pattern: ^(?:\d+\|Qm[1-9A-HJ-NP-Za-km-z]{44}\|b[a-z2-7]{20,})$. Example: "1".

Output Schema

TableJSON Schema

Name	Required	Description
`jobId`	Yes	Server-generated proof submission job ID for status lookup. Constraints: format: uuid. Example: "123e4567-e89b-42d3-a456-426614174000".
`status`	Yes	Immediate Groth16 verification result for the submitted proof and public signals. Constraints: allowed values: verified, invalid. Example: "verified".
`proofHash`	Yes	0x-prefixed lowercase hexadecimal SHA-256 digest of the canonical proof. Example: "0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd".
`submittedAt`	Yes	ISO 8601 UTC date string format. Constraints: format: date-time. Example: "2026-09-19T06:20:00.000Z".
`attestationStatus`	Yes	Nostr NIP-78 publication result: broadcast_confirmed, broadcast_failed, not_configured, or not_broadcast_invalid_proof. Example: "broadcast_confirmed".

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 27, 2026

changedOutput schema / examples

Previous value: -[
-  {
-    "attestationStatus": "broadcast_confirmed",
-    "proofHash": "0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd",
-    "status": "verified",
-    "submittedAt": "2026-09-19T06:20:00.000Z"
-  }
-]New value: +[
+  {
+    "attestationStatus": "broadcast_confirmed",
+    "jobId": "123e4567-e89b-42d3-a456-426614174000",
+    "proofHash": "0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd",
+    "status": "verified",
+    "submittedAt": "2026-09-19T06:20:00.000Z"
+  }
+]

addedOutput schema / properties / jobId

Added value: +{
+  "description": "Server-generated proof submission job ID for status lookup. Constraints: format: uuid. Example: \"123e4567-e89b-42d3-a456-426614174000\".",
+  "example": "123e4567-e89b-42d3-a456-426614174000",
+  "examples": [
+    "123e4567-e89b-42d3-a456-426614174000"
+  ],
+  "format": "uuid",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "proofHash",
-  "status",
-  "submittedAt",
-  "attestationStatus"
-]New value: +[
+  "proofHash",
+  "jobId",
+  "status",
+  "submittedAt",
+  "attestationStatus"
+]

Changed2 schema fields changedSep 25, 2026

changedInput schema / properties / proof / description

Previous value: -"Groth16/Poseidon BN254 proof coordinates using piA and piC as three decimal-string projective coordinates each and piB as three pairs of decimal-string extension-field coordinates; for example, piA ['1','2','1']."New value: +"Groth16/Poseidon BN254 proof coordinates for non-interactive validation: piA and piC are three decimal-string projective coordinates each, and piB is three pairs of decimal-string extension-field coordinates; for example, piA ['1','2','1']."

changedInput schema / properties / publicSignals / description

Previous value: -"Public signals ordered as blockHeight, thermodynamicHash, timestamp, valuationSat, and snapshotDigest. Constraints: minItems: 5; maxItems: 5. Example: [\"920000\",\"1\",\"1789776000000\",\"12583\",\"1\"]."New value: +"Five ordered public inputs—blockHeight, thermodynamicHash, timestamp, valuationSat, and snapshotDigest—that must align with the submitted proof coordinates. Constraints: minItems: 5; maxItems: 5. Example: [\"920000\",\"1\",\"1789776000000\",\"12583\",\"1\"]."

Changed31 schema fields changedSep 24, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "proof": {
-      "pi_a": [
-        "1",
-        "2",
-        "1"
-      ],
-      "pi_b": [
-        [
-          "1",
-          "2"
-        ],
-        [
-          "3",
-          "4"
-        ],
-        [
-          "1",
-          "0"
-        ]
-      ],
-      "pi_c": [
-        "5",
-        "6",
-        "1"
-      ]
-    },
-    "publicSignals": [
-      "920000",
-      "1",
-      "1789776000000",
-      "12583",
-      "1"
-    ],
-    "snapshotDigest": "1"
-  }
-]New value: +[
+  {
+    "proof": {
+      "piA": [
+        "1",
+        "2",
+        "1"
+      ],
+      "piB": [
+        [
+          "1",
+          "2"
+        ],
+        [
+          "3",
+          "4"
+        ],
+        [
+          "1",
+          "0"
+        ]
+      ],
+      "piC": [
+        "5",
+        "6",
+        "1"
+      ]
+    },
+    "publicSignals": [
+      "920000",
+      "1",
+      "1789776000000",
+      "12583",
+      "1"
+    ],
+    "snapshotDigest": "1"
+  }
+]

removedInput schema / properties / proof / default

Removed value: -{
-  "pi_a": [
-    "1",
-    "2",
-    "1"
-  ],
-  "pi_b": [
-    [
-      "1",
-      "2"
-    ],
-    [
-      "3",
-      "4"
-    ],
-    [
-      "1",
-      "0"
-    ]
-  ],
-  "pi_c": [
-    "5",
-    "6",
-    "1"
-  ]
-}

changedInput schema / properties / proof / description

Previous value: -"Groth16/Poseidon zk-SNARK proof coordinates over the BN254 curve."New value: +"Groth16/Poseidon BN254 proof coordinates using piA and piC as three decimal-string projective coordinates each and piB as three pairs of decimal-string extension-field coordinates; for example, piA ['1','2','1']."

addedInput schema / properties / proof / example / piA
```
Added value: +[
+  "1",
+  "2",
+  "1"
+]
```

addedInput schema / properties / proof / example / piB

Added value: +[
+  [
+    "1",
+    "2"
+  ],
+  [
+    "3",
+    "4"
+  ],
+  [
+    "1",
+    "0"
+  ]
+]

addedInput schema / properties / proof / example / piC
```
Added value: +[
+  "5",
+  "6",
+  "1"
+]
```
removedInput schema / properties / proof / example / pi_a
```
Removed value: -[
-  "1",
-  "2",
-  "1"
-]
```

removedInput schema / properties / proof / example / pi_b

Removed value: -[
-  [
-    "1",
-    "2"
-  ],
-  [
-    "3",
-    "4"
-  ],
-  [
-    "1",
-    "0"
-  ]
-]

removedInput schema / properties / proof / example / pi_c
```
Removed value: -[
-  "5",
-  "6",
-  "1"
-]
```

changedInput schema / properties / proof / examples

Previous value: -[
-  {
-    "pi_a": [
-      "1",
-      "2",
-      "1"
-    ],
-    "pi_b": [
-      [
-        "1",
-        "2"
-      ],
-      [
-        "3",
-        "4"
-      ],
-      [
-        "1",
-        "0"
-      ]
-    ],
-    "pi_c": [
-      "5",
-      "6",
-      "1"
-    ]
-  }
-]New value: +[
+  {
+    "piA": [
+      "1",
+      "2",
+      "1"
+    ],
+    "piB": [
+      [
+        "1",
+        "2"
+      ],
+      [
+        "3",
+        "4"
+      ],
+      [
+        "1",
+        "0"
+      ]
+    ],
+    "piC": [
+      "5",
+      "6",
+      "1"
+    ]
+  }
+]

addedInput schema / properties / proof / properties / piA

Added value: +{
+  "description": "Exactly three decimal-string Groth16 BN254 proof A projective coordinates in order. Constraints: minItems: 3; maxItems: 3. Example: [\"1\",\"2\",\"1\"].",
+  "example": [
+    "1",
+    "2",
+    "1"
+  ],
+  "examples": [
+    [
+      "1",
+      "2",
+      "1"
+    ]
+  ],
+  "items": {
+    "description": "Decimal-encoded BN254 scalar-field coordinate in proof point A. Constraints: pattern: ^\\d+$. Example: \"10823\".",
+    "example": "10823",
+    "examples": [
+      "10823"
+    ],
+    "pattern": "^\\d+$",
+    "type": "string"
+  },
+  "maxItems": 3,
+  "minItems": 3,
+  "type": "array"
+}

addedInput schema / properties / proof / properties / piB

Added value: +{
+  "description": "Exactly three Groth16 BN254 proof B extension-field coordinate pairs, each containing two decimal strings. Constraints: minItems: 3; maxItems: 3. Example: [[\"1\",\"2\"],[\"3\",\"4\"],[\"1\",\"0\"]].",
+  "example": [
+    [
+      "1",
+      "2"
+    ],
+    [
+      "3",
+      "4"
+    ],
+    [
+      "1",
+      "0"
+    ]
+  ],
+  "examples": [
+    [
+      [
+        "1",
+        "2"
+      ],
+      [
+        "3",
+        "4"
+      ],
+      [
+        "1",
+        "0"
+      ]
+    ]
+  ],
+  "items": {
+    "description": "BN254 extension-field coordinate pair in proof point B. Constraints: minItems: 2; maxItems: 2. Example: [\"112\",\"331\"].",
+    "example": [
+      "112",
+      "331"
+    ],
+    "examples": [
+      [
+        "112",
+        "331"
+      ]
+    ],
+    "items": {
+      "description": "Decimal-encoded BN254 extension-field coordinate in proof point B. Constraints: pattern: ^\\d+$. Example: \"331\".",
+      "example": "331",
+      "examples": [
+        "331"
+      ],
+      "pattern": "^\\d+$",
+      "type": "string"
+    },
+    "maxItems": 2,
+    "minItems": 2,
+    "type": "array"
+  },
+  "maxItems": 3,
+  "minItems": 3,
+  "type": "array"
+}

addedInput schema / properties / proof / properties / piC

Added value: +{
+  "description": "Exactly three decimal-string Groth16 BN254 proof C projective coordinates in order. Constraints: minItems: 3; maxItems: 3. Example: [\"5\",\"6\",\"1\"].",
+  "example": [
+    "5",
+    "6",
+    "1"
+  ],
+  "examples": [
+    [
+      "5",
+      "6",
+      "1"
+    ]
+  ],
+  "items": {
+    "description": "Decimal-encoded BN254 scalar-field coordinate in proof point C. Constraints: pattern: ^\\d+$. Example: \"554\".",
+    "example": "554",
+    "examples": [
+      "554"
+    ],
+    "pattern": "^\\d+$",
+    "type": "string"
+  },
+  "maxItems": 3,
+  "minItems": 3,
+  "type": "array"
+}

removedInput schema / properties / proof / properties / pi_a

Removed value: -{
-  "default": [
-    "1",
-    "2",
-    "1"
-  ],
-  "description": "Groth16 BN254 proof A projective coordinates.",
-  "example": [
-    "1",
-    "2",
-    "1"
-  ],
-  "examples": [
-    [
-      "1",
-      "2",
-      "1"
-    ]
-  ],
-  "items": {
-    "default": "10823",
-    "description": "Decimal-encoded BN254 scalar-field coordinate in proof point A.",
-    "example": "10823",
-    "examples": [
-      "10823"
-    ],
-    "pattern": "^\\d+$",
-    "type": "string"
-  },
-  "maxItems": 3,
-  "minItems": 3,
-  "type": "array"
-}

removedInput schema / properties / proof / properties / pi_b

Removed value: -{
-  "default": [
-    [
-      "1",
-      "2"
-    ],
-    [
-      "3",
-      "4"
-    ],
-    [
-      "1",
-      "0"
-    ]
-  ],
-  "description": "Groth16 BN254 proof B projective coordinates.",
-  "example": [
-    [
-      "1",
-      "2"
-    ],
-    [
-      "3",
-      "4"
-    ],
-    [
-      "1",
-      "0"
-    ]
-  ],
-  "examples": [
-    [
-      [
-        "1",
-        "2"
-      ],
-      [
-        "3",
-        "4"
-      ],
-      [
-        "1",
-        "0"
-      ]
-    ]
-  ],
-  "items": {
-    "default": [
-      "112",
-      "331"
-    ],
-    "description": "BN254 extension-field coordinate pair in proof point B.",
-    "example": [
-      "112",
-      "331"
-    ],
-    "examples": [
-      [
-        "112",
-        "331"
-      ]
-    ],
-    "items": {
-      "default": "331",
-      "description": "Decimal-encoded BN254 extension-field coordinate in proof point B.",
-      "example": "331",
-      "examples": [
-        "331"
-      ],
-      "pattern": "^\\d+$",
-      "type": "string"
-    },
-    "maxItems": 2,
-    "minItems": 2,
-    "type": "array"
-  },
-  "maxItems": 3,
-  "minItems": 3,
-  "type": "array"
-}

removedInput schema / properties / proof / properties / pi_c

Removed value: -{
-  "default": [
-    "5",
-    "6",
-    "1"
-  ],
-  "description": "Groth16 BN254 proof C projective coordinates.",
-  "example": [
-    "5",
-    "6",
-    "1"
-  ],
-  "examples": [
-    [
-      "5",
-      "6",
-      "1"
-    ]
-  ],
-  "items": {
-    "default": "554",
-    "description": "Decimal-encoded BN254 scalar-field coordinate in proof point C.",
-    "example": "554",
-    "examples": [
-      "554"
-    ],
-    "pattern": "^\\d+$",
-    "type": "string"
-  },
-  "maxItems": 3,
-  "minItems": 3,
-  "type": "array"
-}

changedInput schema / properties / proof / required

Previous value: -[
-  "pi_a",
-  "pi_b",
-  "pi_c"
-]New value: +[
+  "piA",
+  "piB",
+  "piC"
+]

removedInput schema / properties / publicSignals / default

Removed value: -[
-  "920000",
-  "1",
-  "1789776000000",
-  "12583",
-  "1"
-]

changedInput schema / properties / publicSignals / description

Previous value: -"Public signals ordered as blockHeight, thermodynamicHash, timestamp, valuationSat, and snapshotDigest."New value: +"Public signals ordered as blockHeight, thermodynamicHash, timestamp, valuationSat, and snapshotDigest. Constraints: minItems: 5; maxItems: 5. Example: [\"920000\",\"1\",\"1789776000000\",\"12583\",\"1\"]."

removedInput schema / properties / publicSignals / items / default
```
Removed value: -"920000"
```

changedInput schema / properties / publicSignals / items / description

Previous value: -"Decimal-encoded BN254 scalar-field element."New value: +"Decimal-encoded BN254 scalar-field element. Constraints: pattern: ^\\d+$. Example: \"920000\"."

removedInput schema / properties / snapshotDigest / default
```
Removed value: -"1"
```

changedInput schema / properties / snapshotDigest / description

Previous value: -"Decimal field digest or IPFS CID that must equal publicSignals[4] when supplied."New value: +"Decimal field digest or IPFS CID that must equal publicSignals[4] when supplied. Constraints: pattern: ^(?:\\d+|Qm[1-9A-HJ-NP-Za-km-z]{44}|b[a-z2-7]{20,})$. Example: \"1\"."

removedOutput schema / properties / attestationStatus / default
```
Removed value: -"broadcast_confirmed"
```

changedOutput schema / properties / attestationStatus / description

Previous value: -"Nostr NIP-78 publication result: broadcast_confirmed, broadcast_failed, not_configured, or not_broadcast_invalid_proof."New value: +"Nostr NIP-78 publication result: broadcast_confirmed, broadcast_failed, not_configured, or not_broadcast_invalid_proof. Example: \"broadcast_confirmed\"."

removedOutput schema / properties / proofHash / default

Removed value: -"0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd"

changedOutput schema / properties / proofHash / description

Previous value: -"0x-prefixed lowercase hexadecimal SHA-256 digest of the canonical proof."New value: +"0x-prefixed lowercase hexadecimal SHA-256 digest of the canonical proof. Example: \"0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd\"."

removedOutput schema / properties / status / default
```
Removed value: -"verified"
```

changedOutput schema / properties / status / description

Previous value: -"Immediate Groth16 verification result for the submitted proof and public signals."New value: +"Immediate Groth16 verification result for the submitted proof and public signals. Constraints: allowed values: verified, invalid. Example: \"verified\"."

removedOutput schema / properties / submittedAt / default
```
Removed value: -"2026-09-19T06:20:00.000Z"
```

changedOutput schema / properties / submittedAt / description

Previous value: -"ISO 8601 UTC date string format."New value: +"ISO 8601 UTC date string format. Constraints: format: date-time. Example: \"2026-09-19T06:20:00.000Z\"."

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / snapshotDigest / description

Previous value: -"Canonical IPFS CID or hex digest identifier string."New value: +"Decimal field digest or IPFS CID that must equal publicSignals[4] when supplied."

changedOutput schema / properties / proofHash / description

Previous value: -"64-character lowercase hexadecimal SHA-256 digest string."New value: +"0x-prefixed lowercase hexadecimal SHA-256 digest of the canonical proof."

Changed3 schema fields changedSep 22, 2026

changedInput schema / properties / snapshotDigest / description

Previous value: -"Telemetry snapshot CID or Poseidon digest matching the snapshot commitment signal."New value: +"Canonical IPFS CID or hex digest identifier string."

changedOutput schema / properties / proofHash / description

Previous value: -"Lowercase 0x-prefixed SHA-256 fingerprint of the canonical submitted proof object."New value: +"64-character lowercase hexadecimal SHA-256 digest string."

changedOutput schema / properties / submittedAt / description

Previous value: -"ISO 8601 timestamp when the data engine accepted the submission."New value: +"ISO 8601 UTC date string format."

Changed11 schema fields changedSep 22, 2026

changedInput schema / properties / proof / description

Previous value: -"Groth16/Poseidon zk-SNARK proof object containing pi_a (3-element array), pi_b (3x2 nested array), and pi_c (3-element array) BN254 elliptic curve projective points as decimal string field elements. Example: {\"pi_a\":[\"10823\",\"49102\",\"1\"],\"pi_b\":[[\"112\",\"331\"],[\"981\",\"771\"],[\"1\",\"0\"]],\"pi_c\":[\"554\",\"882\",\"1\"]}."New value: +"Groth16/Poseidon zk-SNARK proof coordinates over the BN254 curve."

changedInput schema / properties / proof / properties / pi_a / description

Previous value: -"Required 3-element array of decimal string field elements representing the Groth16 BN254 proof A projective point. Example: ['10823', '49102', '1']."New value: +"Groth16 BN254 proof A projective coordinates."

changedInput schema / properties / proof / properties / pi_a / items / description

Previous value: -"Decimal string BN254 scalar-field coordinate in proof point A. Example: '10823'."New value: +"Decimal-encoded BN254 scalar-field coordinate in proof point A."

changedInput schema / properties / proof / properties / pi_b / description

Previous value: -"Required 3x2 nested array of decimal string field elements representing the Groth16 BN254 proof B projective point. Example: [['112', '331'], ['981', '771'], ['1', '0']]."New value: +"Groth16 BN254 proof B projective coordinates."

changedInput schema / properties / proof / properties / pi_b / items / description

Previous value: -"Required 2-element array of decimal string BN254 extension-field coordinates. Example: ['112', '331']."New value: +"BN254 extension-field coordinate pair in proof point B."

changedInput schema / properties / proof / properties / pi_b / items / items / description

Previous value: -"Decimal string BN254 extension-field coordinate in proof point B. Example: '331'."New value: +"Decimal-encoded BN254 extension-field coordinate in proof point B."

changedInput schema / properties / proof / properties / pi_c / description

Previous value: -"Required 3-element array of decimal string field elements representing the Groth16 BN254 proof C projective point. Example: ['554', '882', '1']."New value: +"Groth16 BN254 proof C projective coordinates."

changedInput schema / properties / proof / properties / pi_c / items / description

Previous value: -"Decimal string BN254 scalar-field coordinate in proof point C. Example: '554'."New value: +"Decimal-encoded BN254 scalar-field coordinate in proof point C."

changedInput schema / properties / publicSignals / description

Previous value: -"Required array of exactly 5 public signal strings representing scalar field elements in BN254 curve modulo space, ordered as blockHeight, thermodynamicHash, timestamp, valuationSat, and snapshotDigest. Example: ['920000', '1', '1789776000000', '12583', '1']."New value: +"Public signals ordered as blockHeight, thermodynamicHash, timestamp, valuationSat, and snapshotDigest."

changedInput schema / properties / publicSignals / items / description

Previous value: -"Decimal string scalar field element in the BN254 curve modulo space. Example: '920000'."New value: +"Decimal-encoded BN254 scalar-field element."

changedInput schema / properties / snapshotDigest / description

Previous value: -"Optional non-empty telemetry snapshot CID or decimal Poseidon digest string that must equal the fifth public signal. The schema default is '1'."New value: +"Telemetry snapshot CID or Poseidon digest matching the snapshot commitment signal."

Changed10 schema fields changedSep 22, 2026
- removedInput schema / properties / proof / properties / pi_a / items / minLength
```
Removed value: -1
```
- addedInput schema / properties / proof / properties / pi_a / items / pattern
```
Added value: +"^\\d+$"
```
- removedInput schema / properties / proof / properties / pi_b / items / items / minLength
```
Removed value: -1
```
- addedInput schema / properties / proof / properties / pi_b / items / items / pattern
```
Added value: +"^\\d+$"
```
- removedInput schema / properties / proof / properties / pi_c / items / minLength
```
Removed value: -1
```
- addedInput schema / properties / proof / properties / pi_c / items / pattern
```
Added value: +"^\\d+$"
```
- removedInput schema / properties / publicSignals / items / minLength
```
Removed value: -1
```
- addedInput schema / properties / publicSignals / items / pattern
```
Added value: +"^\\d+$"
```
- removedInput schema / properties / snapshotDigest / minLength
```
Removed value: -1
```
- addedInput schema / properties / snapshotDigest / pattern
```
Added value: +"^(?:\\d+|Qm[1-9A-HJ-NP-Za-km-z]{44}|b[a-z2-7]{20,})$"
```

Changed16 schema fields changedSep 22, 2026

addedInput schema / properties / proof / default

Added value: +{
+  "pi_a": [
+    "1",
+    "2",
+    "1"
+  ],
+  "pi_b": [
+    [
+      "1",
+      "2"
+    ],
+    [
+      "3",
+      "4"
+    ],
+    [
+      "1",
+      "0"
+    ]
+  ],
+  "pi_c": [
+    "5",
+    "6",
+    "1"
+  ]
+}

addedInput schema / properties / proof / properties / pi_a / default
```
Added value: +[
+  "1",
+  "2",
+  "1"
+]
```
addedInput schema / properties / proof / properties / pi_a / items / default
```
Added value: +"10823"
```

addedInput schema / properties / proof / properties / pi_b / default

Added value: +[
+  [
+    "1",
+    "2"
+  ],
+  [
+    "3",
+    "4"
+  ],
+  [
+    "1",
+    "0"
+  ]
+]

addedInput schema / properties / proof / properties / pi_b / items / default
```
Added value: +[
+  "112",
+  "331"
+]
```
addedInput schema / properties / proof / properties / pi_b / items / items / default
```
Added value: +"331"
```
addedInput schema / properties / proof / properties / pi_c / default
```
Added value: +[
+  "5",
+  "6",
+  "1"
+]
```
addedInput schema / properties / proof / properties / pi_c / items / default
```
Added value: +"554"
```

addedInput schema / properties / publicSignals / default

Added value: +[
+  "920000",
+  "1",
+  "1789776000000",
+  "12583",
+  "1"
+]

addedInput schema / properties / publicSignals / items / default
```
Added value: +"920000"
```
addedInput schema / properties / snapshotDigest / default
```
Added value: +"1"
```

changedInput schema / properties / snapshotDigest / description

Previous value: -"Optional non-empty telemetry snapshot CID or decimal Poseidon digest string that must equal the fifth public signal. No default. Example: '1'."New value: +"Optional non-empty telemetry snapshot CID or decimal Poseidon digest string that must equal the fifth public signal. The schema default is '1'."

addedOutput schema / properties / attestationStatus / default
```
Added value: +"broadcast_confirmed"
```

addedOutput schema / properties / proofHash / default

Added value: +"0x1a2b3c4d5e6f789001234567890abcdef1234567890abcdef1234567890abcd"

addedOutput schema / properties / status / default
```
Added value: +"verified"
```
addedOutput schema / properties / submittedAt / default
```
Added value: +"2026-09-19T06:20:00.000Z"
```

Changed5 schema fields changedSep 21, 2026
- addedInput schema / properties / proof / properties / pi_a / items / minLength
```
Added value: +1
```
- addedInput schema / properties / proof / properties / pi_b / items / items / minLength
```
Added value: +1
```
- addedInput schema / properties / proof / properties / pi_c / items / minLength
```
Added value: +1
```
- addedInput schema / properties / publicSignals / items / minLength
```
Added value: +1
```
- addedInput schema / properties / snapshotDigest / minLength
```
Added value: +1
```
AddedSep 21, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only cover safety/state hints (readOnly=false, destructive=false, idempotent=false, openWorld=true). The description adds non-obvious behavior the annotations cannot express: a 250-sat HTTP L402 cost, validation failure modes, invalid-proof reporting, and that Nostr NIP-78 publication can fail independently of registry success.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Labeled sections (PURPOSE & BOUNDARIES, USAGE GUIDELINES, BEHAVIOR & CONSEQUENCES) front-load the important content and every sentence carries information. It is dense but slightly over-packed into single long sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating, paid, open-world tool with nested parameters and an output schema, the description covers state effects, cost, alternatives, and independent failure modes. Nothing an agent needs before calling is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the nested proof/publicSignals shapes are documented in exhaustive detail in the schema. The description adds only the ordinal summary 'five public signals' and the separate Nostr attestation framing, which is a marginal gain over the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Submit and register a new Groth16 zk-SNARK proof') and explicitly bounds the operation ('does not append a proof to a Merkle tree'), which separates it from mesh.broadcast and other proof.* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use this for registering new attestations, use proof.verify for validation without mutation, proof.get_by_hash for retained submissions, and proof.ground for a Bitcoin-tip receipt. This is a model when/when-not/alternatives section.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All bitcoin-stratigraphy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?