Asset issuance through canton network
- Hi, I'm new to the Canton Network.
I want to learn how to issue, send, and receive assets on the Canton Network.
Could someone please provide the steps to get started with this?
It would be really helpful if you could share guidance on how to integrate asset issuance and transfer operations, along with any relevant references or example projects.So far, I have set up a Canton validator(on local network), explored the Wallet UI. - Does anyone have any idea about this?It would be a great help if someone could provide guidance on this.
Hi Rahil,
There are different aspects to consider, and of course, it depends on your level of understanding of Canton and your background in tokenization. Canton has different properties with regard to privacy and controls compared to some of the more widely known public blockchains.
To get an overview of what this concretely means for your tokenization project, here is a really insightful blog post explaining some of the key differences:
Tokenization of RWAs on Canton Network vs EVM Chains - Part 1If you are already familiar with Canton and how it's different, and just want to get hands-on and deploy an app, this is the right starting point: Canton Quickstart
The ERC-20 equivalent that will be proposed as a CIP can be found here: CIP-0056 - ERC-20 Equivalent
Another option to accelerate your tokenization project is through the Canton Utility, a product that offers smart contract models and a simple UI to issue tokens for any use case. You can find more details here: Canton Utility Documentation (registry workflows)
If you want to use it for a specific project, you should get in touch with DA to see how it fits your use case and what kind of licensing would be required.
I hope this helps!
Best regards,
FrankThe ERC-20 equivalent that will be proposed as a CIP can be found here: CIP-0056 - ERC-20 Equivalent
Note that CIP-0056 has already been accepted and its implementation will go live with the soon to be released splice 0.4.0 release.
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.Thanks for the response.
While checking the Canton Quickstart, I noticed that it requires a Daml Enterprise license, which makes it a paid product.I'm looking for a way to build this from scratch using only open-source tools—I don’t want to use any paid software.
Is there a developer guide or step-by-step tutorial available to help with this?
- toggle quoted message Show quoted textHi Rahil. The Canton Quickstart is not a paid product because you can use it under an evaluation license, free of charge.It is the recommended way to get started with building your Canton Network application because it is designed as application scaffolding that gives you a jumpstart. It provides several guides (e.g., step-by-step tutorial), like you requested. It does use open source tooling (e.g., gradle, etc.).It is published under the BSD Zero Clause License so you can experiment and adjust however you want. For example, you can remove the parts that aren't OSS and still get that jumpstart.On Wed, May 14, 2025 at 6:25 AM Rahil Mansuri via lists.sync.global <rahil=pointsville.com@...> wrote:
Thanks for the response.
While checking the Canton Quickstart, I noticed that it requires a Daml Enterprise license, which makes it a paid product.I'm looking for a way to build this from scratch using only open-source tools—I don’t want to use any paid software.
Is there a developer guide or step-by-step tutorial available to help with this?
--My best regards,Curtis Hrischuk, Ph.D.
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message. - In message #45
Could you share the estimated release date for Splice 0.4.0, or let me know where I can check the release versions of Splice? - Splice 0.4.0 will be released to DevNet, TestNet and MainNet concurrently with Canton 3.3.
You can see all the versions of Splice on the release notes pages for each network at:https://sync.global/docs - We are also starting to dive into this and wanted to share some links that we found valuable
Daml: https://docs.daml.com/
Splice: https://docs.dev.sync.global/app_dev/overview/index.html
Onboard External Party: https://docs.digitalasset.com/build/3.3/tutorials/app-dev/external_signing_onboarding
Token Standard: https://github.com/digital-asset-archive/cn-token-standard-proposal
Featured App Request: https://sync.global/featured-app-request/ - Thanks for sharing these links. Two comments:
On Mon, May 19, 2025 at 9:48 PM /ethen via lists.sync.global <ethen=send.it@...> wrote:We are also starting to dive into this and wanted to share some links that we found valuable
Daml: https://docs.daml.com/
Splice: https://docs.dev.sync.global/app_dev/overview/index.html
Onboard External Party: https://docs.digitalasset.com/build/3.3/tutorials/app-dev/external_signing_onboarding
We are in the process of updating / porting all the 2.x docs to the 3.3 docs and this link might move due to that. In case of doubt just use the search functionality or browse the ToC to find the content on external party signing again._._,_._,_This link is outdated. The token standard has since been accepted https://github.com/global-synchronizer-foundation/cips/blob/main/cip-0056/cip-0056.md; and implemented as part of splice: https://github.com/hyperledger-labs/splice/tree/main/token-standard--
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.