Build

Build a Ward-conformant product without giving up the signer boundary.

Ward provides the SDK surface, API path, and chain adapters needed to ship deterministic default resolution without giving Ward custody or signing authority.

Open Demo Review Protocol Discuss a Pilot

Protocol specification

Five modules. Nine checks. One conformance result.

The Ward conformance engine is deterministic and auditable. Every integration runs the same nine on-ledger checks through the same five modules, returning a machine-readable receipt institutions can inspect.

Read the full protocol specification →

Module 1

WardClient

High-level SDK entrypoint for institutions and integrators.

Module 2

VaultMonitor

WebSocket default detection with authoritative ledger re-verification.

Module 3

ClaimValidator

Nine-step deterministic on-chain claim validation.

Module 4

EscrowSettlement

Unsigned escrow lifecycle for controlled institutional execution.

Module 5

PoolHealthMonitor

Coverage ratio and reserve accounting for pool safety.

Nine on-ledger checks

Check 01

NFT existence and taxon enforcement (WARD_POLICY_TAXON = 281)

Check 02

Policy validity using XRPL ledger close_time, never server clock

Check 03

Vault address binding: metadata vault must equal defaulted_vault

Check 04

LSF_LOAN_DEFAULT flag on LedgerEntry(index=loan_id)

Check 05

Vault loss must be greater than zero drops

Check 06

Pool usable balance must exceed the validated loss amount

Check 07

Replay protection: policy NFT must still be live

Check 08

Claimant must still hold the policy NFT on ledger

Check 09

Pool solvency and rate limits must still hold at settlement

Key constants

WARD_POLICY_TAXON	281
MIN_COVERAGE_RATIO	1.5
CLAIM_RATE_LIMIT_MAX	3
LSF_LOAN_DEFAULT	0x00010000
MONITOR_HEARTBEAT_TIMEOUT_S	60
XRPL_BASE_RESERVE_DROPS	2_000_000

ward_signed = False — always.

Ward returns unsigned payloads only. The institution signs. The chain settles.

Integration architecture

XLS-66, XLS-65, XLS-30, and XLS-20 on the XRP Ledger.

Ward integrates with XLS-66 Lending, XLS-65 Vault, XLS-30 AMM, and XLS-20 NFT on the XRP Ledger. The following shows the settlement pipeline and key calculations.

Settlement timeline

Time	Event
T + 0	Default confirmed on ledger
T + 5 min	Ward monitor detects lsfLoanDefault
T + 10 min	Escrow created — 48 hr dispute lock
T + 48 hr	Dispute window expires
T + 48 hr 5 min	Escrow finishes — claim paid

Monitoring points

Object	Field
Loan	lsfLoanDefault
LoanBroker	DebtTotal
Vault	AssetsTotal
Vault	LossUnrealized

Key calculations

# Drops are the native XRPL integer unit (1 XRP = 1,000,000 drops)

DefaultAmount   = Loan.PrincipalAmount - Loan.PaidAmount
DefaultCovered  = min(DefaultAmount, Policy.CoverageDrops)
VaultLoss       = Vault.LossUnrealized           # set by XLS-65 on default
ClaimPayout     = min(DefaultCovered, VaultLoss)
CoverageRatio   = Vault.AssetsTotal / LoanBroker.DebtTotal  # must be >= 1.5

Integration surface

Start with the SDK. Finish with a conformance receipt.

Python SDK

pip install ward-protocol==0.2.10

View on PyPI →

Validator services, vault monitors, conformance jobs, and institutional backend flows.

TypeScript SDK

npm install @wardprotocol/sdk

View on npm →

Product consoles, dashboards, rail orchestration, and receipt export.

Hosted API

GET https://api.wardprotocol.org/health

Live API status endpoint for pilot integrations, operational checks, and enterprise onboarding.

Chain adapter catalog

Chain-native rails. One conformance result.

Each rail maps the local chain primitive into Ward's conformance engine. Your product keeps its settlement rail. Ward standardizes the resolution path and the institutional review surface.

Live