Hi! As many of you know, the ICRC-1 interface was received very well and accepted: Internet Computer Network Status . If you want to learn more about the design principles behind the standard and the future steps, I wrote a medium post on this topic. The first item on the agenda is figuring out the…

Are there meeting minutes of the WG meeting for those who weren’t able to attend? dfinity/ICRC-1/blob/main/Charters.md#2022-09-06 # Ledger & Tokenization Working Group Charters ## 2023-12-12 Slide deck: n.a., [recording](https://drive.google.com/file/d/1Aqq3tJWh4ke0XPba42KX5MttY…

Ok, so encoders can use the abbreviation with automatic padding or can choose not to? That means there is no uniqueness, or, more precisely, we can have anywhere between 1-33 different encodings for the same account (because the encoder can choose to abbreviate any number of trailing zero bytes).

Regarding the choice of marker for “not a principal” I think we should also inform and ask people outside of the ICRC-1 group.

[image] timo: That means there is no uniqueness, or, more precisely, we can have anywhere between 1-33 different encodings for the same account (because the encoder can choose to abbreviate any number of trailing zero bytes). Yes, but the encoding is already non-unique in the presence of defa…

[image] roman-kashitsyn: advice applications not to use textual representations as keys (in a map/database, etc) Is that so easy? Thinking for example about a block explorer where you paste in the account identifier and then get back all transactions of it. So then I would paste in one encodi…

[image] roman-kashitsyn: [image] timo: Regarding the choice of marker for “not a principal” I think we should also inform and ask people outside of the ICRC-1 group. Yes, I’ve talked to @bjoern about it before the WG meeting and he was cool with that. I’ll prepare a spec change. Made a…

[image] timo: Might be confusing. Whether the pair is exposed or the textual encoding is shown can be easily solved with a toggle. But not the same way between different textual encodings. I also started thinking about block explorers and how users might be confused because some app didn’t ap…

[image] roman-kashitsyn: but will break some natural properties, such as ∀ a ∈ Account : decodeAccount(encodeAccount(a)) = a What is a here? The pair (principal, 32 bytes)? Then the property isn’t broken.

[image] timo: What is a here? The pair (principal, 32 bytes)? Then the property isn’t broken. The pair is (principal, opt blob). Optimizing (principal, opt DEFAULT) to (principal, null) is required for uniqueness, unless we remove the requirement that (principal, opt DEFAULT) is the same is (…

Maybe I don’t understand. The problem with the default account was always there, wasn’t it? What changes with respect to it? I am trying to understand the statement: [image] roman-kashitsyn: Then we have to enforce optimizations on the spec level and reject unoptimized encodings from the very …

Ledger & Tokenization Working Group Update

Developers

timo September 7, 2022, 9:52am 8

Made a general post about the topic here: Using the principals' textual encoding for other things than principals

Topic		Replies	Views
Announcing "Token Standard" as topic of the first meeting of the Ledger & Tokenization Working Group Developers	317	16610	November 26, 2024
Token Standards Working Group: Merging "Ledger and Token" and "NFT" Working Groups Developers icrc	25	497	January 13, 2026
ICRC-1 Token Standard Ledger Developers	128	8197	September 22, 2022
ICRC-1 Token Standard final draft Developers	40	3917	February 28, 2023
Voting results for the ICRC-1 Fungible Token Standard and next steps Developers	12	1104	July 21, 2022

Ledger & Tokenization Working Group Update

Related topics