Hi everyone, The final draft of the ICRC-1 Fungible Token Standard is available at dfinity/ICRC-1 . I’ve incorporated all the changes we discussed plus the missing transfer errors. Please have a look and feel free to give feedback here or on Discord. I would like to share the next steps to make th…

Are Timo’s last minute suggestions of any value here? [image] Thoughts on the token standard Developers I had some thoughts on the token standard. Several payment flows have been discussed in this thread and other threads and interfaces have been proposed for the flows. A…

I know it’s a lot of work and there’s a lot of detail involved, but I wouldn’t feel comfortable voting yes on something as important as an “official” token standard until: Flow diagrams for basic use cases with ICRC-1 are made available. For example, I saw an excellent diagram by @infu on Discord …

+1, I also liked what I read by @timo here. It seems quite general and powerful.

In support of this minimal standard which can be upgraded with extensions later. Right now it is not important for the ICRC-1 standard to be perfect, but for the ICRC-1 standard to be delivered so that the Foundation can deliver the SNS, BTC on-chain and remove uncertainty for canister developers.

[image] bobbylingus: Are Timo’s last minute suggestions of any value here? They are but not for the base standard. We should consider them when we talk about the approve/transferFrom payment flow.

[image] jzxchiang: Flow diagrams for basic use cases with ICRC-1 are made available. For example, I saw an excellent diagram by @infu on Discord for a payment flow (attached below), but how about 3rd party transfers or atomic swaps? There are existing examples such as NNS, SNS and CMC that us…

[image] jzxchiang: A better explanation of fees. I also think a better explanation of fees is needed. We are saying the implementation can decide, but in which way and how much freedom does the implementation have? For example, can the implementation: charge a one-time fee when a subaccount…

A couple of things that we should be aware of and should explicitly state in the description of the standard: It is specifically designed for one-canister ledgers, i.e. not ledgers that are sharded over multiple canisters. It does not guarantee the property that from a private key alone you can re…

[image] timo: I also think a better explanation of fees is needed. We are saying the implementation can decide, but in which way and how much freedom does the implementation have? For example, can the implementation: charge a one-time fee when a subaccount is first used? charge a recurring fee…

[image] timo: It is specifically designed for one-canister ledgers, i.e. not ledgers that are sharded over multiple canisters. The ICP Ledger and the ICRC-1 Ledger from DFINITY are both multi-canister ledgers and both support the standard. [image] timo: It does not guarantee the property…

ICRC-1 Token Standard final draft

Developers

bobbylingus July 15, 2022, 8:23pm 2

Are Timo’s last minute suggestions of any value here?

Topic		Replies	Views
ICRC-1 Token Standard Ledger Developers	128	7331	September 22, 2022
Voting results for the ICRC-1 Fungible Token Standard and next steps Developers	12	1075	July 21, 2022
Announcing "Token Standard" as topic of the first meeting of the Ledger & Tokenization Working Group Developers	317	15660	November 26, 2024
Thoughts on the token standard Developers	199	21662	December 26, 2022
Token Standards Working Group: Merging "Ledger and Token" and "NFT" Working Groups Developers icrc	25	391	January 13, 2026

ICRC-1 Token Standard final draft

Related topics