Independent implementation / beta

Building a rusty road into the XRP Ledger.

Quaxar gives Rust developers a route into XRPL protocol, networking, storage, transaction execution, and node operations.

View source Explore improvements Run on Testnet Contribute
Status
Beta; production validator operation is not recommended.
Observed
Public-Testnet runs reached full and proposing and advanced with the validated chain.
Measured
A huge-profile node held full at about 7.3 GiB process RSS, and a medium-profile full window sat near 3.8 GiB, on one Testnet host.
Boundary
No intentional XRPL rule or amendment changes; complete behavioral parity is not claimed.
FIG. 1 CRATE MAP ASSEMBLY

crate map

Representative protocol and runtime modules in the Quaxar workspace.

CRATE
0%
Drag to rotate

    Why a second codebase matters

    Another way to inspect the same protocol.

    An independent implementation cannot inherit behavior by accident. Serialization order, hashes, state transitions, transaction semantics, peer behavior, and consensus boundaries have to be understood and reproduced.

    When Quaxar and rippled disagree, the difference becomes a concrete test case. That work exposes implicit assumptions, broadens the contributor and reviewer community, and strengthens the specification around existing XRPL behavior.

    Common questions

    IN:What is Quaxar?
    OUT:

    Quaxar is an independent Rust implementation of the XRP Ledger server. It syncs ledger data, participates in the peer overlay, serves HTTP and WebSocket JSON-RPC, and includes operator tooling.

    Continue through the project.