Thoughts on the token standard

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


@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 only one-way messages.

Are you going to replace all calls with one-way messages?

1 Like

Yes, i saw the message but still thanks for the kind reminder @mariop.

We have two things to optimize
1.Please take a look at the question 8 that we have thought about, we want to let the payee canister be notified, so as to know in time that the payment has occurred. We removed notify for security reasons, now we’re bringing it back :slight_smile:
2. In the token standard, there is only three external update call:

  • auto-scaling-storage archives historical transaction records, we will replace it with one-way message
  • create auto-scaling-storage canister (management create_canister),This cannot be replaced for the time being, maybe the management canister can support the one-way method in the future, we will replace
  • install auto-scaling-storage canister code (management install_code) ,the same as above.
1 Like

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

Also in is20. We will this week have the PR reintroducing a similar flow.

1 Like

Here is the PR,Feature: support notify by witter-deland · Pull Request #130 · Deland-Labs/fungible-token-standard · GitHub, more test is comming. :slight_smile:
After the test is over, it will be merged into the master branch. This feature will be released in the next version.

1 Like

To all of those interested in token standards, please help us as a community to coalesce around a minimum viable standard that we can all build off of.

Today we have the Ledger & Tokenization Technical Working Group: Launch Meeting - Zoom

We are also currently collaborating on a Google Doc to discuss the minimum viable standard.
Please leave comments so that we can discuss during the working group an hour and a half from now: IC Ledger Standard - Google Docs


Hi,DFT (fungible-token-standard) v0.6.0 released:
Major Updates:

  1. Code refactoring & optimization for easier expansion
  2. Built-in implementation of mineable & burnable & batchTransfer & batchMint configurable extensions
  3. More unit tests (coverage 85%)
  4. Re-support notify @RmbRT
  5. Auto-scaling storage optimization & unit tests

full changes:



I personally support the addition of batchtransfer and batchmint. In IC ecology, cross canister calls often occur, and batch processing interfaces should be the basic requirements of IC. This can reduce many cross canister calls. Increase TPS per unit time of DAPP

This is an optional feature, if you need it, here is the configuration documentation.
If you just want to test it, this package dft_all_features.wasm is the package that contains all the optional features

I saw the DFT standard, and I am very confused as to why there is an interface such as setFee. The existence of Fee will make all businesses confused in the processing of the amount.

Introduction | Dfinity Fungible Token Standard Documentation Q4

  1. Reverse gas model
  • Question: How to prevent ddos attacks
  • Consideration: The call of the canister does not require the caller to pay gas fees(canister pay the gas fees)
  • Solution: Any update call to canister should be charged to the caller

ddos attack? ? ? I can attack the container without calling transfer

I think that a mature project party will not consider the issue of handling fees, because a successful project does not need to rely on handling fees to survive.

Malicious consumption of cycles is also a DDOS attack.
But the query method also consumes cycles
If the call consumes 500w cycles at a time
query consumes 50w cycles at a time
I don’t need to call the call method, the robot can call query.

1 Like

I don’t think using a fee will prevent it. It should be promoted to let ICP officials deal with this problem of malicious consumption of cycles

1 Like

I just looked at other standards, yes, those based on homogenized tokens have the fee field, and I went to look at non-fungible tokens. I was surprised to find out. I can’t find the fee field, what is the so-called How to prevent ddos attacks in the end.

Hey guys
Im a new developer. Currently im creating a dapp on icp and I havd few questions:
Why do you need to launch your own projects token on ic instead of using icp token?
Im building a dapp tgat requires community to vote on decisions.
If i build my own dapps token how do i even set it up? Does IC has any “dex” like uniswap? Do i create the token based on any token standart projects around, then create a icp/mytoken pair on “icpdex”. How to set up an icon for my token? So many questions…

1 Like

@808mafia This post (like others you have posted recently) are not productive or helpful to advancement of the ecosystem so I’m closing it down. If you would like to help, you can actually join the token working groups not post trolling comments.

I know it can be seen as harsh, but it’s my role to help the community have a healthy forum for deep discussions.