How to issue icp standard tokens based on ic

[avi]

I want to know how to release third-party tokens with the same standard as icp under dfinity. Where do I need to learn about this?

Or, can anyone know the standard hairstyle of ICP tokens?

[ccyanxyz]

DFinance Team is working on implementing a standard token canister template for Dfinity, we will then build a token issuance app (called DToken) based on the token template.
token canister code: GitHub - dfinance-tech/motoko-token: ERC20 style token template for Dfinity
demo: demo1.mp4 - Google Drive
website: https://dfinance.ai

[paulyoung]

These might be of interest:

https://github.com/enzoh/motoko-token

Proposal for a standard token interface

With the Sodium launch happening soon, I thought it’d be a good time to start thinking about token standards. Here’s my proposal for a unified canister interface, with support for single/multiple tokens per canister, fungible and non-fungible tokens. Feedback wanted! We should probably come up with a process for proposals (tentatively calling them ICIPs (Internet Computer Improvement Proposals). Perhaps a public github repo under dfinity?

Wrapped ICP Cycles (WIC) - Working MOTOKO code using ERC20 style token

We put up a repo showing how we can use wrapped ICP cycles as a token that can be converted back to cycles in future. This also provides an easier way for canister owners to add cycles to their canisters - buy WIC from an exchange and then use the simple “burn” call to add these cycles to an canister that the user wants to (as long as it has the accept_cycles call added to it).

[wang]

Have you thought about where to store transaction history? Users will want tools to explore transactions (and other things).

[ccyanxyz]

We are trying to store operation history in the token canister, and provide a set of query functions for users to get their transaction history.

The source code is in the ledger branch of our motoko-token repo: GitHub - dfinance-tech/motoko-token at ledger

Something I’m thinking about right now is whether users should pay for their usage of the token canister just like the gas fee model in Ethereum, and how to achieve that.

[Ori]

@ccyanxyz For reference (though you’re probably aware of this):
https://github.com/dfinity/motoko-base/blob/master/src/ExperimentalCycles.mo

https://sdk.dfinity.org/docs/language-guide/cycles.html

[ccyanxyz]

I do aware of this, but thanks anyway

[dostro]

@avi @ccyanxyz @Ori @wang @paulyoung - could we move this discussion to OpenCan? If we want a decentralized developers’ neuron for proposing standards to the NNS, we’ll need to align on where conversations on standards take place and there’s been a lot of great feedback that this is the right move: GitHub - OpenCan-io/opencan

[createtokenonicp]

Just made a service that lets you deploy icrc tokens without needing any code: https://createicptoken.xyz/

It uses the same code as ckBTC and ckETH.

[0xC0]

You can use the createToken feature of ICPEx to generate personalized burn fees and transfer fees, while also supporting the creation of tokens based on the ICRC-2 and DIP20 standards.
Refer to: https://icpex.org/createToken