ICRC-1 Token Standard Ledger

Developers
109

Ok, let’s see how we can encode the account record {Principal, Subaccount} for better UX. The requirement is that every client(browser) can decode the address easily into Principal 29bytes and Subaccount 32bytes

Which one do you like most?

  • using Principal encoding
    7oxcw-qurpx-fcebq-q5ocd-gvdyn-2pf2n-vec43-o5f4a-zx43m-d6uln-tqe-miyz7-tabae-aqcai-baeaq-caiba-eaqca-ibaea-qcaib-aeaqc-aibae-aqcai-bae
  • using Principal encoding adaptive*
    miyz7-tabae-aqcai-baeaq-caiba-eaqca-ibaea-qcaib-aeaqc-aibae-aqcai-baeae-aqcai
  • using base58 (Bitcoin)
    2xoMuudmMrMNJHVXhij52NfjKUDNk3rZgT5tqjQ1RPmtJfa8P4yjZDufTP4kejWnmNR5oomvjBcSKe9xXYnL
  • adaptive * base58 (Bitcoin)
    AnwNBG7a4rVJizGXQWTSQc69pFCUTCQJTC951zbLUCaY

0 voters

*The adaptive one doesn’t show zeroes. The size will increase and match non-adaptive one if fully used, but such addresses will probably will be used only by canisters internally, so the perceived size will be small.