Lesson 4: Current Status - Xahau, Testnet, and the Path to Mainnet

XRPL mainnet—the production network where XRP has real value—supports:

XRPL MAINNET - LIVE FEATURES (November 2025)

NATIVE FEATURES (No Hooks Required):
├── Payments (XRP and IOUs)
├── Decentralized Exchange (order book)
├── Automated Market Maker (XLS-30)
├── Trust Lines and token issuance
├── Escrow (time and condition based)
├── Payment Channels
├── Multi-signing
├── Checks
├── NFTs (XLS-20)
├── Cross-Chain Bridges (XLS-38)
└── All transaction types in standard XRPL

NOT AVAILABLE:
├── Hooks
├── XLS-101 Smart Contracts
├── Any custom code execution
└── Extensions or programmability

STATUS:
Production ready, running since 2012
No smart contract capability

Hooks require an amendment—a protocol change that validators must approve:

XRPL AMENDMENT PROCESS

Step 1: PROPOSAL
├── Code developed and tested
├── Specification published
├── Security review completed
└── Implementation available

Step 2: VALIDATOR VOTING
├── Validators signal support
├── Requires 80%+ sustained support
├── For 2 weeks (2,016 consecutive ledgers)
└── Automatic activation if threshold met

Step 3: ACTIVATION
├── Amendment becomes enabled
├── All nodes must upgrade
├── Feature available network-wide
└── Cannot be easily reversed

HOOKS AMENDMENT STATUS:
├── Code: Available (tested on testnet)
├── Specification: Complete
├── Validator voting: NOT started on mainnet
├── Support level: Unknown
├── Timeline: UNCERTAIN

Why Uncertain:
├── Validators cautious about new features
├── Security concerns require extensive testing
├── Some prefer native features over programmability
├── No coordinated effort to force vote
└── Could be months, years, or never
```

MAINNET HOOKS TIMELINE (Honest Assessment)

OPTIMISTIC CASE (10% probability):
├── Validators coordinate in 2026
├── 80%+ support achieved
├── Hooks enabled by late 2026
└── Requires: Unusual validator alignment

BASE CASE (50% probability):
├── Gradual validator adoption
├── XLS-101 advances first
├── Hooks or XLS-101 by 2027-2028
└── Requires: Patient ecosystem growth

PESSIMISTIC CASE (40% probability):
├── Validators prefer native features
├── EVM Sidechain absorbs demand
├── Significant delay or never
└── Requires: Nothing (inaction)

BOTTOM LINE:
Don't build a business plan around
"Hooks on XRPL mainnet by [date]"
The date is genuinely unknown.
```

---

Xahau is a production blockchain that forked from the XRPL codebase with Hooks enabled:

XAHAU NETWORK FACTS

BASICS:
├── Origin: Fork of XRPL codebase
├── Launched: Late 2023
├── Status: LIVE PRODUCTION
├── Native token: XAH (not XRP)
└── Hooks: FULLY ENABLED

RELATIONSHIP TO XRPL:
├── Shares codebase ancestry
├── Separate network (not connected)
├── Different native token
├── Different validator set
├── Different governance
└── Independent operation

NOT THE SAME AS:
├── XRPL testnet (Xahau is production)
├── XRPL mainnet (different network)
├── A sidechain of XRPL (independent)
└── A temporary test environment
```

XAHAU SPECIFICATIONS

Network:
├── Network ID: 21337
├── Consensus: XRPL consensus (fork)
├── Block time: ~3-5 seconds
├── Transaction fees: XAH-based
└── Explorer: explorer.xahau.network

Native Token (XAH):
├── NOT XRP (completely different)
├── Initial distribution: Via airdrop
├── Use: Network fees, reserves
├── Trading: Various exchanges
└── Value: Independent of XRP

Hooks Capability:
├── Full Hooks implementation
├── Production ready
├── Real value at stake
├── Live applications
└── Growing ecosystem

Connection Options:
├── WebSocket: wss://xahau.network
├── RPC: https://xahau.network" target="_blank" rel="noopener noreferrer" class="text-cyan-400 hover:text-cyan-300 underline hover:no-underline transition-colors inline-flex items-center gap-1">https://xahau.network">https://xahau.network
├── Testnet available: xahau-test.net
└── Faucet for testnet XAH
```

