Infrastructure

Neutral Infrastructure Provider

Like Infura for Ethereum, LucenDEX provides neutral XRPL execution infrastructure. We don't compete as a DEX brand—we're the backbone for wallets, fintechs, and institutions.

Non‑Custodial

Zero Custody Risk

Backend never sees private keys or seed phrases. All transactions signed client‑side. We provide routing and optional relay—your keys stay with you.

Infrastructure Provider

Not a Broker/Dealer

We don't facilitate trades—we provide infrastructure. Partners integrate our APIs to access liquidity. Think AWS for XRPL trading, not Coinbase.

Deterministic

Cryptographic Binding

QuoteHash = blake2b‑256(params + fees + TTL). Embedded in XRPL memo. Execution must match quote or fail. No discretionary control.

System Components

Infrastructure Stack

🗂️ Indexer

Real‑time XRPL ledger indexing for AMM pools and orderbook state. DEX‑only data—no payments, no user balances, no PII.

Technical Details →
🧮 Router

Deterministic pathfinding across AMM + orderbook liquidity. Computes best route with fee injection and QuoteHash binding. Read‑only access to indexer data.

🔌 API Layer

Public endpoints (quotes, pairs, health) + partner endpoints (Ed25519 authenticated). Per‑partner quotas enforced via in‑memory KV. Usage metering to Database.

🔄 Relay (Optional)

Forwards signed transaction blobs to rippled. No transaction modification. Signature validation only. Disabled by default—clients can submit directly to XRPL.

✅ Validator

Independent XRPL validator operated by LucenDEX. Domain‑verified via xrp‑ledger.toml. Provides network security and infrastructure transparency.

View on XRPScan →
Node Infrastructure

XRPL Node Topology

API Node

Low‑latency read operations for router. Public WebSocket for real‑time ledger stream.

Full‑History Node

Complete ledger history for indexer. Backfill support for gap detection.

Validator

Independent validation. Domain verification at lucendex.com/.well-known/xrp-ledger.toml

Security Model

Zero‑Trust Architecture

No implicit network trust. Every service boundary secured with mTLS. No symmetric keys—Ed25519 for partner authentication.

  • ✓ mTLS Between Services
    All inter‑service communication encrypted with mutual TLS
  • ✓ Ed25519 Request Signing
    Partner API authenticated via public key cryptography
  • ✓ Least‑Privilege Database Access
    Separate roles: indexer_rw, router_ro, api_ro
  • ✓ No Discretionary Control
    QuoteHash binding enforces deterministic execution
Philosophy

Why Neutral Infrastructure?

LucenDEX doesn't compete with DEX frontends. We're infrastructure for partners to build on. You keep your brand, your users, your relationship. We provide the execution rails.