We are opening the ENTITY Independent Node Program (INP) to outside operators.
The goal is simple: run the small public test harness on a device you control, exchange a test object with another node, and tell us exactly where interoperability succeeds or fails.
What we want to test
- installation and persistent pseudonymous node identity;
- A → B device communication;
- A → B → C origin-lineage preservation;
- object/hash tamper rejection;
- restart and local evidence persistence;
- offline envelope handoff;
- Windows/Linux/macOS combinations.
A reproducible failure is useful evidence.
Start
The Independent Node Program is merged into ENTITY main through PR #113:
https://github.com/blackmore-technology-group/ENTITY/tree/main/independent-node
Direct repository ZIP:
https://github.com/blackmore-technology-group/ENTITY/archive/refs/heads/main.zip
Published install/test guide:
https://blackmore-technology-group.github.io/ENTITY-DOCS/developer/independent-node/
The harness uses the Python standard library and does not silently install a service or start a listener. The listener defaults to localhost. Please use a trusted LAN/VPN/isolated test network; do not expose the reference listener directly to the public Internet.
When you report a result
Please include:
- ENTITY release/tag;
- operating systems;
- INP test number(s);
- PASS/FAIL and first reproducible failure;
- receipt SHA-256 values;
- whether endpoints were controlled by the same operator or by unrelated operators.
Please do not post IP addresses, usernames, serial numbers, tokens, keys, personal files, private filesystem paths, or other sensitive information.
Evidence classification
Results are kept distinct as:
BTG_CONTROLLEDEXTERNAL_REPRODUCTIONINDEPENDENT_MULTI_OPERATOR
A successful receipt proves the bounded exchange/hash/lineage behavior tested. It does not automatically establish full protocol conformance, external-world truth, legal ownership, monetary value, payment, certification, or endorsement.
If you can run two different machines—or coordinate with another developer—we especially want the INDEPENDENT_MULTI_OPERATOR case.
We are opening the ENTITY Independent Node Program (INP) to outside operators.
The goal is simple: run the small public test harness on a device you control, exchange a test object with another node, and tell us exactly where interoperability succeeds or fails.
What we want to test
A reproducible failure is useful evidence.
Start
The Independent Node Program is merged into ENTITY
mainthrough PR #113:https://github.com/blackmore-technology-group/ENTITY/tree/main/independent-node
Direct repository ZIP:
https://github.com/blackmore-technology-group/ENTITY/archive/refs/heads/main.zip
Published install/test guide:
https://blackmore-technology-group.github.io/ENTITY-DOCS/developer/independent-node/
The harness uses the Python standard library and does not silently install a service or start a listener. The listener defaults to localhost. Please use a trusted LAN/VPN/isolated test network; do not expose the reference listener directly to the public Internet.
When you report a result
Please include:
Please do not post IP addresses, usernames, serial numbers, tokens, keys, personal files, private filesystem paths, or other sensitive information.
Evidence classification
Results are kept distinct as:
BTG_CONTROLLEDEXTERNAL_REPRODUCTIONINDEPENDENT_MULTI_OPERATORA successful receipt proves the bounded exchange/hash/lineage behavior tested. It does not automatically establish full protocol conformance, external-world truth, legal ownership, monetary value, payment, certification, or endorsement.
If you can run two different machines—or coordinate with another developer—we especially want the INDEPENDENT_MULTI_OPERATOR case.