# Announcing "Token Standard" as topic of the first meeting of the Ledger & Tokenization Working Group

**URL:** <https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925>\
**Category:** Developers\
**Created:** [April 5, 2022, 11:15am UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925 "2022-04-05T11:15:13Z")\
**Posts on this page:** 20\
**Page:** 15

<div class="post-metadata">

**Author:** ![skilesare](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/skilesare/32/5609_2.png) [@skilesare](https://forum.dfinity.org/u/skilesare)\
**Post date:** [April 30, 2024, 4:08pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/283 "2024-04-30T16:08:27Z")

</div>

I’ve personally built this a few times for a few different services, and yes, it would be awesome to standardize it. There is a bit of a conundrum around if you want the deposit addresses to be deterministic or private. Or deterministically private? Or rotate? If we defined the derivation and it would be fairly simple to write the component to manage it all.

---

<div class="post-metadata">

**Author:** ![skilesare](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/skilesare/32/5609_2.png) [@skilesare](https://forum.dfinity.org/u/skilesare)\
**Post date:** [April 30, 2024, 4:10pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/284 "2024-04-30T16:10:16Z")

</div>

Looks like I’m the only one on the call today so I’m going to drop off. Hopefully, we can get a bit more organized in next couple of weeks. Timo’s idea is interesting and we could tackle that.

---

<div class="post-metadata">

**Author:** ![timo](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/timo/32/5543_2.png) [@timo](https://forum.dfinity.org/u/timo)\
**Post date:** [May 1, 2024, 2:28pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/285 "2024-05-01T14:28:53Z")

</div>

> [@skilesare](#):
>
> This is the most reliable list we have at the moment.

Thanks!

So if I want to make a draft I just pick any ICRC number that isn’t used by any of the existing issues? Or are there numbers reserved already that don’t appear in the issues?

---

<div class="post-metadata">

**Author:** ![skilesare](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/skilesare/32/5609_2.png) [@skilesare](https://forum.dfinity.org/u/skilesare)\
**Post date:** [May 1, 2024, 3:03pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/286 "2024-05-01T15:03:08Z")

</div>

Just create an issue with an indication of what you want to use it for and then the number is yours.(the issue number assigned)

---

<div class="post-metadata">

**Author:** ![dieter.sommer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dieter.sommer](https://forum.dfinity.org/u/dieter.sommer)\
**Post date:** [May 13, 2024, 12:24pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/287 "2024-05-13T12:24:58Z")

</div>

@timo

The best is, as Austin mentioned, to create an issue here: [Issues · dfinity/ICRC · GitHub](https://github.com/dfinity/ICRC/issues)  
The issue number `x` you receive is your ICRC number.

Then you can create a subdirectory `icrc-x` in the `ICRCs` directory of the `https://github.com/dfinity/ICRC` repository with your initial or empty draft if you want to develop it in public.

There is some tooling available to generate a Candid file from a standard specification and lint it if you use the according markup to annotate your Candid type and method definitions. See, e.g., ICRC-7 as example. The tooling is not deployed in the ICRC repo at this point.

Hope that helps!

---

<div class="post-metadata">

**Author:** ![dieter.sommer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dieter.sommer](https://forum.dfinity.org/u/dieter.sommer)\
**Post date:** [May 13, 2024, 12:32pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/288 "2024-05-13T12:32:48Z")

</div>

Does anyone have suggestions for the WG call tomorrow, May 14?

---

<div class="post-metadata">

**Author:** ![mariop](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/mariop/32/5114_2.png) [@mariop](https://forum.dfinity.org/u/mariop)\
**Post date:** [May 13, 2024, 3:11pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/289 "2024-05-13T15:11:27Z")

</div>

We could talk about [ICRC-2: It is practically impossible for users to manage allowances · Issue #186 · dfinity/ICRC-1 · GitHub](https://github.com/dfinity/ICRC-1/issues/186) and potential solutions to this. The only problem is that I’m not sure I’ll be able to join as I have another meeting overlapping. I’ll see if I can move the other meeting so that I can join.

---

<div class="post-metadata">

**Author:** ![dieter.sommer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dieter.sommer](https://forum.dfinity.org/u/dieter.sommer)\
**Post date:** [May 13, 2024, 7:24pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/290 "2024-05-13T19:24:02Z")

</div>

@mariop This is a great idea, but only makes sense if you can join. Would be great if you could move your other meeting. Thanks!

---

<div class="post-metadata">

**Author:** ![mariop](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/mariop/32/5114_2.png) [@mariop](https://forum.dfinity.org/u/mariop)\
**Post date:** [May 14, 2024, 9:12am UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/291 "2024-05-14T09:12:36Z")

</div>

> [@dieter.sommer](#):
>
> This is a great idea, but only makes sense if you can join. Would be great if you could move your other meeting. Thanks!

I will be in the WG today, the other meeting was moved. I proposed we discuss about the problem and a potential solution and its implications. I’ll prepare the slides and drive the conversation.

---

<div class="post-metadata">

**Author:** ![dieter.sommer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dieter.sommer](https://forum.dfinity.org/u/dieter.sommer)\
**Post date:** [May 14, 2024, 4:09pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/292 "2024-05-14T16:09:42Z")

</div>

We cut the meeting short this afternoon and have the following agenda for the meeting in 2 weeks:

- The issue [ICRC-2: It is practically impossible for users to manage allowances · Issue #186 · dfinity/ICRC-1 · GitHub](https://github.com/dfinity/ICRC-1/issues/186) and potential solutions to this. @mariop is preparing the content and ideally already a concrete proposal to discuss.

---

<div class="post-metadata">

**Author:** ![dieter.sommer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dieter.sommer](https://forum.dfinity.org/u/dieter.sommer)\
**Post date:** [May 27, 2024, 12:54pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/293 "2024-05-27T12:54:08Z")

</div>

In tomorrow’s WG meeting we will be discussing proposed improvements to ICRC-2. See [ICRC-2: It is practically impossible for users to manage allowances · Issue #186 · dfinity/ICRC-1 · GitHub](https://github.com/dfinity/ICRC-1/issues/186). @bogwar will be leading the session and making a proposal.  
Hope to see many of you in the meeting tomorrow!

---

<div class="post-metadata">

**Author:** ![sea-snake](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/sea-snake/32/7243_2.png) [@sea-snake](https://forum.dfinity.org/u/sea-snake)\
**Post date:** [May 28, 2024, 2:12pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/294 "2024-05-28T14:12:44Z")

</div>

Can’t find a link to the WG meeting, any suggestions where I can find it? Don’t see any zoom link in the agenda.

---

<div class="post-metadata">

**Author:** ![dieter.sommer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dieter.sommer](https://forum.dfinity.org/u/dieter.sommer)\
**Post date:** [May 28, 2024, 5:12pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/295 "2024-05-28T17:12:45Z")

</div>

Hi @sea-snake, only seeing this now after the meeting. There is a Google Calendar link in the top of the topic.

[Google Calendar](https://calendar.google.com/calendar/u/0/r?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t)

The Zoom link is in the calendar. As it may change, please import the calendar and always use the most recent link there. The current one is [this](https://dfinity.zoom.us/j/99093158767?pwd=NEhFdk9yemtmT2NoYW1Ta2VWM2VzZz09).

---

<div class="post-metadata">

**Author:** ![sea-snake](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/sea-snake/32/7243_2.png) [@sea-snake](https://forum.dfinity.org/u/sea-snake)\
**Post date:** [May 28, 2024, 6:22pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/296 "2024-05-28T18:22:22Z")

</div>

If any proposal was presented in the session, is there any link I can check? The earlier issue link only describes the issue but doesn’t have any links to a proposal yet.

Regarding the topic, since a wallet already needs to keep track of allowances anyway (to check if a transfer\_from is allowed). I don’t see why there can’t be a method to return these allowances. In ICRC-37 there’s also methods to get a list of approvals for similar use cases.

Relying on the index canister only seems logical for historical state, but as far as I understand, allowances are an ongoing state until they expire or reach 0, they’re used and needed within the canister to do a transfer\_from.

---

<div class="post-metadata">

**Author:** ![dieter.sommer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dieter.sommer](https://forum.dfinity.org/u/dieter.sommer)\
**Post date:** [May 29, 2024, 6:22am UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/297 "2024-05-29T06:22:19Z")

</div>

Yes, a proposal was presented, @bogwar will post the slides shortly here for reference. We can continue the discussion on the forum.

---

<div class="post-metadata">

**Author:** ![bogwar](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/bogwar/32/2161_2.png) [@bogwar](https://forum.dfinity.org/u/bogwar)\
**Post date:** [May 29, 2024, 8:15am UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/298 "2024-05-29T08:15:29Z")

</div>

Here’s [the slides](https://docs.google.com/presentation/d/1MZGdAOu0c4lq9FJjcaSkM6jVxk3rxPMrst3cfdP7Y0Y/edit?usp=sharing) I’ve used for the discussion.

---

<div class="post-metadata">

**Author:** ![skilesare](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/skilesare/32/5609_2.png) [@skilesare](https://forum.dfinity.org/u/skilesare)\
**Post date:** [May 29, 2024, 1:42pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/299 "2024-05-29T13:42:36Z")

</div>

My suggestion was to grab a new ICRC Number and update the function to something like the following to follow the emerging pagination standards in ICRC 7,etc.

icrc84\_list\_allowances(filter: opt Account, prev: opt Allowance, take: opt nat);

There was some discussion about needing to add this to ICRC37, but as you pointed out, I think we already have icrc37\_get\_token\_approvals and collection approval that would let a service check for approvals on owned NFTs which may be sufficient.

---

<div class="post-metadata">

**Author:** ![dieter.sommer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dieter.sommer](https://forum.dfinity.org/u/dieter.sommer)\
**Post date:** [June 10, 2024, 4:00pm UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/300 "2024-06-10T16:00:09Z")

</div>

Tomorrow, June 11, we will continue the discussion of the most recent Working Group meeting. See [here](https://drive.google.com/file/d/1mVGgbFfKyZYhQRF8mwyJKrS7PzIh3l4i/view?usp=share_link) for a link to the recording of the meeting, minutes are not available for this meeting.

---

<div class="post-metadata">

**Author:** ![dieter.sommer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dieter.sommer](https://forum.dfinity.org/u/dieter.sommer)\
**Post date:** [June 25, 2024, 11:35am UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/302 "2024-06-25T11:35:38Z")

</div>

The proposal for the discussion for the WG meeting this afternoon is to have a look at how standards can be “extended”. There is currently a concrete example available that would require an extension that is merely a clarification, but not adding new / different normative parts to the standard.

---

<div class="post-metadata">

**Author:** ![dieter.sommer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dieter.sommer](https://forum.dfinity.org/u/dieter.sommer)\
**Post date:** [July 5, 2024, 11:43am UTC](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925/303 "2024-07-05T11:43:41Z")

</div>

Please find the slides and recordings of the recent meeting [here](https://drive.google.com/drive/u/0/folders/1TlaDISjZpAKpqJdXzYMw4hhuKj5YxZ3J).

**Meeting of 2025-05-28**

- [Slides](https://docs.google.com/presentation/d/1MZGdAOu0c4lq9FJjcaSkM6jVxk3rxPMrst3cfdP7Y0Y/edit?usp=share_link)
- [Recording](https://drive.google.com/file/d/1mVGgbFfKyZYhQRF8mwyJKrS7PzIh3l4i/view?usp=share_link)

**Meeting of 2025-06-25**

- [Slides](https://docs.google.com/presentation/d/1p4i1IfMqXS_rjuNdM8rt3TU5VmsjOgs3xvVYeoEJwyU/edit?usp=share_link)
- [Recording](https://drive.google.com/file/d/1G7rn64Lo14JkWA5K8PI-h4_rG4W7PyAa/view?usp=share_link)

[Previous page](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925.md?page=14)

[Next page](https://forum.dfinity.org/t/announcing-token-standard-as-topic-of-the-first-meeting-of-the-ledger-tokenization-working-group/11925.md?page=16)
