Hi, The Ledger&Tokenization Working Group has finalized the second draft of the ICRC-3 standard to access the Block Log of Ledgers. You can find the rendered document here . The changes since the first draft are: improved definition of the icrc3_get_tip_certificate endpoint to fetch the certified…

[image] mariop: <standard_number><field_type> I’m okay with this, since icrc-7 also is doing the same thing… eg: 7xfer hopefully icrc-3 will start progressing now.

[image] kayicp: what do you mean by this? I thought the usual design was always the “one main ledger with multiple archive canisters”. ICRC-3 is designed to be used with generic Ledgers and we cannot make assumptions about archives or what not. Therefore ICRC-3 was designed such that any blo…

Regarding 1: I don’t have a strong prejudice except that I don’t want to have to refactor my code :slight_smile: I guess it does make sense to have this at the top level. [image] mariop: Add a new endpoint icrc3_supported_block_types to list all the supported block types. Given the open nature …

[image] mariop: improved definition of the icrc3_get_tip_certificate endpoint to fetch the certified tip of the chain, i.e. the last block index and the last block hash Hey Mario, can we get a certified approval? This will help with DOS attacks.

[image] Maxfinity: Hey Mario, can we get a certified approval? This will help with DOS attacks. Yes, you can (if you are not a canister): make an approval and get back the approval block index get the tip certificate via icrc3_get_tip_certificate fetch all blocks from the tip in 2. to the b…

The ICRC-3 topic will be discussed in the WG meeting this afternoon. [image] Announcing "Token Standard" as topic of the first meeting of the Ledger & Tokenization Working Group Developers Dear WG! We have a topic of broad interest for tomorrow’s agenda: ICRC-3 Specifi…

[image] mariop: point 2 of the Generic Block Schema section requires ICRC-3 blocks to have a field tx: Map with a field of type op: Text inside. The change request is to drop this requirement in favour of having a field type: Text at top level which defines the type of the block. I think this…

[image] levi: Since a ledger can upgrade to support more block types, a client that has called icrc3_supported_block_types before the ledger upgraded, will still end up getting the new block types when reading the block log. If the client must call icrc3_supported_block_types before every time i…

That works, the certificate verification can be used in inspect message.

[image] mariop: The advantage of icrc3_supported_block_types is that you get an error as quickly as possible before doing any operation and that it is a well defined error containing e.g. the URL of the supported block so that the dev can immediately understand the work they have to do to suppor…

ICRC-3 Draft v2 and Next Steps

Developers

dieter.sommer March 5, 2024, 1:04pm 51

The ICRC-3 topic will be discussed in the WG meeting this afternoon.

Topic		Replies	Views
ICRC-3 Draft and Next Steps Developers community-consideration	9	1111	November 10, 2023
Toward a Cleaner ICRC-3: One Format for ICRC-1/2, Clear Rules for the Future Developers	23	477	September 24, 2025
Announcing "Token Standard" as topic of the first meeting of the Ledger & Tokenization Working Group Developers	317	16741	November 26, 2024
ICRC-1 Token Standard final draft Developers	40	3971	February 28, 2023
Call for Participation: NFT Token Standard Working Group [Status Updated] Developers	248	10052	December 2, 2024

ICRC-3 Draft v2 and Next Steps

Related topics