Use cases

Six institution types. One conformance standard.

Ward gives tokenized credit a standard answer to the hardest question: what happens when something goes wrong? The answer is deterministic, auditable, and never dependent on Ward holding a key.

01

The 3 AM Default

A borrower defaults — not at a convenient hour, not when the risk committee is assembled, but at 3 AM on a Sunday. In the traditional model, nothing happens until people wake up, convene, review, and decide. Depositors wait, exposed, while discretion plays out over days.

Ward removes the wait, because it removes the decision. The moment the default is recorded on-ledger, Ward runs its checks against live ledger state — solvency, coverage, eligibility, replay protection — and produces an unsigned settlement instruction. The institution signs. The chain settles. Ward is never a counterparty, never a custodian, never a signatory.

The outcome a committee would have reached after a week of review is reached in seconds — and reached identically, every time. The 3 AM default and the 3 PM default resolve the same way, because resolution was never a matter of judgment. It was always a matter of fact.

02

The Auditor Who Doesn’t Have to Trust You

A regulator asks you to account for every default resolution last quarter: who was paid, why, and on whose authority. In a discretionary system, this means producing minutes, justifying decisions, defending judgment calls — and the regulator still has to trust that your record reflects what actually happened.

With Ward, there is nothing to defend, because there were no decisions to make. Every resolution leaves a record drawn entirely from the ledger: which credential verified the counterparty, which permissioned domain authorized them, which checks passed, what settled. No committee. No discretion. No story to corroborate.

The auditor doesn’t review your judgment — there wasn’t any. They replay the on-chain facts and arrive at the identical result. Compliance stops being a narrative you tell and becomes a computation anyone can verify. You’re not asking the regulator to trust you. You’re handing them the means to check.

03

The Permissioned Lending Market

A consortium of regulated institutions wants to lend to one another on-chain — but only among verified, authorized counterparties. Their regulators forbid exposure to anonymous addresses. For years, that requirement alone kept them off public ledgers.

The XRP Ledger now closes that gap: live, on-mainnet standards let institutions define exactly who participates. Members hold verified credentials; the domain enforces the perimeter; identity stays off-chain while authorization stays provable. But the perimeter only governs who can transact — it says nothing about what happens when credit inside it defaults.

That’s where Ward operates. When a default occurs, Ward resolves it scoped to the domain’s authorized members — confirming, at the moment of resolution, that the claimant is a credentialed participant, and producing the record that proves it. The consortium gets a market that is compliant at its edge and deterministic at its hardest moment. Ward is among the first to put that live compliance stack to work.

04

Tokenized Real-World Credit

A fund brings real-world credit on-chain — trade finance, private loans, invoices — as tokenized assets. Investors hold transparent, liquid exposure to cash flows that once lived in spreadsheets and PDFs. The promise is real. So is the unanswered question: what happens when the underlying loan goes bad?

Tokenization makes ownership transparent but inherits credit’s oldest problem — default resolution that depends on someone’s discretion, somewhere off-chain. Token holders are asked to trust a process they can’t see. Ward replaces that trust with determinism: defaults resolve against on-chain state, scoped to verified holders, with an auditable record of every step.

And because Ward verifies relationships — ownership, collateral, loan state, solvency — rather than any single chain’s mechanics, its model is built to follow tokenized credit wherever it settles. The resolution layer is rail-agnostic by design. Tokenization finally has an answer for the question that matters most: not how the asset trades, but how it resolves when it fails.

05

Shadow Mode

An institution is intrigued but unwilling to route live capital through deterministic resolution on day one. They’ve been burned before by systems that did the wrong thing quickly. Reasonable. Ward doesn’t ask for a leap of faith.

In shadow mode, Ward runs alongside the existing process. Real defaults, real scenarios — Ward produces its verdict and its full compliance record in parallel, while settling nothing. For a quarter, the institution simply compares: what Ward determined against what their committee eventually decided.

Every time, the outcomes match — except Ward reached its in seconds, with a replayable record, and without a meeting. By the time they move Ward to live settlement, they aren’t trusting a promise. They’re automating a process they’ve already watched get it right, over and over, with their own eyes. Trust earned by observation, not assertion. The skeptic’s on-ramp — and the one most institutions will want to take first.

06

The Exceptional Event

A claim arrives. On its face it looks valid — a default was declared, a counterparty wants resolution, money is waiting to move. In a discretionary system, this is where pressure builds: someone wants a decision, and a human under pressure tends to find a way to say yes.

Ward runs its checks against live ledger state — and the facts don’t line up. The loan’s default flag was never set on-chain. Or the claimant doesn’t hold the credential the domain requires. Or the coverage math doesn’t clear. The conditions for a deterministic outcome simply aren’t met.

So Ward does nothing. It declines. No payout is constructed, no settlement is proposed — and the rejection is recorded, on-chain and replayable, with the exact reason. Not a judgment call, not a delay for review: a refusal that follows directly from the facts.

This is the case that proves the rest. A system that only ever approves can’t be trusted to protect you. Ward’s willingness to resolve nothing when the facts don’t support resolution is what makes its “yes” mean something. The restraint is the credibility.

Ready to build?

The default path should be as engineered as the lending product.

Ward Protocol is not a button, a bot, or a back-office workaround. It is the resolution layer institutions can build around — before capital scales.