Enforcement layer for digital rights

Verification tells you who someone is.
It was never built to tell you what they're allowed to do.

Every digital asset gets defined at issuance and checked at transfer. Almost nothing happens in between. That middle gap, the space where royalties get skipped, licensing terms get ignored, and rights outlive the conditions attached to them, is what TrustLogic exists to close.

Table 1: Closed systems protect rules but trap value. Open systems capture both, or neither.
Condition Closed system Bearer token / NFT TrustLogic
Issuer can revoke on misuse Yes No Yes
User loses seed phrase Recoverable Lost Recoverable
Rules survive the transfer Persist End at transfer Persist
Asset stays open to trade Locked in Liquid Liquid
Wrapping bypass Not applicable Easy Blocked by design
The gap

Digital assets are programmable. They were never made enforceable.

Most tokens function like bearer instruments: whoever holds the token holds the authority. Once it moves, the issuer has no way to compel compliance, no matter what the smart contract says on paper.

01

Marketplaces choose what to honor

Royalty logic, transfer restrictions, and licensing terms only execute if the platform in between chooses to call them. Several major marketplaces have simply turned that logic off.

02

Wrapping strips the rules

An asset placed inside a wrapper contract can be issued as a new, unrestricted token. Whatever obligations were attached to the original never make the trip.

03

Enforcement depends on an operator

Some standards give issuers freeze and forced-transfer powers, but the obligation itself does not live in the asset. If no one acts, or the asset has already moved somewhere that never checks, the restriction quietly disappears.

Architecture

Authority and rights are held separately, on purpose.

The asset never leaves custody. What moves is a governed, revocable claim to the rights the asset represents. That single separation is what makes the rules survive a transfer.

Trustee Token

Authority

Held exclusively by the trustee. Encodes the rule set: licensing terms, transfer conditions, royalty structure, revocation triggers, and compliance requirements.

  • Never held by the end user
  • Cannot be wrapped or transferred
  • Changes only through time-delayed, governed rule updates
Beneficiary Token

Rights

A revocable, soulbound receipt held by the user. Represents the rights granted under the rules, not ownership of the underlying asset itself.

  • Transfers only via trustee-validated burn-and-mint
  • Can be suspended, restored, or revoked under the rule set
  • Carries no personal data on-chain

Why soulbound, and why burn and mint? A token that transfers like cash can land in a wallet, a wrapper, or a protocol that never checks the rules. Soulbinding closes that bypass. Burn and mint makes every change of hands a governed re-issuance: the rules are re-checked and re-encoded for the new holder, and the new token stays tied to the same trustee relationship. The right moves. The authority does not.

Where enforceability matters

Once rules can survive a transfer, whole categories of asset open up.

Fifteen examples of one pattern: an economic right moves, but a restriction, obligation, or authority has to remain.

Creator rights

Royalties that survive resale

A song or artwork license is assigned or sublicensed. Royalty, territory, term, and attribution travel with every downstream holder.

Sanctions

Rules that apply after receipt

A holder is sanctioned after the asset is already in their wallet. The position can pause without waiting for a transfer.

Courts & disputes

Orders, liens, garnishment

A court order attaches to a position. An authorized party executes it with an audit trail, and restores it on resolution.

Securities

Transfer restrictions that persist

Accreditation, holding periods, and jurisdiction limits stay attached through secondary transfers.

RWA & DeFi

Collateral eligibility

A tokenized fund interest is valid collateral today. Its status can be updated after deposit if eligibility changes.

Stablecoins

Reserve and backing events

If backing is impaired, affected positions can pause pending review instead of circulating as if nothing changed.

Public funds

Purpose-bound aid and benefits

Grants, aid, and benefits stay spendable while merchant, category, geography, and cap rules continue.

Insurance

Proceeds and claims

Payouts stay tied to their purpose. Claims carry canonical state, fraud review, suspension, and duplicate protection.

Capital formation

Governed draw control

Reg CF and Reg A funds, construction loans, and escrow release against vendors, budgets, and milestones.

AI agents

Spending within limits

An agent spends autonomously while the company keeps authority to change scope, suspend, or revoke.

Data rights

AI training licenses

A model receives training rights while the licensor keeps authority over scope, duration, and revocation.

Compensation

Vesting and clawbacks

Equity and bonuses can move or mature while clawback and forfeiture conditions remain enforceable.

Ticketing

Resale and access rules

Price caps, transfer limits, and access windows hold through every resale.

Carbon markets

Retirement and double counting

A credit's retirement status and eligibility stay with it, so a second claim can be blocked.

Regulated goods

Lineage and chain of custody

Origin, licensing, and compliance status follow the product through each change of hands.

See them working: trustlogic-demos.replit.app

How they fit together

ERC-3643 governs transfer compliance. TrustLogic keeps the obligation with the asset.

ERC-3643 (the T-REX standard) is a real, adopted standard for regulated security tokens, with powerful administrative controls including freeze, recovery, and forced transfer. TrustLogic addresses a different question: how a continuing obligation stays represented and enforceable as rights move, rules change, and events occur between transfers. It is designed to integrate with ERC-3643, not replace it.

