Integer minor units only
All financial and token math runs on integers. No floating point touches a value path anywhere in the stack. A rounding bug in a settlement engine is not a bug you find in production.
Live · donkai.org
The portfolio stops being a list.
The portfolio stops being a list.
It becomes a system you can ask.
Donkai is the simulation and agent layer of the UnyKorn stack. It gives every entity, asset and platform a state, a health record, a topology and a procedure — and then puts an assistant in front of all of it that will tell you the truth about what is built, what is gated, and what we flatly will not do.
DONK
It knows every surface in the estate, the whole architecture, the engagement model and the boundary. It runs on the edge for you and on our own hardware for us. It does not invent figures, it does not name clients, and it does not hand out keys — and those are not house rules written on a poster, they are three independent layers of code you can read about on how DONK works.
DONK
Simulation & agent layer · guarded
Public tier
DONK
I'm the assistant on the Donkai layer. Ask me how any of this works and I'll answer straight — including the parts we refuse to do, which is usually the more useful half.
Good places to start: what UnyKorn actually is and is not, how custody works without us being the custodian, what a tokenization readiness review costs you, or which of the forty-odd surfaces is the right door for what you're holding.
UnyKorn is the plumbing. That is the whole positioning.
Clients keep their own assets, their own bank, their own custodian and their own lawyers. We supply the software that makes those parts talk to each other, and the evidence trail that proves what happened. Everything else on this page is detail underneath that sentence.
What it is
- A technology rails and infrastructure gateway provider.
- The architectural layer under real-world asset distribution, digital-asset integration and tokenization workflows.
- Software you can license, deploy white-label, or have us run as an operating layer.
- An evidence system — append-only, hash-chained receipts that survive a diligence review.
What it is not
- A lender. No balance sheet goes into a deal.
- A bank. Deposits sit with a chartered partner, never with us.
- A custodian. Qualified custody is delegated; we never hold client assets.
- A broker-dealer, an investment adviser, or the issuer of anyone else's security.
The published phrase for the custody posture is custody without being the custodian. It is not a slogan — it is a structural fact about where the keys live, and the next section shows you exactly where they live.
Seven layers, in plain language
No diagram here does more work than the words. If any of this needs to go deeper — down to the contract family, the hook, or the saga state machine — ask DONK and it will go there.
-
Identity spine
Who a party is, proven once and reusable across every asset they touch. On-chain identity attestations; ERC-3643 / T-REX and ONCHAINID on the EVM side. Prove it once, not once per deal.
-
Compliance gate
The rule that decides whether a transfer is permitted at all, enforced at the token level rather than by a person watching a screen. The bank owns BSA/AML, CIP, OFAC and monitoring. The client's VASP or custodian owns the Travel Rule. We execute technology only — that split is written into the engagement, not assumed.
-
The quorum is you plus your custodian Custody
Non-custodial, multi-signature. Three keys: the client's, an offline backup, and the custodian's. The spending quorum is client plus custodian. Where an UnyKorn share exists at all it is an encrypted offline recovery share and is never an online signer — which is the difference between a non-custodial claim that is true and one that is decorative.
-
Deterministic two-phase saga Settlement
XRPL Hooks and MPTs, Stellar, EVM chains, and a native Rust L1 engine. Fiat legs run through the chartered bank: RTP and FedNow for instant 24/7 movement, ACH and Same-Day ACH, domestic and international wires, push-to-card payouts. Fiat-to-stablecoin ramps run as a deterministic two-phase saga under one ramp identifier.
-
Six blocks before anything issues Issuance
The token, its legal wrapper, its rights model, its market controls, and the SPV that holds the asset. Six blocks are mandatory before anything issues: asset anchor, legal wrapper, token model, rights model, simulation model, market controls. Miss one and the readiness review fails — which is the point of running it before the money moves.
-
Evidence
Append-only, hash-chained receipts. Every state change writes a line; the chain verifies from genesis. Change one byte of any payload and verification fails at that line and names it. This is the layer most platforms skip, and the one that decides whether a diligence review ends well.
-
Simulation — this layer, Donkai
Digital twins of entities and instruments, scenario runs, health and gap detection, and an agent swarm that observes, flags and proposes repairs. Agents never execute a money move on their own. A human sits at every gate, and the gate is code, not a policy document.
Five engineering rules that are actually enforced
These are the ones that get argued about in a code review and win.
Everything is idempotent
Every API request and every sweep carries a cryptographic idempotency key with deterministic seed generation. A replay is safe by construction rather than by convention.
Safety beats automation
A partial multi-leg failure freezes and raises for human review. It does not attempt a clever cross-domain rollback. Automatic reversal across two settlement domains is how you turn one problem into two.
Zero public ingress
Production runs in isolated networks with static egress and no public inbound. The control plane reaches in; nothing reaches back out to it.
Every figure has an artifact
A number gets published only if someone can name the signed artifact behind it and the date on that artifact. If nobody can, the number does not ship. This rule has killed more of our own copy than anyone else's.
Agents are analysts, not operators
Where an agent has no tools on a run, its output is scanned for first-person action claims. A model that narrates work it did not do gets flagged and its receipt suppressed. A charter alone does not stop that — a regex does.
What Donkai adds on top
A registry tells you what exists. Donkai tells you what state it is in, what it is connected to, what is missing, and what happens if you change one variable.
Twins
A per-entity digital twin: the asset anchor, the legal wrapper, the rights and market controls, the lifecycle it is actually in. An instrument with a twin can be inspected instead of described.
Scenarios
What-if runs against a twin. Move a rate, change a maturity, fail a counterparty leg, and watch what the structure does before it does it with real money in it.
Nerve
Health, gap detection and the repair board. The state that matters is not up or down — it is thin: a surface returning HTTP 200 with nothing behind it, which every naive monitor calls green. Nerve catches those.
Agents
A fleet that observes, flags and drafts. Zero cost per call because inference runs on our own hardware. Every real action writes a receipt; a fabricated one writes nothing and raises a flag instead.
Donkai is one layer. The Gate is the whole thing.
Donkai simulates and operates. Underneath it sit the identity spine, the compliance gate, custody, settlement and issuance — the UnyKorn stack. Same evidence discipline all the way down, same perimeter at every layer.
The Gate
The mark is a ring with a chevron through it, and it means what it looks like: a thing you pass through, with a rule about who gets to. Every layer under Donkai is a gate in that sense — identity proven once, a transfer permitted or refused at the token level, a quorum that needs two keys, a receipt written before the act.
Donkai is where you watch all of that run, ask it questions, and find out what is missing before it costs you.
The estate
Every public surface, with what it is for. Demonstrations are labelled as demonstrations and their inventory is fictional — that label is deliberate and it stays. This table is loaded live from the same registry DONK answers from, so it cannot drift from what the assistant tells you.
| Surface | Group | What it is for |
|---|---|---|
| Loading the registry… | ||
Flat fees, published, no percentage of anything
You never pay a percentage of a recovery, of a raise, or of assets under management. Where an introducer is paid, that share comes out of our flat fee — never out of your money. These are the doors people actually come through.
Tokenization readiness review
Is this asset actually issuable, and what is missing. You get a written gap list against the six mandatory blocks, not a pitch deck. Most reviews end with a short list of legal and data problems that would have surfaced far more expensively later.
Forensic investigation
Blockchain fraud tracing and a report you can hand to counsel or law enforcement. The first check is free and it is a real check, not a lead capture. Flat fee from there, never a percentage of what is recovered.
Software licensing
White-label the issuance and settlement stack and run it under your own brand, your own bank relationship, your own custodian. We ship the rails and the receipts; the client relationship stays yours.
Operating layer deployment
The portals, the gates, the approvals and the receipt chain, deployed and run for you. A human at every gate, and the gate enforced in code rather than in a policy PDF nobody reads.
Integration engineering
You already have a platform and you need it on the rails. Identity spine, compliance gate, settlement legs, receipts. Scoped as a fixed engagement against a written interface list.
Machine payments gated
x402 endpoints priced for software agents rather than humans — pay-per-call, no account, no invoice. Five endpoints are priced; settlement is gated on an external step, and the Foundation Report labels it that way rather than calling it live. Worth starting the conversation now if you are building an agent that needs to buy from an API.
Not sure which one? Describe what you are holding to DONK and it will route you, or book time with the desk at meet.unykorn.ai.
What we will not do
Published on purpose. Selling the constraint is more useful to a serious counterparty than selling the capability, and it saves both sides a month.
Take custody
We will not hold your assets. The quorum is you plus your custodian, and no configuration exists in which we can move anything alone.
Fund the deal
We will not lend our own balance sheet or put capital into a transaction we also build the software for. That conflict does not get managed; it gets avoided.
Be the broker-dealer
We are not a BD, not an RIA, and not the issuer of anyone else's security. If your structure needs one, you need a different counterparty and we will say so on the first call.
Price on a percentage
No percentage of recovery, of raise, or of assets under management. Flat fees only, so the incentive to inflate a number does not exist.
Publish an unbacked figure
If a number cannot be traced to a signed artifact with a date and a named signer, it does not go on a page, in a deck, or in DONK's mouth.
Put your name on a public surface
No client name, no deal economics, no counterparty. Not on the site, not in a case study, and not in this chat.
The record
Every figure below is lifted from the Foundation Report, which renders from a published evidence ledger and labels each number by how well it is actually known. The labels are the product. A number without one does not go on this page, into a deck, or into DONK's mouth.
THE LABELS
Six ways of knowing a number
MEASURED — produced by a command, an API call or an on-chain read, and re-runnable today.
CAPABILITY — the code exists, builds, and its tests pass. No production measurement yet.
GATED — complete, blocked on an external step. The blocker is named; the counterparty is not.
IN DEVELOPMENT — incomplete, with the remaining gap named out loud.
TARGET — forward-looking, carrying a target date.
ABSENT — deliberately not built, or not on file, with the reason stated.
273 repositories
On the public GitHub account. 153 of them cloned and counted: 1,656,705 lines of code.
322 proxied hosts
Across 16 zones. 120 serve real content, 60 are stubs, 121 are dead and awaiting retirement, 21 are dark. The report counts its own dead hosts out loud.
419 checks passing
Served-site checks against live domains — a real HTTP request every time, never a source-code read.
0 percentage fees
Zero percentage-of-recovery pricing, enforced in the compensation standard. A rule, not a state that can quietly drift.
17 Rust L1 workspaces
On disk — and none on a public mainnet. The second half of that sentence gets published every time the first half does.
478 sanctioned addresses
Loaded into the free screen, alongside 43 scam patterns evaluated in your own browser with nothing uploaded.
No LEI
No GLEIF Legal Entity Identifier is registered. The report says so plainly rather than leaving a blank for someone to fill in. If you are shown one, it is not ours.
0 client names
No client or partner name is published, because none is on file with consent. That is the whole reason this site has no logo wall.
Read the Foundation Report →
Edition 1.1, September 2026. Eleven chapters, four appendices, a stated methodology and a hashed document register.
Open source
The contract library, the settlement engines, the research chains.
Published engine
The Genesis Rust engine on crates.io — 388 test functions, labelled CAPABILITY, not production.
Research
Three works on the ORCID record, DOIs on Zenodo and SSRN. Download counts deliberately omitted as too volatile to publish.