So I was thinking a lot about what exactly should the perfect token standard look like, and now I’m finally ready to declare my opinion on this subject. I thought, it might be more appropriate to share it here and not on the sailfish’s github repo. In short, I believe that we should reject ERCs and…

Thanks. So the new flow is: User sends ICP to canister via ICP ledger, and receives the block index as a result. User sends information about where to find the TX to the canister. Canister calls ICP ledger’s query_blocks() with the block ID, and receives back the block containing the TX. I take i…

Yes. For additional security I suggest to call query_blocks as an update instead of a query. In this way the IC will guarantee that the response can be trusted.

Since @RmbRT wants to call query_blocks from another canister it has to be an update call anyway. There’s no way to do inter-canister query calls, in particular not across subnets.

I got confused on the third point. If it’s a canister then use an update call and all is fine. If it’s not a canister, do one of 1) make an update call 2) do multiple queries 3) use the answer certification to check the result. I realised now that my answer was more confusing than helpful.

Hi, @RmbRT CDK0.5.1 supports notify, DFT standard will bring back notify support [image] Rust CDK v0.5.1 is out Developers I’m happy to announce that Rust CDK 0.5.1 is out. There are a few great additions hiding behind the minor version bump: The long-standing issue wit…

[image] witter: Hi, @RmbRT CDK0.5.1 supports notify, DFT standard will bring back notify support @witter just to be sure, have you read notify_with_payment128 in ic_cdk::api::call - Rust and particularly the point : It is safe to upgrade a canister without stopping it first if it sends out o…

Yes, i saw the message but still thanks for the kind reminder @mariop . [image] mariop: It is safe to upgrade a canister without stopping it first if it sends out only one-way messages. We have two things to optimize 1.Please take a look at the question 8 that we have thought about, we want …

Great. That went much quicker than I anticipated. I’m glad about your choice to reintroduce notifications into the DFT standard.

[image] mariop: EDIT: @rmbRT I realised my answer is wrong. You can call query_blocks as a query from a canister safely as we use certified variables that guarantee the answer can be trusted. If you call it from a custom client then you may want to call the method in replicated mode so that you …

Thoughts on the token standard

Developers

witter May 18, 2022, 3:34pm 163

Hi, @RmbRT CDK0.5.1 supports notify, DFT standard will bring back notify support

Topic		Replies	Views
ICRC-1 Token Standard Ledger Developers	128	7289	September 22, 2022
ICRC-1 Token Standard final draft Developers	40	3805	February 28, 2023
DRC20: A standard interface for Dfinity tokens (Request for Comments) Developers Discussing , community-consideration	0	661	January 26, 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	15657	November 26, 2024

Thoughts on the token standard

Related topics