Anúncios incomodam? Ir Sem anúncios Hoje 

Base58 Encoder / Decoder

DadosDesenvolvedorSegurança

ANÚNCIO · REMOVER?

ENTRADA

Processo Automático

SAÍDA

Lado cliente

ANÚNCIO · REMOVER?

Guia

Base58 Encoder / Decoder

Encode and decode Base58 strings used in Bitcoin addresses, IPFS CIDs, and other blockchain systems. Supports multiple alphabet variants and Base58Check with SHA-256d checksum verification.

Como usar

Switch between Encode and Decode modes. For encoding, enter text (UTF-8) or hex data and select your Base58 variant. For decoding, paste a Base58 string to get the decoded text and hex output. Enable Base58Check to add or verify the 4-byte SHA-256d checksum used in Bitcoin addresses.

Características

Three Alphabet Variants – Bitcoin, Flickr, and Ripple Base58 alphabets
Base58Check Support – Encode with SHA-256d checksum or verify existing checksums on decode
Dual Input Formats – Encode from UTF-8 text or raw hex strings
Dual Output on Decode – See decoded data as both UTF-8 text and hex
Arbitrary Precision – BigInt arithmetic handles any input length correctly
Leading Zero Preservation – Properly handles leading zero bytes as required by the Base58 spec
Cliente 100% – All encoding and decoding happens in your browser

ANÚNCIO · REMOVER?

 Perguntas frequentes

Why was Base58 created instead of using Base64?

Base58 was designed by Satoshi Nakamoto for Bitcoin to avoid visually ambiguous characters. It removes 0 (zero), O (uppercase o), I (uppercase i), and l (lowercase L) from the Base64 alphabet because they look too similar in many fonts. It also removes + and / to make Base58 strings easy to double-click and select.
What is Base58Check and how does the checksum work?

Base58Check adds a 4-byte checksum to catch typos and transmission errors. The checksum is computed by taking the SHA-256 hash of the SHA-256 hash (double SHA-256) of the payload, then appending the first 4 bytes of that hash. When decoding, the checksum is recalculated and compared to detect corruption.
What is the difference between Bitcoin, Flickr, and Ripple Base58 alphabets?

All three use 58 characters but in different orders. Bitcoin uses 123456789ABCDEFGH...with uppercase first. Flickr swaps the case (lowercase before uppercase). Ripple uses a completely different character ordering starting with rpshnaf39w. The encoding algorithm is identical, only the character mapping differs.
Where is Base58 encoding used besides Bitcoin?

Base58 appears in IPFS content identifiers (CIDs), Solana addresses, Monero addresses, Litecoin addresses, and various other cryptocurrency systems. It is also used in some distributed identity protocols and content-addressable storage systems where human-readable, unambiguous identifiers are needed.