Web3 / Blockchain (ICP, XRPL)
XRP YieldVault — Non-Custodial XRPL Escrow Protocol
- XRPL Protocol
- Next.js
- Web3Auth
- Smart Escrows
- Tailwind CSS
Before
Crypto investors lacked transparent, automated yield strategies and decentralized DAO voting on the XRP Ledger.
After
Engineered an investor-focused dApp platform featuring 18-year locked on-chain escrows, yield analytics, and dual Web2/Web3 auth.
Problem statement
Crypto investors lacked transparent, automated yield strategies and decentralized DAO voting on the XRP Ledger.
Solution built
Engineered an investor-focused dApp platform featuring 18-year locked on-chain escrows, yield analytics, and dual Web2/Web3 auth.
Tech architecture
- Ledger
- Native XRPL escrows hold the locked position. The app does not take custody of the XRP.
- App
- Next.js and Tailwind for vaults, governance, analytics, and the platform guide.
- Auth
- Web3Auth for Google or email, and an XRP wallet connect path for the non-custodial route.
Results
-
On-chain escrow
18-year locked positions on XRPL
-
Two entry paths
Google sign-in or an XRP wallet
-
DAO voting
Governance beside the yield analytics
Screenshots
Vault home
Yield headline, Launch Vault App, and the entry-path panel.
Web2 / Web3
Google or email, and XRP wallet connect.
Governance
DAO voting next to vault analytics.
If this is the kind of system you need
Book a call and bring the workflow as it works today. We will say what should be built, and what should be left alone.