Comparison: transfer compliance and persistent obligations
Dimension ERC-3643 (T-REX) TrustLogic
Core model Single permissioned token; compliance logic runs inside the token itself Dual-token: authority (Trustee Token) held apart from rights (Beneficiary Token)
What's enforced Eligibility to hold or receive the token: identity, jurisdiction, investor caps, lockups Continuing obligations after transfer and between transactions: royalties, licensing scope, sanctions, eligibility, suspension
Identity handling On-chain identity claims (ONCHAINID) tied to the holder's wallet Verified off-chain by the application layer; only non-PII attributes reach the trustee
Revocation Issuer or agent can freeze, force-transfer, or recover the token directly Rights suspended, revoked, or restored by a persistent authority relationship, with a structured dispute path and audit trail
Primary domain Regulated securities and tokenized real-world assets Cross-category: IP, royalties, licensing, AI datasets, payments, aid, and RWAs
Programmable money

Policy remains sovereign. Implementation becomes programmable.

TrustLogic separates the monetary anchor from the transferable monetary claim. The Trustee Token anchors the governing relationship to the settlement asset and monetary authority. Beneficiary Tokens carry the claims people actually hold and move: USD, USDC, and other regulated dollar instruments. TrustLogic provides the architecture. It does not operate the system or become a central authority.

BIS test

Singleness

Different forms of money should exchange at par because they reference a common safe settlement asset.

The Trustee Token anchors every governed claim to that settlement asset or monetary authority. The representations may differ. The authoritative monetary relationship does not.

BIS test

Elasticity

Money must expand and contract as conditions require, under the authority of the monetary system.

Issuance, redemption, reserve, and liquidity rules live in the Trustee layer. When the authorized institution changes them, outstanding tokens follow without wholesale reissuance. The institution supplies the capacity; TrustLogic makes the rules executable.

BIS test

Integrity

Money must stay governed against fraud, illicit finance, and sanctions violations after issuance.

Compliance does not stop at onboarding or transfer. Sanctions, eligibility, spending, freeze, and review conditions operate while money is held and between transactions, with identity kept off-chain and human review where required.

Credentialed Sovereign Governance

A hierarchy of DAOs, each publishing and updating the rules within its scope. Membership is tied to credentialed institutional roles rather than individuals, so authority follows the office when personnel change. Every instrument inherits the applicable rules at creation, and existing Beneficiary Tokens keep referencing the same Trustee relationship, so updated rules propagate without wholesale reissuance. Institutional authority, represented and propagated. Not anonymous token voting.

Layer 1

Global standards DAO

BIS-level standards for singleness, elasticity, integrity, and reserves.

Layer 2

Central bank DAO

Translates those standards into monetary policy, reserve requirements, and elasticity parameters.

Layer 3

National regulator DAO

Sets licensing, AML/CFT, sanctions, and reporting rules for issuers operating in-country.

Layer 4

Issuer DAO

Issues the stablecoin or tokenized deposit, which inherits every applicable rule above it.

TrustLogic is implementation architecture. Outcomes depend on how rules are configured and governed; no deployment automatically satisfies a legal requirement. For the stablecoin one-pager, GENIUS and CLARITY context, and demos, see the TrustLogic overview.

On the public record

Regulatory filings

TrustLogic's approach is on record with the SEC in three filings, each addressing the gap between verifying who holds an asset and enforcing what happens after.

March 2026SEC Crypto Task Force
Technical submission

Structural Enforcement Standards for Digital Assets

Smart contracts execute; they do not enforce. Proposes a dual-layer architecture grounded in trust law, with worked examples in tokenized securities, real estate, and on-chain lending.

Read the submission (PDF)
April 2026Petition for rulemaking
Ref. S7-2026-09

Continuous Control Framework for Digital Assets

Asks the Commission to recognize persistent-enforcement digital asset systems: architectures where the conditions governing an asset keep operating after it changes hands.

Read the petition (PDF)
August 2026Public comment
Regulation Crypto Assets
File No. S7-2026-27

Comment on Regulation Crypto Assets

Brings the BIS tests of singleness, elasticity, and integrity to a live SEC rulemaking, and introduces persistent enforceable state as a regulatory concept.

Read the comment (PDF)
Positioning
Closed systems protect the rules but trap the value. Open systems with embedded enforcement capture both.
On why TrustLogic is a method, not a platform

The same way double-entry bookkeeping or Dolby became a method any institution could implement, TrustLogic is designed to be embedded in assets at creation across existing marketplaces, custodians, and chains, not to replace them. Phase one of digital assets was tokenization. Phase two is enforcement.

Where things stand

Protocol status

Filing

Core dual-token trust architecture is the subject of a U.S. non-provisional patent application filed December 31, 2025 and published as US 2026/0211982 A1, with additional applications pending.

Regulatory engagement

Three SEC filings on record: a Crypto Task Force technical submission, a petition for rulemaking, and a comment on Regulation Crypto Assets.

See the filings

Deployment

Working pilot in development for purpose-bound institutional disbursement, alongside active integration discussions across licensing, compliance detection, and tokenization infrastructure.

Get in touch

If your rules don't survive the first transfer, they were never rules.

For licensing conversations, institutional pilots, partnership discussions, or press inquiries, reach out directly.

Direct contact
Amy Pearson
Founder, TrustLogic