Skip to content

Independent Node Program: device communication and lineage campaign - #113

Merged
blackmore-technology-group merged 10 commits into
mainfrom
feature/independent-node-program
Oct 1, 2026
Merged

blackmore-technology-group merged 10 commits into
mainfrom
feature/independent-node-program

Conversation

@blackmore-technology-group

Copy link
Copy Markdown
Owner

Summary

Adds the ENTITY Independent Node Program (INP), a deliberately bounded test-network harness for independently operated devices.

Includes

  • standard-library Python node transport;
  • pseudonymous persistent test-node IDs;
  • A→B and multi-hop lineage envelopes;
  • SHA-256 origin/object integrity;
  • tamper rejection;
  • local privacy-minimized receipts;
  • offline envelope verification;
  • Windows bootstrap;
  • INP-01 through INP-07 campaign;
  • explicit evidence classifications;
  • dedicated CI qualification.

Claim boundary

This does not label BTG-controlled tests as independent evidence and does not infer ownership, payment, market value, certification, or endorsement from participation.

The listener binds to localhost by default and never starts automatically.

Comment thread .github/workflows/independent-node.yml Fixed
@blackmore-technology-group
blackmore-technology-group merged commit cab3a73 into main Oct 1, 2026
6 checks passed
@blackmore-technology-group
blackmore-technology-group deleted the feature/independent-node-program branch October 1, 2026 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants