Digital scarcity should give a person something they can genuinely hand to somebody else. For INTEGYRS, the object is the usable digital item: the book, film, program or other protected work. The ambition is that Alice can transfer that item to Bob, Bob can use it, and Alice can no longer obtain fresh access through the possession she transferred. A change of name in a registry is insufficient if both people retain unrestricted use of the same item.
That ambition has an economic purpose. Transferable possession could let people lend digital goods, sell them after use, move business entitlements between authorised users and permit computation without distributing unrestricted source material. It could also reduce the amount of information exposed to ordinary applications. Those benefits depend on enforcement, workable rights and a service people can rely on. Scarcity alone supplies none of them automatically.
INTEGYRS currently describes a software alpha and bounded private-node experiments. The host operating system can inspect the alpha’s keys and plaintext. Its proposed protected-device architecture is a further engineering objective, not an independently established production capability. The distinction matters throughout this article: the intended result is transferable possession of the item, while the strength of present implementation claims must follow the available evidence. INTEGYRS digital scarcity
Scarcity concerns usable possession
A digital file can be copied without depriving its sender of the original. Sending somebody an ordinary document therefore differs from handing over a physical book. Both parties may finish with a complete usable copy. Encryption protects content from people without the necessary access material, but it does not solve transfer if a former holder retains a reusable key and the encrypted file.
The relevant question is whether retaining bytes also preserves the ability to use the protected item. Encrypted storage can be replicated for resilience and delivery without granting every storage operator permission to read it. A recipient may already have the encrypted payload before receiving possession. The transfer must change which holder can turn that representation into a permitted use. INTEGYRS’s public explanation distinguishes this controlled use from ordinary file distribution. Why digital scarcity changes information security
Consider a limited edition of one hundred digital books. Each copy would need its own recognised identity and transfer history. The system must distinguish the hundred legitimate possessions from duplicated storage and reject competing claims to the same possession. Issuance policy matters too. A seller who promises one hundred copies cannot make that promise credible merely by preventing duplication of each record while quietly issuing additional recognised copies elsewhere.
Scarcity also differs from secrecy. A reader can learn what a book says. Selling a physical book does not erase memory, notes or an earlier photograph. The corresponding digital objective cannot plausibly mean removing information from a former reader’s mind. It means transferring the protected item and ending the former holder’s ability to obtain further use through it. Preventing unrestricted digital extraction remains important because a retained full plaintext copy could reproduce much of the item’s practical utility.
This is why an NFT is an inadequate description of the INTEGYRS objective. ERC-721 specifies an interface for tracking and transferring distinct tokens, with optional metadata. It does not itself require a protected reader or prevent copying media associated with a token. Additional systems can enforce access, but their guarantees must be assessed separately. INTEGYRS’s intended deliverable concerns possession of the usable work, not simply exclusivity over a token that refers to an openly available file. ERC-721 Non-Fungible Token Standard
A transfer must end the previous possession
A credible transfer needs a defined sequence. The system must identify the current possession, establish the intended successor, stop conflicting new uses and activate the successor under the agreed settlement rule. It must also recover correctly if a connection drops or a process fails halfway through. Otherwise, a pleasant demonstration could conceal a period when both parties can use the same possession, or when neither can recover it.
Timing needs particular care. INTEGYRS’s published protocol distinguishes an access authorisation that committed before a transfer freeze from a request arriving after it. In the reported software model, freeze-first refuses a new seller authorisation and an unused retained capability. An operation already authorised before freeze can finish afterward. This is a defined ordering rule, not a claim that every existing display vanishes at the moment somebody presses Transfer. INTEGYRS access protocol
For a buyer, the practical promise should be intelligible: when the transfer is complete, what can the seller still do, what can the buyer do, and what happens if the service is interrupted? The interface should expose pending states rather than announce success before the necessary conditions are met. A payment, if introduced, would need an equally clear rule for completion and failure. Updating possession does not by itself establish that money and the item exchanged atomically.
Previously issued permissions also need limits. A permission tied to one recipient, one operation and current state should not become an unlimited licence merely because its bytes can be copied. Old device snapshots and cached messages must not restore yesterday’s authority after today’s transfer. INTEGYRS identifies replay, rollback and stale observations as explicit threats. Checking a signature is useful, but a valid signature on an obsolete statement does not establish present control. INTEGYRS security boundaries
These requirements define the substance of digital possession. Transfer must change what the former holder can actually do within the enforced system. Accounting entries are evidence of that relationship, not a substitute for enforcing it.
Enforcement must reach the point of use
INTEGYRS separates possession records, encrypted content, access decisions and the receiving endpoint. A ledger contributes evidence about transactions. Access services decide whether a request is eligible. The endpoint is where protected material becomes usable. A failure at that last boundary can defeat restrictions imposed elsewhere. INTEGYRS technology
The proposed hardware approach would process only an authorised portion of a work inside a protected boundary. A reader might display a bounded content unit without assembling the entire book as plaintext in ordinary application memory. Video needs an appropriate decoding window rather than an unrealistically isolated frame. Reflowable books require stable content ranges because changing font size changes visual pages. These details determine what the protection actually covers. INTEGYRS hardware architecture
Protected key storage is only part of the task. If a device keeps its key secure but returns decrypted content to an application the user controls, the application can still copy that content. Protection must therefore cover the necessary processing and output path. Accessibility, search, annotations and diagnostic tools must be designed into that boundary rather than added as unrestricted escape routes.
Remote attestation can help a service evaluate evidence about a device, but it does not remove these engineering obligations. The IETF’s Remote ATtestation procedureS architecture describes evidence, verification and policy decisions, including the problem that relevant state can change after evidence is produced. For INTEGYRS, a resulting design requirement is to bind acceptable evidence to the operation, freshness policy and implementation being relied upon. Attestation cannot certify all future behaviour. RFC 9334, sections 10 and 12
The same discipline applies to distributing authority. Requiring several access-service contributions can avoid reliance on one participant, but a sufficient colluding group remains a defined threat. INTEGYRS’s proposed combination of remote participation and a compulsory protected-device factor needs a construction that makes both genuinely necessary. Merely addressing a response to a device does not prove that a malicious group cannot bypass it. The public architecture identifies this as work requiring separate validation. INTEGYRS technology
What transferable digital items could deliver
The following applications are economic possibilities, not announcements of completed INTEGYRS products. Their value follows from a common change: the same recognised possession can pass between people without authorising an additional concurrent possession each time.
Books and other digital publications
A transferable digital book could have a life after its first purchaser finishes reading it. It could be given to a friend, lent under agreed terms or resold where the relevant rights permit. Publishers could offer different products with explicit conditions, including personal copies, transferable editions and temporary access. Readers would know what they were buying before purchase.
For the reader, a credible resale opportunity can reduce the expected cost of ownership. A purchaser might pay more for an item they expect to sell later than for access that ends with their account. That is an economic mechanism, not a prediction that every digital book will gain resale value. Demand, fees, condition rules, availability and the publisher’s future issuance policy would still influence the outcome.
Authors and publishers would face choices rather than a guaranteed windfall. Secondary sales might reach readers who would not buy a new copy, but might also replace new sales. Transfer charges could fund support or become barriers that destroy the benefit. Royalties would require agreed rules and an enforceable route through the relevant market. Scarcity does not by itself make buyers want a work or oblige them to pay its creator on every later transaction.
Lending and shared collections
A library or an organisation could acquire a defined number of transferable possessions and lend them sequentially. A borrower would receive the permitted use while the corresponding lender-held use was suspended. Return would reverse that relationship. The number of purchased possessions and their lending conditions would be explicit.
Such a model would need to earn its place against existing licensing arrangements. Waiting lists and restrictive terms can undermine access. Preservation, accessible formats and continuity if an operator closes are essential parts of a collection’s usefulness. A technically successful system that strands a library’s purchases would fail the institution even if its duplication controls worked perfectly.
Business software and equipment entitlements
A business could move a licensed tool or equipment entitlement from one authorised team to another without leaving the previous installation usable under the transferred possession. This could make unused entitlements easier to identify and reallocate. The practical value would be fewer redundant purchases and clearer responsibility for the rights already acquired.
Interoperability would be decisive. Buyers need to know whether they can change service provider, replace failed hardware or reorganise their business without losing the item. Transferability restricted to one fragile service can amount to little more than another account-management feature. Commercial terms and recovery arrangements must support the technical lifecycle.
Protected data and computation
Some transactions need a result rather than a copy of all underlying information. A purchaser might need a calculation over a licensed dataset or permission to execute a protected program on an approved input. A system that confines processing to the agreed operation could make such transactions possible while reducing unnecessary disclosure.
The output is part of the security problem. Repeatedly asking carefully chosen questions can reveal information even when no single response contains the whole source. A useful design therefore needs cumulative output limits, an appropriate query policy and a clear definition of what the recipient may learn. Permission to compute cannot quietly become permission to export the protected material through thousands of small answers. This is an explicit consideration in INTEGYRS’s public protected-output design. INTEGYRS security boundaries
These uses point towards a broader commercial opportunity: selling controlled use with a transferable lifecycle, while retaining efficient encrypted storage and distribution. The benefit must be measured as a useful outcome for the customer. More transactions, tighter restrictions or a higher token price would not establish that outcome.
Technical possession and legal rights must agree
A system can recognise a holder without deciding every legal right that person has. Possessing a copy of a book does not automatically confer its copyright. Permission to read, lend, resell, modify or commercially exploit a work may involve different rights. INTEGYRS’s current public description expressly separates its possession model from copyright management and copyright transfer. INTEGYRS digital scarcity
There is a useful legal parallel in the United Kingdom’s Electronic Trade Documents Act 2023. For the trade documents within its scope, section 2 requires a reliable system with features including identification of the document, protection against unauthorised alteration, exclusive control and transfer that deprives the former controller of control. Merely reading or viewing the document is not control for this purpose. Section 3 then provides for possession of qualifying electronic trade documents. Electronic Trade Documents Act 2023, sections 1 to 3
The parallel is instructive because it connects recognised possession with effective transfer and the distinction between an operative document and its copies. Its scope is limited. It does not make every ebook a trade document, authorise every resale or establish that INTEGYRS satisfies the statutory requirements. Each proposed market still needs an appropriate legal and contractual basis.
Patent publications require similar precision. US12367468B2, granted on 22 July 2025, names Craig Steven Wright and Stephane Savanah as inventors and describes blockchain-mediated distribution of digital-content episodes with associated payment and key mechanisms. It is a relevant published technical reference. It does not prove that a deployed INTEGYRS reader prevents extraction, establish universal digital scarcity or demonstrate INTEGYRS’s ownership of the patent rights. US12367468B2, abstract and claim 1
Scarcity carries costs and obligations
Controls can create valuable options, but they can also impose friction. A person who has legitimately acquired a book still expects it to open. If every useful operation depends on fresh remote participation, outages and network delay become part of the reading experience. INTEGYRS’s public alpha description says its access path is online; research into later proof mechanisms should not be confused with an available offline mode. INTEGYRS digital scarcity
Smaller protected units can reduce the amount of plaintext exposed at once, while increasing requests, metadata and transitions. Hardware assurance, independent service operators, updates and recovery also cost money. A low blockchain transaction fee would not establish a low total cost of ownership. The relevant calculation includes the device, access service, support, failures and the time users spend resolving them.
Recovery creates a difficult obligation. If a lost device can be replaced, the old device must not retain an equally valid possession. If a lost owner key can be recovered, somebody must possess the authority to approve that recovery. That authority can rescue a legitimate owner or become a route for mistaken or abusive reassignment. Buyers need explicit rules, evidence requirements and a dispute process. The public roadmap treats these as design questions rather than finished guarantees. INTEGYRS roadmap
Privacy matters as much as confidentiality of the work. A system can hide a book’s contents while revealing who reads it, when and how often. Transaction histories, access requests and recovery records need their own minimisation and retention policies. The ability to enforce possession should not become an excuse to collect a complete account of somebody’s reading or work.
There is also a basic allocation decision. Many digital resources are more useful when freely reproducible. Open research, public information and deliberately shared software do not gain value merely because copying can be restricted. Scarcity is justified where transferable control solves an actual problem and its benefits exceed its costs. The goal should be a useful additional form of digital possession, with clear choices for creators and buyers.
What must be demonstrated next
The public evidence register describes recorded software tests, isolated BSV private-node work and deliberately forced transfer-order cases. It distinguishes these observations from real protected-device operation, independent security review and production public-network settlement. Reading that register verifies what the project reports. It is not an independent rerun of its private tests, and the article makes no claim to have performed one. INTEGYRS evidence register
The next convincing demonstration should make the intended item tangible. A rights-cleared publication should pass between two qualified endpoints. The buyer should obtain the promised use. Attempts by the former holder to regain access through retained permissions, restarted software or an old device state should fail within the declared threat model. Interruption and recovery should preserve a single recognised possession without silently discarding a legitimate buyer’s item.
Hardware evaluation must then show that the ordinary host cannot extract protected keys or content through the claimed path. Independent review should examine the protocol’s composition and the assumptions about service-provider collusion. Usability testing should measure successful access and false refusals separately. Costs and recovery times should be measured on the actual supported configuration. These are the kinds of acceptance conditions identified in the public development roadmap. INTEGYRS roadmap
If INTEGYRS establishes those properties, it will deliver a practical capability: digital items whose possession can change hands while their permitted use follows the new holder. That could support secondary markets, lending and controlled computation without requiring unrestricted distribution of the work. The economic value will come from what people can safely do with those items, the rights they receive and the reliability of the system supporting them.
The ambition remains possession of the digital item itself. Delivering it requires the protocol, device, operating service and legal terms to uphold the same promise.
References
All links and the specific claims attributed to them were checked on 5 November 2026. INTEGYRS pages are primary project statements, not independent assurance. Application examples and economic consequences in this article are analysis, not measured market forecasts.
- INTEGYRS. Digital Scarcity. Current scope, transfer objective, online access and separation from copyright.
- INTEGYRS. Why digital scarcity changes information security. Copyable storage, possession and controlled use.
- William Entriken, Dieter Shirley, Jacob Evans and Nastassia Sachs. ERC-721 Non-Fungible Token Standard. Created 24 January 2018. Token ownership and transfer interfaces, and optional metadata.
- INTEGYRS. Protocol authority and access lifecycle. Access ordering, authorisation and transfer boundaries.
- INTEGYRS. Security and trust boundaries. Host compromise, replay, rollback, collusion and protected output.
- INTEGYRS. Technology and device architecture. Component responsibilities and proposed device-dependent architecture.
- INTEGYRS. Hardware trust and protected-device architecture. Proposed bounded processing and output requirements.
- Henk Birkholz, Dave Thaler, Michael Richardson, Ned Smith and Wei Pan. Remote ATtestation procedureS (RATS) Architecture. RFC 9334, January 2023, especially sections 10 and 12.
- United Kingdom. Electronic Trade Documents Act 2023, chapter 38, sections 1 to 3. Scope, reliable systems, control and possession.
- Craig Steven Wright and Stephane Savanah. Blockchain-implemented method for control and distribution of digital content. US12367468B2, published 22 July 2025, abstract and claim 1. Patent text reproduced by Google Patents.
- INTEGYRS. Evidence and experimental results. Dated project-reported checkpoints and limitations.
- INTEGYRS. Product roadmap and acceptance gates. Proposed hardware, review, pilot and recovery requirements.