§ NEW · 20-Node Mesh Verification Test

20-node mesh verification test suite

A complete set of pass/fail assertions to confirm every integration point is functioning correctly before permitting production traffic. Record results against this document and file as a production readiness artifact.

45
Total assertions
0
Passed
0
Failed
0
Critical failures

Running the automated test suite

The full verification suite can be run programmatically using themeshinfer-fleet verifyCLI command. Results are emitted as structured JSON and can be ingested into any CI/CD pipeline.

bash
# Run the full 20-node verification suite:
meshinfer-fleet verify   --org org_mesh20_prod   --api-key msk_live_...   --node-count 20   --suite all   --output verification_report_2026-07-06.json

# Run a single suite (e.g. routing only):
meshinfer-fleet verify --suite T3

# CI/CD integration (exits 1 if any critical assertion fails):
meshinfer-fleet verify --suite all --strict-critical && echo "GO" || echo "NO-GO"
T1

Identity & Registration

Verify all 20 nodes have valid identities and are registered with the Coordinator.

0 passed0 failed5 pending
IDAssertionSeverityResult
T1.1All 20 NodeIDs present in Coordinator registry (GET /v1/nodes)critical
T1.2Each NodeID has a valid DeviceID binding (1:1 mapping)critical
T1.3All 20 nodes bound to correct OrgID (org_mesh20_prod)critical
T1.4All 20 DIU wallets created on MeshNativeExchangecritical
T1.5Ed25519 signature on capability vector validates for all 20 nodescritical
T2

Connectivity & Heartbeat

Verify persistent connections and heartbeat cadence for all 20 nodes.

0 passed0 failed5 pending
IDAssertionSeverityResult
T2.1All 20 nodes emit heartbeat within last 30 scritical
T2.2Heartbeat ACK round-trip ≤ 5 s on all 20 nodeshigh
T2.3mTLS certificate valid and not expiring within 30 days for all 20high
T2.4WebSocket reconnect after forced disconnect ≤ 10 smedium
T2.5Missed-heartbeat eviction fires after 6 missed cycles (90 s)high
T3

Routing Pool Admission

Confirm all 20 nodes are correctly admitted to the routing pool.

0 passed0 failed6 pending
IDAssertionSeverityResult
T3.1All 20 nodes in pool tier ≥ standard (none suspended)critical
T3.2Routing weight > 0 for all 20 nodescritical
T3.3Router selects each node at least once in 200 randomized requestshigh
T3.4Mobile nodes (node-m01–m04) excluded on simulated cellular networkcritical
T3.5Mobile nodes (node-m01–m04) excluded when battery-only flag setcritical
T3.6Exploration fires: a small fraction of requests go to random eligible nodesmedium
T4

Inference Scheduling & Execution

End-to-end inference task dispatch and completion across all node types.

0 passed0 failed7 pending
IDAssertionSeverityResult
T4.1Tiny task (≤ 128 tokens) completes on all 20 nodes within 500 ms p95critical
T4.2Small task (≤ 512 tokens) completes on desktop/server nodes ≤ 800 ms p95critical
T4.3Task NACK response time ≤ 500 ms on overloaded nodehigh
T4.4Task re-dispatched within 1 s on NACK or timeouthigh
T4.5Model cold-start window granted (800 ms) for uncached modelmedium
T4.6Interactive task preempts background task on full nodemedium
T4.7Server-tier nodes (node-s01, node-s02) handle medium req_class (≤ 4096 tokens)high
T5

Metering & DIU Spend

Confirm metering pipeline accuracy and DIU spend accounting.

0 passed0 failed5 pending
IDAssertionSeverityResult
T5.1Metering event emitted for every completed inference taskcritical
T5.2diu_spend matches formula for 10 sampled taskscritical
T5.3Requester wallet debited synchronously with metering eventcritical
T5.4Zero-DIU task for local route (local_only nodes, own org)high
T5.5hypothetical_cloud_cost and actual_cost_usd logged on all eventsmedium
T6

DIU Issuance

Confirm DIU issuance logic, multipliers, and edge cases.

0 passed0 failed6 pending
IDAssertionSeverityResult
T6.1diu_issued event generated for every successful completed taskcritical
T6.2Failed task yields diu_net = 0 (no phantom issuance)critical
T6.3Late task (> 3× SLO) yields diu_net = 0critical
T6.4Elite node (reputation ≥ 90) earns elevated reputation multiplierhigh
T6.5Platform fee and reserve correctly split from gross spendhigh
T6.6Pending DIU visible in node wallet dashboard before epoch closemedium
T7

Settlement & Audit

Confirm MeshNativeExchange settlement and AuditLog integrity.

0 passed0 failed5 pending
IDAssertionSeverityResult
T7.1Settlement epoch closes within 5 min of top of hourhigh
T7.2All 20 node wallets show non-zero settled DIU after first epochcritical
T7.3Settlement integrity hash verifiable externally (SHA-256)critical
T7.4AuditLog records written for every settlement epochhigh
T7.5DOSFI accounting oracle receives epoch_settled ACK within 60 smedium
T8

Health, Privacy & Removal

Verify health checks, privacy enforcement, and node lifecycle operations.

0 passed0 failed6 pending
IDAssertionSeverityResult
T8.1Verification sampler fires on a sample of tasks (within configured tolerance)critical
T8.2Privacy gate: local_only node rejects cross-org task with 403critical
T8.3Thermal breach causes immediate pool removal (within 1 heartbeat = 15 s)critical
T8.4Graceful drain completes within 300 s on a loaded nodehigh
T8.5Replacement node (new NodeID, same DeviceID) reaches online status within 120 shigh
T8.6Reputation score penalized after intentional verification mismatch injectionhigh

Verification sign-off

Test suite versionv1.0 — 2026-07-06
Node count tested20
Required passing rate100% of critical assertions; ≥ 90% of all assertions
Sign-off authoritySenior Engineer + DevOps Lead — dual approval required
Artifact storageverification_report_{date}.json → file in SOC 2 evidence repository
Re-test triggerAny node replacement, firmware update, or Coordinator version upgrade
bash
# Submit verification report to AuditLog:
meshinfer-fleet verify sign-off   --report verification_report_2026-07-06.json   --approver-1 "senior-eng@org.com"   --approver-2 "devops-lead@org.com"   --org org_mesh20_prod   --api-key msk_live_...

# AuditLog entry:
# action: "mesh_verification_complete"
# resource_type: "verification_report"
# status: "success" | "failure"
# details.assertions_total: 44
# details.assertions_passed: 44
# details.critical_failures: 0
Production go-live gate
Zero critical failures AND overall pass rate ≥ 90% are hard requirements before the 20-node mesh may receive production inference traffic. This verification document, once signed, serves as the official go-live authorization artifact.