Skip to content
CCPEDIAby Unity Nodes
Discussions/App Development/Testing CIP-56 on LocalNetForum ↗

Testing CIP-56 on LocalNet

App Development5 posts90 views2 likesLast activity 3d ago
CIPs mentioned:CIP-0056CIP-0112
BE
berestovskyyOP
11d ago

Hi folks,
What is the recommended way to test CIP-0056 tokens on a LocalNet?

KE
kevmuko
5d ago

Could you clarify by what you mean by testing? You can use the token-standard CLI that’s bundled in the splice repo to simulate transfers of your CIP-0056 token.

github.com

splice/token-standard/cli at main · canton-network/splice

main/token-standard/cli

Splice repository. Contribute to canton-network/splice development by creating an account on GitHub.

SI
Simon_Meier
5d ago

And if you need a token that implements CIP-0056 then use the Amulet token from your LocalNet, which BTW also implements CIP-0112 in case you need to test TSv2 workflows.

BE
berestovskyy
4d ago

Thanks for the suggestions! By testing, I meant an integration test covering CIP-0056 token transfers with and without pre-approval via the DA registry. Amulet doesn’t use the DA registry though.

SI
Simon_Meier
3d ago

The common expectation is that testing the interaction with apps operated by other app providers happens on DevNet and TestNet. This matches the situation with internet services like Stripe or Github: you don’t run a local instance of them to test interactions with their APIs. You test against their real APIs using their testing support. For example, Stripe offers special test credit card numbers.

So for your case, consider usingAmulet as a mock for your token standard workflows in your CI running against LocalNet. This greatly reduces chance that your transfer workflows won’t work when then afterwards being tested on DevNet or TestNet against the DA registry.

← Back to Discussions