XRPL hackathon starter stack (2026)

Documentation-based guide: code examples are from the makers' docs and weren't run by us. Compiled from each maker's own docs on Oct 23, 2026.

Before an XRP Ledger hackathon starts, set up five things: a funded Testnet account from the XRPL faucet, an SDK in a language your team already knows (xrpl.js or xrpl-py for most teams), a Testnet RPC endpoint, a wallet path for your users, and an explorer to check transactions. All of it is free on Testnet, so you can have a transaction confirmed before the opening talk ends.

This guide is for teams heading to the AI & Fintech XRPL Hackathon in New York (Oct 24-25) and IXH26 in Bari in November, and for any XRPL weekend build. It only covers tools whose own docs name the XRP Ledger. For the full list, see our XRP Ledger developer tools page. It is a summary of what each maker says, not a ranking.

Contents

• Quick answer
• Which XRPL network should you build on?
• Which SDK should you use?
• Which RPC endpoint should you use?
• How will users sign transactions?
• Explorer and data APIs
• Building an AI agent on XRPL
• How to choose: a pre-hackathon checklist

Quick answer

Which XRPL network should you build on?

Build on Testnet unless your track says otherwise. XRPL's faucet page describes Testnet as a "Mainnet-like network for testing applications" and Devnet as a preview of upcoming amendments. It also lists two preview networks: Lending-Devnet (XLS-66d Lending Protocol) and WASM Devnet (XLS-100d Smart Escrows) Source: XRP Faucets.

That matters in New York. The event's Lending & Borrowing track asks teams to build on the XRP Ledger Lending Protocol and Single Asset Vaults "before it goes live" Source: AI & Fintech XRPL Hackathon. If you pick that track, fund an account on Lending-Devnet from the faucet page, not on Testnet. Its JSON-RPC endpoint is https://lend.devnet.rippletest.net:51234/ Source: XRP Faucets.

Two gotchas from the same page: test network history and balances "are reset as necessary", and Devnets "may be reset without warning". Don't hard-code account addresses into your demo the night before. And don't use Testnet credentials on Mainnet Source: XRP Faucets.

Which SDK should you use?

Use the language your team already writes. The New York event says so directly: "no need to learn a new coding language", and names JavaScript and Python Source: AI & Fintech XRPL Hackathon.

• xrpl.js (JavaScript/TypeScript): install it with npm install xrpl. The tutorial asks for Node.js 20 or later, and its example funds a new Testnet wallet in one call with client.fundWallet() Source: xrpl.org JavaScript get started. Best for web front ends, since it also runs in browsers.
• xrpl-py (Python): install it with pip install xrpl-py. The tutorial asks for Python 3.7 or later, and generate_faucet_wallet creates and funds a Testnet account Source: xrpl.org Python get started. Good for back ends, scripts and AI agent code.
• xrpl4j (Java), xrpl-go (Go) and XRPL_PHP (PHP) each have their own get-started tutorial on xrpl.org. Compare them on our XRPL smart contract and SDK page.

The faucet helpers save you a trip to the website and make it easy to give every teammate their own funded account.

Which RPC endpoint should you use?

For a weekend build, the free public servers are enough. XRPL's public servers page lists Testnet servers run by Ripple (wss://s.altnet.rippletest.net:51233/), Honeycluster and XRPL Labs. It notes the XRPL Labs server supports CORS, which matters if you call it straight from a browser Source: Public servers.

If you want a private endpoint with a dashboard, two listed providers name XRPL Testnet in their docs:

• QuickNode lists XRPL Mainnet and Testnet, both with WSS and archive data Source: QuickNode XRPL docs. Its free trial lasts one month with 10M API credits and no card Source: QuickNode pricing. QuickNode is also a partner of the New York event Source: AI & Fintech XRPL Hackathon.
• Chainstack lists the XRP Ledger with a Testnet Source: Chainstack networks. Its free Developer plan includes 3M requests a month at 25 requests per second, with WebSockets Source: Chainstack pricing. Its docs also warn that XRPL doesn't implement the eth_* interface, so ethers.js, web3.py and Hardhat don't apply Source: Chainstack XRPL tooling.

We compare these two side by side at QuickNode vs Chainstack. For networks, free tiers and history depth across all providers, read Best RPC and node providers for the XRP Ledger.

How will users sign transactions?

Decide this before you write UI code. It shapes your whole demo flow.

• Xaman Developer Platform: your app creates a sign request and the user signs it in the Xaman wallet. The docs recommend the JavaScript/TypeScript SDK (npm package xumm) and list community SDKs for Python and other back-end languages Source: Xaman getting started. The catch for a hackathon: the user picks the network in the app, not you. Xaman's docs warn about "getting paid on Testnet" while expecting Mainnet, and say to check the network in the signed result or force one in the payload Source: Xaman networks. Sign requests average about 30 per minute, and Xaman asks you to subscribe to status updates rather than poll Source: Xaman rate limits.
• MetaMask Embedded Wallets (formerly Web3Auth): users sign in with a social or email login and get an XRPL wallet. Its XRPL guide uses the @web3auth/xrpl-provider package and gives Mainnet, Testnet and Devnet configs. It also warns against using its public RPC target in production Source: MetaMask XRPL guide. Good for fintech demos where judges shouldn't need a wallet app.

Both are on our XRPL wallets page.

Explorer and data APIs

• Testnet explorer: the xrpl.js tutorial links new accounts to testnet.xrpl.org, so keep it open in a tab during your demo Source: xrpl.org JavaScript get started.
• Bithomp API: REST data for accounts, NFTs, tokens and transactions. It is free on the test networks. On Mainnet, the free tier is for non-commercial use at 10 requests a minute and 2,000 a day, and paid plans start at 30 EUR a month Source: Bithomp API docs.
• DIA Price Oracles: for fintech apps that need prices. DIA's XRPL guide lists a Mainnet and a Testnet oracle that you read with the ledger_entry API Source: DIA XRPL guide.

More options are on our XRPL data and oracles page.

Building an AI agent on XRPL

The New York event has an Agentic Finance track for AI agents that make payments on the XRP Ledger, and it welcomes AI coding tools and agent frameworks Source: AI & Fintech XRPL Hackathon.

mcp-xrpl is a Model Context Protocol server that lets an agent work with XRPL MainNet, TestNet and DevNet. Its README defaults the network to testnet, needs Node.js 18 or later, and can take a wallet seed from a .env file Source: mcp-xrpl README. It is a small community project, so use a throwaway Testnet seed and read the code before you point it at anything real. Or write a thin wrapper around xrpl.js or xrpl-py yourself, so you control which transactions the agent can sign.

How to choose: a pre-hackathon checklist

1. Pick your track's network first. Testnet for most tracks; Lending-Devnet for lending and vault work. Bookmark its faucet.
2. Fund one account per teammate with fundWallet() or generate_faucet_wallet, and keep the seeds out of your repo.
3. Install the SDK and send one test payment at home, so setup problems don't eat hour one.
4. Choose an RPC: public Testnet servers to start (XRPL Labs for browser CORS), a QuickNode or Chainstack free endpoint if you want your own.
5. Decide how users sign: Xaman for wallet users (check the network in every result), embedded wallets for social login.
6. Keep an explorer tab open and plan where your demo data comes from: Bithomp for indexed history, DIA for prices.
7. Plan for resets: Devnets can reset without warning, so script your demo setup and don't rely on yesterday's accounts.

Tools, plans and prices change often. Confirm on each maker's page before you rely on them.