# E26 Multi-Host Validation

**Result: 4 independent hosts; independent failure domains = YES.** Evidence:
`artifacts/e26/E26_MULTIHOST_RESULTS.json`.

## Topology
- Node 1: this host (local process).
- Nodes 2–4: three remote hosts (`45.76.169.191`, `207.246.66.130`, `149.28.193.50`), each running a
  standalone Ed25519-signed observation node. Remote inbound ports are firewalled, so the coordinator
  reaches them over **SSH local-forwarding** (real TCP across the network). Recorded kernels:
  `7.0.0-30-generic`, `7.0.0-31-generic`, `7.0.0-34-generic` — **3 distinct kernels**, separate hosts.
- Same provider (Vultr) and same operator: this is independent *hosts*, not independent operators or
  geographically verified regions.

## Results
| Scenario | Outcome |
|---|---|
| none | **SETTLED** |
| node drop | no settlement |
| partition | no settlement |
| forged observation | rejected |
| Byzantine node (conflicting outcome) | no settlement |
| node restart | recovers and settles |

`all_properties_hold = true`. Properties demonstrated: a Byzantine node cannot manufacture a
settlement; a minority failure / partition cannot produce a conflicting executable settlement;
forged observations are rejected; a restarted node recovers and is revalidated.

## Limitation
This is a **short** validation (seconds), not a 72-hour soak; geographic failure-domain independence
and region-level partition behaviour are not measured.
