What makes the Ripple alphabet special?

The XRP Ledger uses the same 58 unambiguous characters as Bitcoin but in a completely different order, beginning rpshnaf39wBUDNEGHJKLM4PQRST7VWXYZ. The reordering means a Ripple-encoded value and a Bitcoin-encoded value of the same bytes look totally different, which is intentional to keep the two address spaces distinct.

Base58Check is plain Base58 with integrity protection. Before encoding, a four-byte checksum — the first four bytes of SHA-256 applied twice to the payload — is appended. On decode, the checksum is recomputed and compared, so a single mistyped character is almost always caught instead of silently producing wrong bytes.

Why do I enter hex instead of text?

Ripple addresses and ledger objects are raw binary that rarely corresponds to printable text, so hex is the natural way to supply and read the payload. Enter the bytes as hex digits; spaces and colons between bytes are ignored.

What does a checksum mismatch mean?

It means the recomputed four-byte checksum does not match the last four bytes of the decoded value. Usually that is a typo, a truncated string, or a value that was never Base58Check-encoded in the first place. The tool refuses to return a payload it cannot verify.

Does this run locally?

Yes. The SHA-256 hashing uses the browser's built-in Web Crypto API and all encoding runs in your browser, so payloads and addresses never leave your device.

Base58 Ripple Encoder/Decoder

Ripple Base58 is the address encoding of the XRP Ledger. It shares Base58’s human-friendly 58-character set but uses a unique ordering, and real addresses are wrapped in Base58Check, which adds a four-byte checksum for typo protection. This tool encodes hex payloads to Ripple Base58 and decodes them back, verifying the checksum, entirely in your browser.

How it works

The encoder combines big-integer base conversion with an optional integrity check:

The hex payload is parsed into raw bytes.
In Base58Check mode, the payload is hashed with SHA-256, that digest is hashed with SHA-256 again, and the first four bytes of the result are appended as a checksum.
The bytes are treated as one big-endian integer and converted to base 58 against Ripple’s dictionary rpshnaf39wBUDNEGHJKLM4PQRST7VWXYZ2bcdeCg65jkm8oFqi1tuvAxyz, with leading zero bytes encoded as the leading symbol r.

Decoding reverses the conversion, then — in Base58Check mode — splits off the last four bytes, recomputes the double-SHA-256 checksum over the remaining payload, and confirms they match before returning the payload.

Tips and example

The double SHA-256 is what guards against transcription errors: change one character of a valid address and the recomputed checksum will almost certainly differ, so the tool reports a mismatch instead of handing back corrupt bytes. Use Raw mode when you only want the underlying base-58 conversion without a checksum — for example to inspect how a specific byte sequence maps into Ripple’s alphabet. Note that you supply the version-prefixed payload yourself; this tool encodes exactly the bytes you give it.