nanoo.tools - Unofficial Nano Currency Developer Wiki + Toolbox

NANO vanity burn (Joke tool) V1.3

Minimizing circulating supply with style

Type or paste a string to generate an artificial NANO vanity burn address that matches all formal requirements. Maximum vanity input is 52 characters. NANO addresses won't allow characters like 0 2 L V, they will be replaced by similiar looking characters. No symbols or spaces are allowed in addresses, they will be filled with the padding character. Addresses have to start with either xrb_1 or xrb_3. Input will be converted to small letters.

Nice to know:

Burn Addresses either don't have a corresponding private key, or in case they do, you will most likely never be able to generate that one due to the sheer amount of possible private keys (16⁶⁴).

Fully functional vanity addresses are a real thing though, they are made by generating a huge number of random private keys and searching their corresponding address for desired strings. With regular CPU power you'll be able to generate about 5000-10000 addresses per second, so it is feasible to achieve 6 or 7 predefined characters.

The last 8 characters of an address is the checksum which apps can use to validate your address for typos. You can't really influence that part in a predictive way. The checksum is the main reason why this app exists, because nodes would reject blocks with totally random addresses as invalid.

NANO uses a special Base32 encoding algorithm for better human readability of addresses (same charset as z-base-32 but in alphabetical order). Base32 is simply a translation table to convert binary strings to predefined letters and numbers, 5 bit a pop. Each 5-bit-pattern is assigned to one letter on the list [13456789abcdefghijkmnopqrstuwxyz] (2⁵=32 possible patterns, hence 32 assigned letters)

Addresses will always start with a 1 or 3, because the 256 bit binary pattern of the public key leaves a dividing rest of one when chopped into 5-bit-pieces. That single bit then gets zero-padded, resulting in either '00001' or '00000', hence leaving only the first two characters of the encoding table as an option.

Don't use uppercase letters in addresses. Theoretically it wouldn't affect their function because they don't collide with anything within the Base32 charset, but this edge-case is not part of the standard and most wallets will reject these.