Workshop readiness and secure Testnet setup
Complete the prerequisites, verify the Academy coding environment, and establish the safety and validation habits used in every lab.
What you'll learn
- Connect the Academy runner to XRPL Testnet.
- Create a disposable funded Testnet account without exposing its seed.
- Distinguish submission from validated success.
- Use the backup endpoint and Explorer when diagnosing a problem.
Before the live workshop
This course starts where the introductory developer training ends. Before the live session, watch the previous training recordings and complete Code with the XRPL & JavaScript. You should already be comfortable connecting a client, funding a Testnet account, creating a trust line, signing locally, and using submitAndWait. If any of that is unfamiliar, the next module (Introduction to the XRP Ledger) recaps it in plain language.
Every action follows the same five steps
Every live exercise runs the same sequence: build, autofill, sign, submit, validate, then read the result. Watch the difference between submit and done. When a server accepts your transaction, that is a promise, not a settlement. It settles once it lands in a validated ledger. So record the transaction hash at submit time, wait for validation, then read meta.TransactionResult (tesSUCCESS, for example) and the fields it changed.
Safety boundary
Use only wallets from client.fundWallet() on Testnet. A Mainnet seed should never go into the Academy editor, a chat, an issue, or a message to a mentor. The starter exercises build wallets in memory and print addresses, never seeds. Mentors work from your code, public addresses, transaction hashes, result codes, and metadata, so they never need your wallet.
Environment check
Run the exercise below. A good result gives you a funded public address and validated ledger index. Open the address in the Testnet Explorer. If the primary endpoint is unavailable, the supplied connection helper tries the backup endpoint automatically.
Resources
Assignments
0 of 2 complete