The institutional fintech stack has a fragmentation problem. A fund trying to settle RWA transactions across XRPL and Stellar while maintaining a compliant KYC layer, generating audit trails, and routing through Fireblocks MPC custody needs to integrate at least six separate vendors, write the glue code between them, and hope the compliance runtime speaks to all of them.
UnyKorn is the answer to that problem. Not a wrapper. Not a middleware. A native Rust workspace that treats settlement, compliance, identity, governance, and capital routing as first-class citizens of a single coherent architecture.
The Five Layers
The architecture is a clean 5-layer stack, each layer building on the one below with no circular dependencies and full auditability at every seam.
Layer 1 · Core Infrastructure
Cryptography and Node Runtime
Ed25519 signatures, SHA-256 and BLAKE3 hashing, deterministic key derivation, the node runtime itself. Everything above this layer inherits the same cryptographic primitives. No vendor-specific crypto. No fallback to OpenSSL surprises.
Layer 2 · Consensus and State
Proof-of-Stake, Validators, Mempool
A 6-class validator system with weighted PoS consensus, a fee-priority mempool, and a 2-of-3 policy quorum for governance actions. State transitions are deterministic. The same transaction produces the same state on every node.
Layer 3 · Domain Modules
13 Production Modules
Treasury management, DID identity, KYC/AML, governance, RWA tokenization, carbon credits, energy markets, IP registry, notary, TLD registry, ERC-6551 vaults, credit ledger. Each module is a discrete crate. None of them talk to the settlement rail directly — they go through Layer 4.
Layer 4 · Funding and Finance
Multi-Rail Settlement
XRPL bridge (escrow, DEX, XLS-38d sidechain, witness attestation), Fireblocks MPC vault, BitGo 2-of-3 multisig, Circle USDC/EURC with CCTP cross-chain transfer, Stripe fiat on-ramp, and Stellar SEP-24 anchor integration. Provider abstraction guarantees custody isolation — the domain modules never touch custody keys directly.
Layer 5 · Application
JSON-RPC API, MCP AI, RAG, Metrics
The surface layer: JSON-RPC 2.0 API, an MCP agentic AI system that can issue, query, and route transactions through natural language, a RAG system for document search over compliance records, Prometheus metrics, and an affiliate system. This is where broker-dealer integrations, bank APIs, and AI agents plug in.
What Makes It Different from a Multi-Vendor Stack
Every organization building on institutional blockchain infrastructure eventually runs into the same four problems:
| Problem | Multi-Vendor Approach | UnyKorn Approach |
|---|---|---|
| Compliance runtime | Third-party KYC/AML bolted onto existing APIs, often asynchronous, sometimes non-deterministic | Native KYC/AML module in Layer 3 — every transaction passes through a compliance gate before reaching the funding rail |
| Audit trail | Separate logging systems per vendor; aggregation is manual | SHA-256 hash chaining across all state transitions; full audit log is native output, not an afterthought |
| Settlement atomicity | Cross-vendor atomic settlement requires custom orchestration; race conditions are real | Settlement atomicity is a first-class guarantee — the funding engine either settles or rolls back, with deterministc routing and full audit logging |
| Identity | Separate identity provider, often OAuth-based, not cryptographically linked to transactions | DID identity module issues cryptographic identities that are attached to every transaction as provable metadata |
The Multi-Rail Settlement Guarantee
The funding engine in Layer 4 operates on four explicit guarantees that are enforced at the code level, not at the SLA level:
Provider abstraction — the domain modules never touch a specific settlement rail directly. They call the funding engine, which routes to the appropriate provider based on instrument type, jurisdiction, and availability.
Custody isolation — MPC keys (Fireblocks), multisig keys (BitGo), and XRPL wallet keys are stored in isolated custody systems. The application layer cannot access keys directly. All signing happens inside the custody module, which returns only signed transaction bytes.
Settlement atomicity — cross-rail settlements (e.g., USDC receipt on Circle triggering XRPL IOU issuance) are coordinated through a two-phase commit pattern. Partial settlements are detected and rolled back automatically.
Full audit logging — every state transition, every routing decision, every compliance check produces a timestamped, SHA-256 anchored event. The audit log is a first-class output of the system, not a separate reporting pipeline.
The Domain Modules That Matter for Banks and Broker-Dealers
The modules that will matter most to institutional clients are the ones that turn regulatory requirements into automated enforcement rather than manual processes.
The KYC/AML module runs at Layer 3 and enforces compliance before any transaction reaches the funding rail. The RWA tokenization module handles the full lifecycle: asset registration, token issuance, transfer restrictions, and investor verification. The credit ledger tracks loan facilities, draws, and repayments against structured credit agreements. The vaults module implements ERC-6551 token-bound accounts — a standard that lets individual tokens hold assets, enabling per-position custody at the token level.
For trade finance specifically, the Layer 4 funding module includes UCP 600 trade finance support. That means the system can issue, manage, and settle Letters of Credit under the internationally recognized UCP 600 ruleset — a requirement for any institution doing cross-border trade finance.
The AI and x402 Layer
The Layer 5 application includes an MCP agentic system — a structured API for AI agents to issue transactions, query settlement state, check compliance status, and route capital. This is the x402 pattern applied to capital markets: AI agents that can participate in institutional financial workflows without requiring human intermediaries for every step.
The implication is significant. A compliance-checked AI agent can initiate an XRPL escrow, request a KYC check from the identity module, receive a DID-verified attestation, and route a Circle USDC payment — all through the MCP interface, with full audit logging, without a human approving each step.
This is not a prototype capability. It is live in v0.5.0, built 2026-02-26, with 166 tests passing and zero unsafe Rust blocks in the entire codebase.
Who This Infrastructure Is For
| Client Type | Use Case | Key Modules |
|---|---|---|
| Broker-dealers | RWA issuance, investor onboarding, settlement reporting | KYC/AML, RWA tokenization, XRPL bridge, audit log |
| Banks | Trade finance (LC/SBLC), correspondent banking, cross-border corridors | Trade Finance (UCP 600), Stellar SEP-24, Fireblocks MPC, credit ledger |
| Family offices / funds | Tokenized asset portfolios, custody, DvP settlement | RWA tokenization, ERC-6551 vaults, BitGo multisig, DID identity |
| Commodity traders | On-chain trade finance, cargo-backed financing, settlement proof | Trade Finance (UCP 600), notary, XRPL escrow, audit log |
| Fintech builders | Compliance-first product development on live rails | Full stack — JSON-RPC API, MCP AI layer, all modules |
The Build Behind This System
UnyKorn is a live product built by FTH Trading out of Norcross, Georgia. The GitHub repository (FTHTrading/UnyKorn-L-1) is a 22-crate Rust workspace at v0.5.0. The 166 tests include unit tests per module, integration tests across the funding engine, and end-to-end settlement tests against XRPL mainnet and Stellar testnet. Zero unsafe blocks means the memory safety guarantees of Rust are preserved across the entire codebase — no escape hatches.
The clients running on this infrastructure include OPTKAS (structured capital markets platform) and SunFarm Solar DR, which uses the treasury layer for energy asset financing. Both are live on XRPL mainnet with verifiable transaction hashes.
Build on the infrastructure.
If you are a broker-dealer, bank, fintech builder, or fund that needs deterministic capital infrastructure — custom XRPL integrations, compliance runtime implementation, or a full platform build on UnyKorn rails — this is a direct conversation. Engagements start at $50,000 for institutional builds.