A recognised holder.
Establish which state represents the possession, who controls it and which successor is recognised after a transfer.
Digital ownership, closer to the device
Building digital ownership into devices.
A digital possession should have a clear owner, a defined way to transfer it and a device that respects the change. INTEGYRS is building the connection.
Working software alpha. Private-node experiments recorded. Protected-device integration is a development milestone.
01 / The problem
What makes a digital
possession yours?
Files are easy to copy. A transferable digital possession also needs a recognised ownership state, a rule for fresh access and an endpoint that can enforce that rule.
A fresh decision.
Check eligibility when a section is requested. A change in ownership must change the previous holder’s next access decision.
A meaningful boundary.
Work toward protected processing and rendering. A software policy alone cannot keep secrets from a compromised host.
02 / The approach
One possession.
An explicit handover.
Our first program connects an ownership record to threshold-controlled access. Transfer is a sequence with defined hold, refusal and recovery states.
Walk through the lifecycleRecognise.
Create a possession state. Keep its encrypted content separate from the ownership record.
Authorise.
Use fresh eligibility evidence and recipient-bound contributions for section access.
Freeze.
Stop new seller authorizations at the defined freeze boundary while the handover is resolved.
Activate.
Recognise the successor and test that the previous holder’s later access is refused.
Concept sequence. The current implementation is experimental software; protected-device enforcement remains to be demonstrated.
03 / Current evidence
Build. Test.
Show the boundary.
Our recorded experiments cover successful transfers and deliberate failures. Each result belongs to a specific environment and version. Test counts are coverage records, not security scores.
195offline tests
47private-node checks
2forced race orders
04 / Why it matters
Access that can
follow ownership.
The first intended experience is simple: a rights-cleared digital publication, a recognised holder and a transfer between two approved endpoints.
Explore the first use caseProposed applications
A foundation for more than one reader.
Transferable publications, licensed professional materials and device-bound software entitlements are candidate uses. Each needs its own rights, security and commercial validation.
Possession in a technical system does not itself transfer the copyright in the underlying work.
05 / The path ahead
Software first.
Devices next.
Hardware design work is underway. The next challenge is to turn a clear software access rule into a measured, protected device path.
See the product roadmapStrengthen end-to-end evidence
Authenticated state, adversarial failure paths and reproducible recovery.
Validate the device boundary
Attestation, non-exporting processing, protected rendering and rollback resistance.
Earn a supported product
Independent review and controlled pilots, with beta targeted for early 2027 and live rollout planned by April 2028.
Technical library
Go deeper.
Follow every boundary.
Explore what digital scarcity changes, how the current protocol works, and the infrastructure, hardware and published inventions behind the longer-term direction.
FOUNDATIONS / INFORMATION SECURITY
Why digital scarcity matters.
Copyable files, transferable authority, least-privilege use and the potential to reduce host-visible information exposure.
Read the foundations → CHAPTER 01 / SOFTWARE MODELInside the access protocol.
Minting, independently encrypted sections, threshold contributions, two fresh observations and the exact receipt/freeze boundary.
Read the protocol → CHAPTER 02 / DEVICE DESIGNThe protected-device path.
Competing threshold providers and compulsory hardware, fixed trust anchors, protected unit processing and the hostile-host test plan.
Read the hardware architecture → CHAPTER 03 / INFRASTRUCTURETeranode and scale.
Distributed transaction-processing services, state and storage, throughput context and the separate rates of settlement and device use.
Read the scalability analysis → CHAPTER 04 / PUBLISHED RECORDSInventions and protection.
Eight linked US patent grant publications covering related key, recovery, credential, content and exchange mechanisms.
Read the patent register → ASSURANCE / ADVERSARIAL MODELWhat the protection means.
Current software limits, future device guarantees, collusion, output leakage, privacy and the obligations created by recovery.
Read the security model →