XAHAU USE CASES

GOOD FIT:
├── Need production Hooks NOW
├── Building Hooks-native applications
├── Testing Hooks with real value
├── XAH ecosystem participation
├── Can't wait for XRPL mainnet
└── Don't require XRP specifically

NOT GOOD FIT:
├── Must use XRP as native asset
├── Need XRPL mainnet liquidity
├── Integrating with XRP ecosystem
├── Institutional clients requiring XRP
├── Don't want to manage two tokens
└── Need broader exchange support

HONEST ASSESSMENT:
├── Xahau is legitimate production network
├── But smaller ecosystem than XRPL
├── XAH has less liquidity than XRP
├── Fewer exchanges, less adoption
├── Trade-off: Hooks now vs. XRP ecosystem
```

---

The Hooks testnet is where you'll develop and test:

HOOKS TESTNET

Purpose:
├── Development environment
├── Testing before deployment
├── Learning and experimentation
├── NO real value at stake
└── Free to use

Access:
├── Website: hooks.xrpl.org
├── Hooks Builder: browser-based IDE
├── Testnet faucet: Free test tokens
├── Explorer: Available
└── Documentation: xrpl-hooks.readme.io

Differences from Production:
├── Test tokens (no value)
├── May reset periodically
├── Less stable than mainnet
├── Newer/experimental features
├── Smaller network

What You Can Do:
├── Write and compile Hooks
├── Deploy to test accounts
├── Test transaction flows
├── Debug execution
├── Iterate without cost
└── Learn without risk

The browser-based development environment:

HOOKS BUILDER FEATURES

Core Capabilities:
├── Code editor with syntax highlighting
├── C-to-WASM compiler
├── Account creation
├── Hook deployment
├── Transaction submission
├── Debug output (trace logs)
└── Example library

1. Create/import testnet account
2. Write Hook code in editor
3. Compile to WebAssembly
4. Deploy to your account
5. Test with transactions
6. Review debug output
7. Iterate

Limitations:
├── Browser-based (no offline)
├── Basic debugging
├── Limited code completion
├── No formal verification
├── Educational focus
└── Not for large projects

Best For:
├── Learning Hooks
├── Testing concepts
├── Quick experiments
├── Following tutorials
└── Prototype development

TESTNET → PRODUCTION PATH

Step 1: DEVELOP ON TESTNET
├── Write and test Hooks
├── Iterate freely
├── Use Hooks Builder
└── Cost: $0

Step 2: DEPLOY TO XAHAU TESTNET
├── Test with XAH testnet tokens
├── More realistic environment
├── Faucet available
└── Cost: $0

Step 3: DEPLOY TO XAHAU MAINNET
├── Production with real XAH
├── Real value at stake
├── Full functionality
└── Cost: Real XAH for fees/reserves

Step 4: WAIT FOR XRPL MAINNET (Optional)
├── When/if Hooks amendment enables
├── Deploy same code with XRP
├── May require adjustments
└── Timeline: Unknown

Note: Step 3 and Step 4 are independent choices.
You might do one, both, or neither.
```

---

XLS-101 is a proposed smart contract system for XRPL:

XLS-101 OVERVIEW

Status: PROPOSAL (Not implemented on mainnet)

Design Goals:
├── Permissionless deployment
├── Native XRPL feature integration
├── EVM-inspired developer experience
├── XRPL transaction familiarity
├── WebAssembly execution
└── More flexible than Hooks

Key Differences from Hooks:
├── Contracts live on pseudo-accounts
├── Direct call model (ContractCall tx)
├── Function-based interface
├── More flexible state management
├── Broader composability
└── Separate from user accounts

