Free · Open · Vendor-honest

Real-world asset infrastructure, explained properly

The open knowledge base from the team that builds the rails. How qualified custody actually works, what a compliance gate really is, how permissioned tokens enforce eligibility on-chain — written for the people who have to defend these decisions in a diligence review, not just nod along in a demo.

Learning tracks

Three tracks, from first principles to production

Sequenced reading paths. Each article stands alone; the track gives it order.

Foundations

RWA Tokenization 101

For allocators, counsel, and operators new to the space. No prerequisites.

  1. What a tokenized real-world asset actually is (and isn't)
  2. Custody vs. self-custody vs. "we use secure wallets"
  3. Why 2-of-3 multisig is a structure, not a promise
  4. Permissioned vs. permissionless tokens
  5. What a compliance gate does before value moves
Practitioner

Running an Issuance

For issuers and program managers taking an asset to institutional markets.

  1. KYC/KYB, sanctions, and Travel Rule — what gates what
  2. ERC-3643 & ONCHAINID: eligibility enforced on-chain
  3. Cap tables, investor registries, and forced-transfer recovery
  4. Choosing a settlement environment: EVM, XRPL, or an L1
  5. The audit trail your regulator will actually ask for
Architect

Building the Rails

For engineers building on or integrating with RWA infrastructure.

  1. Deterministic settlement: integer math, no wall-clock, no floats
  2. Oracle attestations: EIP-712, m-of-n, replay protection
  3. Atomic patterns: DvP and payment-for-obligation swaps
  4. Webhook security: HMAC verification and idempotency
  5. Multi-tenant isolation and compliance-gated routing
Flagship guides

The long-form references

Deep, citable, and honest about trade-offs — including the ones that don't favor us.

Guide Coming soon

Not All Custody Is Custody

Qualified custodians, trust charters, MPC vendors, and the marketing fog between them — how to tell who actually holds what.

Guide Coming soon

The Compliance Gate

Pre-settlement enforcement vs. post-trade reporting — the architectural difference and why regulators increasingly care.

Guide Coming soon

Permissioned Tokens, Explained

ERC-3643, identity claims, transfer restrictions, and recovery — how a security token stays a security under scrutiny.

Guide Coming soon

40 Questions to Ask Any RWA Vendor

The diligence checklist — including every question that's uncomfortable for us. Use it on Unykorn too.

Glossary

Terms, defined the way diligence uses them

A sample of the full glossary — each term links to its long-form entry.

Qualified Custodian
A regulated entity (e.g., an OCC-chartered trust bank) legally permitted to hold client assets in a fiduciary capacity. A software vendor with "secure wallets" is not one.
2-of-3 Multisignature
A wallet requiring any two of three keys to move value. Distributing the keys across client, platform, and custodian removes unilateral control cryptographically.
Compliance Gate
Enforcement placed in the transfer path itself, so an ineligible transaction never executes — as opposed to screening that flags it afterward.
Travel Rule (IVMS101)
The FATF requirement that originator and beneficiary information travel with value transfers above threshold, exchanged between VASPs in the IVMS101 data format.
ERC-3643 (T-REX)
An EVM standard for permissioned security tokens: identity-bound holdings, modular compliance checks on every transfer, and issuer recovery mechanisms.
Atomic DvP
Delivery-versus-payment where the asset and its payment settle in one indivisible transaction — either both happen or neither does.
Oracle Attestation
A signed, replay-protected statement bringing off-chain fact (a meter reading, an inspection, a price) on-chain with verifiable provenance.
Append-Only Audit Trail
A record that can be added to but never edited or deleted, with each entry cryptographically signed — verifiable without trusting the vendor that produced it.
The Unykorn principles

The standards we build to — published, so you can hold us to them

These read like engineering rules because they are. Every product on unykorn.ai is built against this list.

Compliance is a gate, not a report

Eligibility is enforced before value moves. If a transfer fails the check, it never executes — there is nothing to unwind, reverse, or explain.

Never the custodian

The client holds a key. The qualified custodian holds a key. The architecture — not a policy document — makes unilateral movement impossible.

Integer money, deterministic state

No floating point in any money path. No wall-clock dependence, no unseeded randomness in settlement. The same inputs always produce the same state.

The record outlives the vendor

Every decision and transfer is signed into an append-only trail that clients can export and verify independently — including after we're gone.

No transaction-contingent fees

We are paid to run infrastructure, never on volume — so our incentives can't drift toward throughput over safety.

Label the roadmap honestly

If it isn't live, it says "In development" — on the site, in the deck, and in the data room. A diligence team should never discover a gap we didn't disclose first.

Ready to build?

Learning done — the rails are one door over

The commercial platform lives at unykorn.ai. Developer documentation and the x402 engine live under unykorn.ai/docs.