digestVidSign in
summary

Ripple - Programmability on the XRPL | Mayukha Vadari, Ripple

Thumbnail of the video “Ripple - Programmability on the XRPL | Mayukha Vadari, Ripple”
Community upload. AI output has not been independently verified.
Author: Ripple
Categories: Business
Tags: business
Views: 1 · Last viewed: 2026-10-13 22:52 UTC

Short Summary

Main recommendation: Use the XRP Ledger's upcoming Permissioned DEX, built on credentials and Permissioned Domains, so companies can access regulated liquidity while meeting compliance requirements. The speaker argues that the XRPL's native, pre-built features, rather than custom smart contracts, make bringing this kind of programmability on-chain practical.

Key Points

  • The Permissioned DEX is a new XRP Ledger feature that lets projects access regulated liquidity, in contrast to today's fully decentralized and permissionless DEXes, which are difficult for companies to use given compliance obligations.
  • Credentials are on-chain attestations or permissions, with KYC (know-your-customer) status by jurisdiction given as an example.
  • A Permissioned Domain is a collection of credentials that satisfies a specific regulatory need, such as accepting several different KYC providers.
  • Only members of a domain, meaning accounts holding one of the qualifying credentials, can trade in the corresponding restricted section of the DEX.
  • The XRPL has many features built natively into the ledger, which the speaker describes as powerful, efficient, and well tested, whereas the EVM and most other chains rely on smart contracts for comparable functions.

Details Worth Noting

  • Concrete instructions: The transcript gives no step-by-step setup, dosage, or procedure. The only actionable guidance is conceptual: to implement compliant trading on the XRPL, first define credentials (for example, KYC status tied to jurisdiction), then group the qualifying credentials into a Permissioned Domain, and then trade within the permissioned section of the DEX. The speaker also advises that developers generally do not need to write a smart contract for features already native to the XRPL, using multi-signature setup as the example, which on the XRPL is a native feature but requires a smart contract on Ethereum.
  • The speaker frames the Permissioned DEX as building on two earlier layers: credentials first, then Permissioned Domains, with the DEX as the top layer.
  • The stated goal is to let projects and companies transact more freely and easily while still satisfying compliance and regulatory needs.
  • The speaker, Mayukha Vadari, is identified as a senior software engineer at Ripple leading the programmability initiative for native XRPL programmability.
  • The transcript is a partial excerpt; it does not cover timelines, launch dates, or specific KYC providers.

Bottom Line

The XRP Ledger's Permissioned DEX, layered on credentials and Permissioned Domains, is presented as a way to make regulated trading possible on-chain, and the transcript's main argument is that native XRPL features reduce the need for custom smart contracts.