Published: July 2025 (XLS-101d)
Author: Mayukha Vadari (RippleX)
Discussion: GitHub XRPL-Standards #271

XLS-101 STATUS (November 2025)

WHAT EXISTS:
├── Formal proposal document
├── AlphaNet for testing
├── Active development
├── Community feedback period
└── RippleX engineering support

WHAT DOESN'T EXIST:
├── Production deployment
├── Mainnet availability
├── Confirmed timeline
├── Final specification
└── Amendment for voting

Development Path:
├── AlphaNet testing (now)
├── Community review (ongoing)
├── Specification finalization (TBD)
├── DevNet/TestNet (TBD)
├── Amendment proposal (TBD)
├── Validator voting (TBD)
└── Mainnet activation (TBD)

Translation: Don't expect this quickly.
Multi-year development cycle likely.
```

XLS-101 VS HOOKS COMPARISON

Feature Hooks XLS-101
──────────────────────────────────────────────────
Trigger Transaction Direct call
Account Attached Pseudo-account
Interface hook()/cbak() Functions
State Namespaced Per-contract
Composability Limited Better
Flexibility Constrained More flexible
Execution WASM WASM
Status Xahau live Proposal
Mainnet Not enabled Not enabled

Relationship:
├── XLS-101 inspired by Hooks
├── Hooks may coexist with XLS-101
├── Different use cases possible
├── Not necessarily competing
└── Both may reach mainnet eventually
```

---

The XRPL EVM Sidechain is live and production-ready:

XRPL EVM SIDECHAIN

Status: LIVE (June 2025)

What It Is:
├── EVM-compatible blockchain
├── Connected to XRPL via Axelar bridge
├── Full Solidity support
├── XRP as gas token
├── Separate consensus (PoA)
└── Production ready NOW

Technical Details:
├── EVM version: Compatible with Ethereum
├── Consensus: Proof of Authority
├── Block time: Fast (~seconds)
├── Bridge: Axelar (1:1 XRP ratio)
├── Cross-chain: 55+ networks via Axelar
└── Documentation: xrplevm.org

EVM SIDECHAIN VS HOOKS

Category EVM Sidechain Hooks
───────────────────────────────────────────────────────
Status LIVE mainnet Xahau only
Layer 2 (bridged) 1 (native)
Language Solidity C
Turing Complete Yes No
Flash Loans Yes No
Tooling Full Ethereum Limited
Learning Curve Solidity C + Hooks API
Composability Full Limited
XRP Bridged Native (Xahau: XAH)
Security Model EVM (known issues) Constrained (safer?)

CHOOSE EVM SIDECHAIN:
├── Need production NOW
├── Have Solidity expertise
├── Complex DeFi required
├── Existing EVM codebase
└── Accept bridging trade-offs

CHOOSE HOOKS:
├── Want native integration
├── Simple transaction logic
├── Security constraints valued
├── Learning for future XRPL
└── Xahau ecosystem participation
```

XRPL ↔ EVM SIDECHAIN BRIDGE

Trust Assumptions:
├── Axelar bridge security
├── PoA validator set
├── Cross-chain message integrity
└── Not trustless (federated)

Practical Implications:
├── Two-step process for assets
├── Bridge fees apply
├── Bridge downtime possible
├── Not instant settlement
└── Smart contracts can't affect L1

Risk Considerations:
├── Bridge hacks are common in crypto
├── Axelar has good track record
├── But not risk-free
└── Consider amounts at risk
```

---

PLATFORM DECISION MATRIX

