# XRPL Fit Assessment Collected: 2026-06-09 Purpose: map Ripple/XRPL needs against Moonsong Labs projects, skills, and people so the team can prepare a targeted Ripple response and later showcase the relevant proof points in the website. ## Executive Readout Ripple is evaluating MSL against an XRPL modernization agenda, not a narrow staff augmentation request. The strongest fit is a compact protocol/tooling engagement around programmable XRPL features, especially Smart Escrows, Smart Contracts/WASM, Confidential MPTs, developer tooling, conformance testing, and AI-assisted developer workflows. The highest-confidence MSL story is: - MSL has shipped production blockchain protocol/runtime work: Moonbeam, Tanssi, DataHaven, StorageHub, Madara/SNOS. - MSL has deep developer tooling and simulation experience: Foundry-zksync, anvil-zksync, ZKstack tooling, transaction simulation, Substrate MCP. - MSL has relevant safety and upgrade tooling: ZKsync GovAuth, Upgrade Verification Tool, Moonbeam runtime/release work, Tanssi/DataHaven validation workflows. - MSL has credible privacy, identity, and permissioning experience: Prividium, ZKsync SSO/OIDC recovery, Guardian Recovery, off-chain privacy work. - MSL has payment/vault/settlement experience that maps to escrow, batch, lending, and institutional tokenization: Solana Subscriptions/Multi-Delegate, Perena Metavaults, Tradable, UBS gold, Canton/vault work. - MSL has cross-chain and EVM-adjacent experience: Moonbeam, Tanssi Snowbridge, DataHaven Snowbridge, Glacis, XCM, EVM compatibility. The main caveat: do not imply prior direct `rippled` ownership unless confirmed. Position most evidence as adjacent production-chain, tooling, privacy, and financial primitive experience that can transfer into XRPL protocol work. ## Ripple Need Signals ### Internal Signals From `xrpl-project.md` and Ripple Notion pages: - Ripple requested formal diligence around people, repos, operated infrastructure, tokens, governance/admin keys, IP, and related matters. - The RippleX opportunity is marked strategic, proposal delivered, six-month term, 1 TPM and 4 engineers, with known monthly value of $147,500. - Conversation notes identify smart features, programmability, ZK, AI, and broader roadmap discovery. - The proposal draft centers on Smart Escrows, Smart Contracts/WASM, Confidential MPT integration, AI agent payment infrastructure, and AI-enabled developer workflows. - The earlier Ripple response already called out cross-feature composability, WASM VM determinism, host function policy/versioning, event semantics, indexing, conformance suites, stress harnesses, and fuzzing. ### Public XRPL Feature Surface Current public XRPL/XLS sources support the same need areas: - Smart Escrows are a draft amendment using WebAssembly conditions for escrow release/cancel logic, with a deliberately limited execution model and mandatory safety constraints. Source: https://xls.xrpl.org/xls/XLS-0100-smart-escrows.html - XRPL Smart Contracts are a draft/proposal direction for native L1 contracts using pseudo-accounts, contract source/data objects, contract calls, events, and explicit fee/resource governance. Source: https://xls.xrpl.org/xls/XLS-0101-smart-contracts.html - XLS-0102 WASM VM is listed as a draft amendment in the XLS index. Source: https://xls.xrpl.org/ - MPTs are the institutional token primitive: transferability controls, supply caps, transfer fees, freeze/clawback controls, issuer/holder separation, and token escrow flags. Source: https://xrpl.org/docs/concepts/tokens/fungible-tokens/multi-purpose-tokens - Confidential MPTs are an active XLS direction around confidential balances, selective disclosure, auditors, and ZK proof requirements. Source: https://xls.xrpl.org/xls/XLS-0096-confidential-mpt.html - Credentials and Permissioned Domains provide compliance-gated access patterns. Permissioned Domains are expected to back features such as permissioned DEXes, Single Asset Vaults, and Lending Protocols. Sources: https://xrpl.org/docs/concepts/decentralized-storage/credentials and https://xrpl.org/docs/concepts/tokens/decentralized-exchange/permissioned-domains - Single Asset Vaults and the Lending Protocol map directly to institutional vault/credit use cases. Sources: https://xrpl.org/docs/concepts/tokens/single-asset-vaults and https://xrpl.org/docs/tutorials/how-tos/set-up-lending/use-the-lending-protocol - Batch Transactions package up to eight transactions with explicit modes such as all-or-nothing and only-one, creating direct needs around transaction semantics, signature safety, metadata interpretation, wallets, explorers, and client libraries. Source: https://xrpl.org/docs/concepts/transactions/batch-transactions - The 2026 Batch amendment vulnerability disclosure is strong evidence that release validation, conformance, signature-safety review, and fuzzing are not optional. Source: https://xrpl.org/blog/2026/vulnerabilitydisclosurereport-bug-feb2026 - XRPL sidechains and bridges are part of the interoperability surface; the XRPL EVM Sidechain is documented as a standalone Cosmos-SDK-based EVM chain with XRP gas and Axelar bridge options. Sources: https://xrpl.org/docs/concepts/xrpl-sidechains/cross-chain-bridges and https://docs.xrplevm.org/ ## Workstream Fit Map | XRPL workstream | What Ripple likely needs | MSL fit | Proof projects | Candidate leads / people | Caveat | |---|---|---|---|---|---| | Smart Escrows, Smart Contracts, WASM | Deterministic execution, host functions, resource accounting, event semantics, integration with ledger objects. | Strong adjacent. | Moonbeam, Foundry-zksync, anvil-zksync, ZKstack tooling, Madara/SNOS, DataHaven. | Alan, Nish, Juan, Federico, Steve, Facundo, Elois, Artur. | Needs XRPL-specific discovery before claiming implementation velocity. | | WASM conformance and protocol safety | Cross-architecture determinism, gas/host-function invariants, fuzzing, serialization boundaries, release validation. | Very strong. | ZKsync Upgrade Verification, GovAuth, Moonbeam runtime/release work, Tanssi E2E, DataHaven, Fabric/security workflows. | Tim, Juan, Gabriel, Alan, Steve, Elois, Artur, Ahmad. | Fabric/security evidence needs shareability review. | | Cross-feature composability | Interaction matrix for Smart Escrows, Smart Contracts, Confidential MPTs, events, token rules, and rollback semantics. | Strong. | ZKsync governance/upgrade flows, transaction simulation, Perena atomic composition, Solana subscriptions, Prividium permissioning. | Alan, Nish, Tomi, Juan, Miguel, Eze, Tobias, Michael. | Exact transaction simulation ownership needs validation. | | Confidential MPTs and privacy | Confidential balances, ZK proofs, selective disclosure, auditor/regulator visibility, privacy-preserving escrow lifecycle. | Strong specialist. | Prividium, ZKsync SSO/OIDC recovery, Guardian Recovery, Offchain Privacy, ZKsync governance/security. | Miguel, Gabriel, Tim, Juan, Agustin Aon, Agustin Rodriguez, Meidhy. | Offchain Privacy is currently internal/private evidence. | | MPTs and institutional tokenization | Token lifecycle, controlled transferability, freezes/clawbacks, metadata, vault shares, treasury/stablecoin/RWA workflows. | Strong adjacent/specialist. | Perena Metavaults, Tradable, UBS Gold, Solana Multi-Delegate, Canton/vault work, Prividium. | Eze, Facundo, Meidhy, Tim, Miguel, Tomi, Mattias. | Tradable/UBS public attribution to MSL is weak; use carefully. | | Credentials, Permissioned Domains, permissioned markets | Identity/credential checks, issuer/subject controls, permissioned access to DEX/vault/lending flows. | Strong specialist. | Prividium, OIDC Recovery, Guardian Recovery, Offchain Privacy, Canton/Daml workflows. | Miguel, Tim, Juan, Agustin Aon, Agustin Rodriguez, Gabriel. | Need to avoid overstating direct XRPL Credentials work. | | Lending, vaults, institutional credit | Private vaults, deposits/redemptions, share accounting, risk controls, collateral/first-loss concepts. | Relevant adjacent. | Perena Metavaults, Tradable, Canton vaults, Solana Multi-Delegate, UBS Gold. | Eze, Meidhy, Facundo, Tim, Mattias. | Direct XRPL lending protocol evidence is thin. | | Batch, escrow, atomic settlement | Batch semantics, all-or-nothing workflows, multi-party signatures, conditional payments, wallet/indexer interpretation. | Strong adjacent. | Solana Subscriptions/Multi-Delegate, Perena, Payment Channels/MPP, transaction simulation, GovAuth. | Nish, Eze, Tobias, Michael, Juan, Tomi, Meidhy. | Batch requires careful XRPL semantics review because recent vulnerability history is material. | | Developer tooling, local testing, SDKs | Local nodes, test harnesses, RPC compatibility, examples, CLI tools, docs navigation, protocol interaction tooling. | One of MSL's strongest areas. | Foundry-zksync, anvil-zksync, ZKstack CLI, Substrate MCP, Solana subscriptions SDK/Codama clients. | Nish, Juan, Federico, Parth, Gabriel, Alan, Tomi. | Substrate MCP has thin public narrative evidence. | | XRPL EVM, bridges, interoperability | EVM sidechain integration, Axelar/cross-chain bridge patterns, wrapped assets, relayers, XChainBridge-style review. | Strong. | Moonbeam, Tanssi Snowbridge, DataHaven Snowbridge, Moonbeam XCM, Glacis, Substrate-Cosmos bridge work. | Parth, Agustin Rodriguez, Tobias, Ahmad, Mattias, Elois, Gonzalo, Rodrigo. | Map to XRPL EVM/Cosmos/Axelar specifics before staffing. | | AI-enabled developer/security workflows | AI-assisted docs, code navigation, spec Q&A, protocol debugging, security triage, agent payment infrastructure. | Strong cross-cutting, but should be secondary unless Ripple prioritizes it. | Substrate MCP, Prompt Train, Agenter, Fabric, Taurus MCP, DataHaven, Theoriq. | Gabriel, Parth, Federico, Alan, Michael, Rodrigo, Manuel. | Some AI proof is internal and should not be headline evidence yet. | ## Recommended Pods ### Pod 1: Programmability and WASM Mission: support Smart Escrows, Smart Contracts, WASM VM integration, host function boundaries, event semantics, and execution constraints. Lead candidates: Alan, Nish, Steve, Facundo. Core support: Juan, Federico, Elois, Artur, Tim. Proof to use: Moonbeam, Foundry-zksync, anvil-zksync, Madara/SNOS, DataHaven. ### Pod 2: Protocol Safety and Conformance Mission: build the conformance suite, determinism checks, fuzzing/stress harnesses, serialization boundary tests, and release-validation workflow for amendments. Lead candidates: Tim, Juan, Gabriel, Alan. Core support: Steve, Elois, Artur, Ahmad, Federico. Proof to use: ZKsync Upgrade Verification, GovAuth, Moonbeam release/runtime work, Tanssi E2E, DataHaven validation workflows. ### Pod 3: Confidential MPT, Credentials, and Permissioning Mission: analyze and prototype confidential token/escrow interactions, selective disclosure, issuer/auditor flows, credential-gated features, and permissioned markets/vaults. Lead candidates: Miguel, Tim, Gabriel. Core support: Juan, Agustin Aon, Agustin Rodriguez, Meidhy, Tomi. Proof to use: Prividium, ZKsync SSO/OIDC Recovery, Guardian Recovery, Offchain Privacy, Canton/Daml workflows. ### Pod 4: Payments, Vaults, and Atomic Settlement Mission: evaluate escrow/batch/vault/lending flows, transaction lifecycle, subscriptions/recurring payment patterns, multi-party signing, and institutional asset workflows. Lead candidates: Eze, Nish, Meidhy. Core support: Tobias, Michael, Mattias, Facundo, Tomi. Proof to use: Solana Subscriptions/Multi-Delegate, Perena Metavaults, Solana Payment Channels/MPP, Tradable, UBS Gold, Canton vaults. ### Pod 5: Interoperability and XRPL EVM Mission: support sidechain/EVM interoperability analysis, bridge review, relayer patterns, cross-chain asset movement, replay/attestation safety, and developer ergonomics. Lead candidates: Parth, Agustin Rodriguez, Tobias. Core support: Ahmad, Mattias, Elois, Gonzalo, Rodrigo. Proof to use: Moonbeam, Tanssi Snowbridge, DataHaven Snowbridge, Moonbeam XCM, Glacis, Substrate-Cosmos bridge work. ### Pod 6: AI Developer Enablement Mission: build XRPL-specific AI docs/navigation tooling, agent-friendly CLI/RPC workflows, spec exploration, security triage workflows, and early agent payment prototypes. Lead candidates: Gabriel, Parth, Federico. Core support: Alan, Michael, Rodrigo, Manuel. Proof to use: Substrate MCP, Prompt Train, Agenter, Fabric, DataHaven, Theoriq. ## Best Ripple-Facing Proof Points Use these prominently: - Moonbeam: production EVM-compatible chain, runtime upgrades, XCM, governance, benchmarking, protocol operations. - Foundry-zksync and anvil-zksync: developer tooling, local testing, RPC compatibility, EraVM workflows, deployment/testing/debugging ergonomics. - ZKsync GovAuth and Upgrade Verification Tool: governance workflow, role-based upgrades, signature coordination, upgrade verification. - Prividium: permissioned/private infrastructure, RPC filtering, private explorer, enterprise access control. - ZKsync SSO/OIDC Recovery: ZK circuits, account recovery, guardian/OIDC proof systems, audit maturity. - Perena Metavaults: vault strategy architecture, atomic adapter composition, SDKs, instant withdrawals, risk controls. - Solana Subscriptions/Multi-Delegate: payment primitives, mainnet Solana program, Token-2022/SPL support, client generation. - Tanssi/DataHaven/StorageHub: Substrate appchain/storage/bridge engineering, relayers, SDKs, E2E workflows. Use with validation or careful framing: - Offchain Privacy: strong fit to Confidential MPT/permissioned flows, but keep internal unless approved. - Tradable and UBS Gold: strong RWA/tokenization relevance, but public Moonsong attribution is not established in current research. - Glacis: strong cross-chain relevance, but the specific Solana xERC20 PoC needs confirmation. - Taurus MCP, Fabric, Prompt Train/Agenter: strong AI workflow relevance, but proof/shareability varies. - Canton DevKit/vaults: potentially valuable for institutional tokenization/vaults, needs exact scope and evidence. ## Recommended Response Shape Use two linked documents: 1. Formal diligence response: org chart, census, contractor list, disputes, operated infrastructure, token/admin/key/governance disclosures, repo list, IP/grant/foundation/prior-employer claims. 2. Strategic XRPL fit brief: the workstream map above, proof-point bundles, suggested pods, key people, evidence appendix, and validation questions. The strategic brief should avoid raw compensation, performance history, attrition risk, internal rankings, or retention language. Those belong only in controlled diligence materials. ## Ripple-Facing Narrative Draft Moonsong Labs can support Ripple as a pre-formed blockchain engineering team with demonstrated experience in protocol/runtime engineering, developer tooling, protocol safety, privacy/permissioned infrastructure, cross-chain systems, and financial primitives. The most relevant engagement shape is a focused team that pairs implementation with design discovery: Smart Escrow and Smart Contract/WASM work, Confidential MPT composition, conformance and stress testing, developer tooling, and AI-assisted workflows for XRPL builders and protocol engineers. We should be precise that the team brings adjacent production-chain experience rather than claiming existing `rippled` ownership. The strength is that MSL has repeatedly shipped analogous systems under real constraints: deterministic runtimes, EVM-compatible chains, local execution tools, upgrade verification, private/permissioned infra, vaults/payments, and cross-chain messaging. ## Validation Checklist Before using this externally: - Confirm exact contribution depth by engineer for Transaction Simulation, GovAuth, Prividium, OIDC, Guardian Recovery, xERC20/Glacis, Canton, Offchain Privacy, Taurus MCP, Solana Multi-Delegate, and Perena. - Confirm which project details are public, NDA-covered, or client-approved. - Confirm current employee/contractor status for every named person. - Remove or downscope departed/historical contributors: Herman, Santi, Seva, Priyav, Karo, Andrea/noandrea, tgmichel, girazoki, pLabarta, peektism, lgalabru. - Ask Ripple/Ayo to prioritize among Smart Escrow init logic, Confidential MPT escrow composition, Smart Escrow/Smart Contract interaction rules, WASM VM conformance, AI developer tooling, and agent payment infrastructure. - Ask Ripple whether they prefer a first deliverable as design feedback, reference implementation, test/conformance harness, or developer tooling prototype. ## Source Notes Internal sources: - `xrpl-project.md` - Notion: Ripple Proposal DRAFT - Notion: Ripple - General Updates - Notion: Ripple - RippleX Dev Opportunity - Notion: Ripple Response - `data/research/showcase-cards.json` - `data/research/proof-gaps.json` - `data/research/skill-taxonomy.json` - `data/research/summary.md` Public XRPL sources checked: - https://xls.xrpl.org/ - https://xls.xrpl.org/xls/XLS-0100-smart-escrows.html - https://xls.xrpl.org/xls/XLS-0101-smart-contracts.html - https://xls.xrpl.org/xls/XLS-0096-confidential-mpt.html - https://xrpl.org/docs/concepts/tokens/fungible-tokens/multi-purpose-tokens - https://xrpl.org/docs/concepts/decentralized-storage/credentials - https://xrpl.org/docs/concepts/tokens/decentralized-exchange/permissioned-domains - https://xrpl.org/docs/concepts/tokens/single-asset-vaults - https://xrpl.org/docs/tutorials/how-tos/set-up-lending/use-the-lending-protocol - https://xrpl.org/docs/concepts/transactions/batch-transactions - https://xrpl.org/blog/2026/vulnerabilitydisclosurereport-bug-feb2026 - https://xrpl.org/docs/concepts/xrpl-sidechains/cross-chain-bridges - https://docs.xrplevm.org/