Hi folks, While working on the ICRC-1 fungible token standard we realised that it would be nice to have a string format for addresses that is human readable and compatible with most systems. This format is orthogonal to the standard but is a nice to have that could be incorporated with the standard…

Great post, thank you @infu ! Should we consider bech32 (BIP0173) instead of base58? I think the motivations given to use bech32 instead of base58 are very interesting and we are in the position where we can pick the better option.

Of course, the working group can have its own decision. I just wish ICRC1 was better. My preference would be for the Account to be a 32-byte hash value with a check digit, which is the format that users are used to. There are a lot of things that can happen when users copy addresses, and they can …

[image] bitbruce: My preference would be for the Account to be a 32-byte hash value with a check digit, which is the format that users are used to. There are a lot of things that can happen when users copy addresses, and they can easily lose assets. For example, if the address has a “.” etc., b…

I agree. Encoding can improve the user experience. As mentioned above, ICP will be compatible with Account-id. In a dapp, for example a wallet, three address formats will appear in the UI for better compatibility: Principal, AccountId (It is being used by CEX), ICRC1Address. The question is, is th…

One of the benefits of base32 from that link is The mixed case in base58 makes it inconvenient to reliably write down, type on mobile keyboards, or read out loud. So it’s basically removing the uppercase characters. This will also make addresses look better in UIs Bech32 consists of (custom text) …

[image] infu: That ship has sailed Or is it? Apparently you have lost the support of psychedelic, who openly criticized icrc-1 and decided to continue push its own DIP-20 without subaccount . Now you are about to lose other people who supports subaccount but wanted a uniform & opaque AccountI…

[image] bitbruce: I hope you will do more to understand the habits of crypto users, especially those of the ETH ecosystem. While this is important, if the ic is to be successful it will come from users that have never seen an address before. 95%(or more) of the world is a blank canvas here. …

Agreed but this isn’t a step in that direction, currently IC addresses are even more confusing than BTC’s, maybe encoding can help, but we’re far from something the average user can understand.

So let’s fix it. Why not a phone book subnet/canister that does nothing but translate something like @savage_wolf_banana to accounts. We are already taking about dns right? A couple groups have tried .icp, but this seems like one of those things that is more protocol level. Random addresses could b…

ICRC-1 Account Human Readable Format

Developers

neeboo August 5, 2022, 4:19pm 21

https://forum.dfinity.org/t/proposal-of-using-bech32-format-address-an-alternative-and-sounded-way-to-display-account-id/9898?u=neeboo

3 Likes

Topic		Replies	Views
Addresses - defining the standard Developers Discussing , community-consideration , sns	11	315	April 9, 2025
Voting results for the ICRC-1 Fungible Token Standard and next steps Developers	12	1069	July 21, 2022
Completed: ICDevs.org - Bounty #26 - ICRC-1 Motoko - up to $10k Bounties & RFPs Discussing	64	4449	April 6, 2023
ICRC-1 Token Standard Ledger Developers	128	7106	September 22, 2022
Announcing "Token Standard" as topic of the first meeting of the Ledger & Tokenization Working Group Developers	319	15338	November 26, 2024

ICRC-1 Account Human Readable Format

Related topics