Requirement Best Platform
──────────────────────────────────────────────────
Production deployment NOW EVM Sidechain
Native Hooks NOW Xahau
XRP as native asset NOW XRPL (native features only)
Development/learning Hooks Testnet
Complex DeFi EVM Sidechain
Simple transaction rules Hooks (Xahau)
Institutional requirements XRPL mainnet (native)
Maximum security XRPL (native features)
Future XRPL Hooks Testnet (learn now)
Cross-chain DeFi EVM Sidechain
```

WORKFLOW: "I want to learn Hooks"

WORKFLOW: "I need production smart contracts NOW"

WORKFLOW: "I'm building for institutional clients"

PLATFORM RISKS

XRPL MAINNET (Native Features):
├── Risk: Limited functionality
├── Risk: Can't implement custom logic
├── Mitigation: Use for what it does well
└── Stability: Highest

XAHAU:
├── Risk: Smaller ecosystem
├── Risk: XAH liquidity limited
├── Risk: Less exchange support
├── Mitigation: Understand limitations
└── Stability: Production-grade

HOOKS TESTNET:
├── Risk: No production value
├── Risk: May reset
├── Risk: Features may change
├── Mitigation: Development only
└── Stability: Test environment

XLS-101:
├── Risk: Not production ready
├── Risk: Timeline unknown
├── Risk: Spec may change
├── Mitigation: Track development
└── Stability: Experimental

EVM SIDECHAIN:
├── Risk: Bridge security
├── Risk: PoA centralization
├── Risk: L2 limitations
├── Mitigation: Limit bridged amounts
└── Stability: Production-grade
```

---

✅ Xahau is live production. Real value, real applications, Hooks working—not vaporware.

✅ XRPL mainnet does not have Hooks. This is fact, not speculation. The amendment hasn't passed.

✅ EVM Sidechain is production-ready. Launched June 2025, functional, growing ecosystem.

✅ XLS-101 is a real proposal with real development. Not speculation, but also not production.

⚠️ When Hooks will enable on XRPL mainnet. No confirmed timeline. Could be 2026, 2028, or never.

⚠️ When XLS-101 will reach production. Active development but multi-year timeline likely.

⚠️ How large the Xahau ecosystem will grow. Depends on adoption, which is uncertain.

⚠️ Whether validators will embrace programmability. Some prefer native features, some want smart contracts.

🔴 Planning production launches on unconfirmed timelines. "We'll launch when Hooks enable" is not a plan.

🔴 Confusing Xahau with XRPL mainnet. They're different networks with different tokens.

🔴 Assuming XLS-101 will replace Hooks. They may coexist, or timeline may differ.

🔴 Ignoring EVM Sidechain because it's "not native." It's production-ready and useful.

The XRPL programmability landscape is genuinely fragmented right now. Xahau offers Hooks in production but with XAH, not XRP. The EVM Sidechain offers full smart contracts with bridged XRP. XRPL mainnet offers only native features but the most liquidity and adoption. XLS-101 offers future potential but no timeline. Smart developers assess their specific needs and choose accordingly—or use multiple platforms for different purposes.

---

Assignment: Create a deployment strategy document for a hypothetical application that could benefit from programmability.

Requirements:

Part 1: Application Definition (20%)

• Subscription payment service for digital content

• Compliance-enforced remittance platform

• Automated savings tool with customizable rules

• Payment splitting service for businesses

• Functionality requirements

• Technical needs (state, transactions, etc.)

• Target users

• Timeline requirements

Part 2: Platform Analysis (40%)

For each platform, assess suitability:

Platform	Can Build?	Production Ready?	Trade-offs	Timeline
XRPL Native
Xahau
Hooks Testnet
EVM Sidechain
XLS-101

Part 3: Recommended Strategy (30%)

• Phase 1: What to build now and where
• Phase 2: How to migrate if/when options change
• Risk mitigation plan
• Fallback options

Part 4: Go/No-Go Criteria (10%)

• What milestones trigger Phase 2

• What risks would stop the project

• What external events you're monitoring

• Accuracy of platform assessment (30%)

• Practicality of strategy (30%)

• Risk awareness (20%)

• Clear documentation (20%)

Time investment: 2-3 hours
Value: This framework applies to any real project in the XRPL ecosystem

---

For Next Lesson:
We'll set up your development environment—Hooks Builder, local tools, testnet accounts—so you can start writing code. Bring a computer ready for development.

---

End of Lesson 4

Total words: ~4,200
Estimated completion time: 50 minutes reading + 2-3 hours for deliverable