# Findings (derived from the recorded probes, 2026-09-21T18:33:12Z)

These are what an independent reader gets by running the published prober against the public sites. Verdicts are computed, not asserted.

## via cainstudio.online: NOT_ESTABLISHED  (N=4, f=1, Byzantine quorum 2f+1=3, verified signed proofs=1)
- nodes reporting a quorum below the Byzantine quorum 3 (2f+1 for N=4): {'node1@http://149.28.193.50:19023': 2, 'node3@http://45.76.169.191:8420': 2, 'node4@http://207.246.66.130:8420': 2}; a quorum of 2 lets two conflicting decisions both commit
- only 1 node(s) serve a verifiable signed state proof; need >= 3
- software version reported by only some nodes (missing: node1@http://149.28.193.50:19023, node3@http://45.76.169.191:8420, node4@http://207.246.66.130:8420): the cluster is not running one verified build
- UNSUPPORTED CLAIM: gateway@https://cainstudio.online claims 'PROVEN' but the derived verdict is NOT_ESTABLISHED

## via mcpgate.online: NOT_ESTABLISHED  (N=4, f=1, Byzantine quorum 2f+1=3, verified signed proofs=1)
- nodes reporting a quorum below the Byzantine quorum 3 (2f+1 for N=4): {'node1@http://149.28.193.50:19023': 2, 'node3@http://45.76.169.191:8420': 2, 'node4@http://207.246.66.130:8420': 2}; a quorum of 2 lets two conflicting decisions both commit
- only 1 node(s) serve a verifiable signed state proof; need >= 3
- software version reported by only some nodes (missing: node1@http://149.28.193.50:19023, node3@http://45.76.169.191:8420, node4@http://207.246.66.130:8420): the cluster is not running one verified build
- UNSUPPORTED CLAIM: gateway@https://mcpgate.online claims 'PROVEN' but the derived verdict is NOT_ESTABLISHED

## via clawx.click: NOT_ESTABLISHED  (N=4, f=1, Byzantine quorum 2f+1=3, verified signed proofs=1)
- nodes reporting a quorum below the Byzantine quorum 3 (2f+1 for N=4): {'node1@http://149.28.193.50:19023': 2, 'node3@http://45.76.169.191:8420': 2, 'node4@http://207.246.66.130:8420': 2}; a quorum of 2 lets two conflicting decisions both commit
- only 1 node(s) serve a verifiable signed state proof; need >= 3
- software version reported by only some nodes (missing: node1@http://149.28.193.50:19023, node3@http://45.76.169.191:8420, node4@http://207.246.66.130:8420): the cluster is not running one verified build
- UNSUPPORTED CLAIM: gateway@https://clawx.click claims 'PROVEN' but the derived verdict is NOT_ESTABLISHED

## What is established
- Three remote nodes on three distinct hosts (plus node2, the gateway) answered /health at probe time. The three site domains are one gateway, not three hosts.
- All nodes agree on membership (4 nodes).
- node2's signed PBFT state proof verifies with only the `cryptography` package (independently of any CAIN code).
- The consensus logic passes its tests (consensus-test-run.txt): PBFT cluster, proof-carrying quorum certificates, independent verifier, multi-process BFT evidence, Byzantine swarm.

## What is NOT established (and why the verdict is NOT_ESTABLISHED)
- The other nodes report a quorum of 2 where a Byzantine quorum for N=4, f=1 is 3. With a quorum of 2, two conflicting decisions could both commit.
- Only one node serves a signed state proof, so cross-node agreement on state cannot be verified from outside.
- The other nodes do not report a software version and expose a smaller, older API: the cluster is not running one verified build.
- The `byzantine_f1_readiness: PROVEN` field is computed from a membership COUNT (N>=4 and 4 trusted members). It is not evidence of fault tolerance, and this bundle does not treat it as such.

## What would change the verdict
Bring the remote nodes to the same build as node2 (quorum 2f+1=3, state-proof endpoint served, version reported), then re-run `python3 verify_cluster_bundle.py <url> --live`.
Not done by this bundle: no fault was injected into the live cluster (no node was stopped or partitioned); the consensus tests run in an isolated copy, not against the live nodes.