Public interoperability campaign

Run an independent ENTITY test node.

Put ENTITY lineage on another real device and test whether the evidence survives the trip.

The Independent Node Program tests A→B communication, A→B→C lineage preservation, SHA-256 object integrity, tamper rejection, restart persistence, offline handoff and cross-platform behavior.

Windows quick start

Download. Initialize. Test.

Current package status: merged to ENTITY main in PR #113 after Independent Node CI, dependency review, public conformance, CodeQL and required analysis checks passed.
Expand the downloaded ZIP
Open PowerShell in the ENTITY folder
powershell -ExecutionPolicy Bypass -File independent-node/install.ps1
python independent-node/node.py init
python independent-node/node.py status
python independent-node/node.py serve

On the second device, initialize another node and send the included sample object to the first device's trusted-network address.

python independent-node/node.py init
python independent-node/node.py send --to http://DEVICE_A_IP:8343 --file independent-node/examples/sample-object.json
Campaign

Seven bounded tests.

INP-01 / INP-02

Installation, persistent pseudonymous node identity and two-device exchange.

INP-03 / INP-04

Three-device lineage preservation and deliberate object/hash tamper rejection.

INP-05 / INP-06 / INP-07

Restart/recovery, offline envelope handoff and cross-platform exchange.

Evidence

Operator independence is recorded, not assumed.

BTG_CONTROLLED

BTG controls every endpoint.

EXTERNAL_REPRODUCTION

An unrelated operator reproduces the published test.

INDEPENDENT_MULTI_OPERATOR

Different unrelated operators control different endpoints in the exchange.

Claim boundary: a PASS establishes the bounded transport/hash/lineage behavior tested. It does not automatically establish full ENTITY conformance, external-world truth, legal ownership, monetary value, payment, certification or endorsement.
Report your resultPrivacy & safetyFull test campaign