Dear community,
as explained by @bernhard in his announcement of the work on a token standard v2, DA stood up a “Token Standard V2 DevNet”, which is a temporary testing network aimed exclusively at organizations involved in validating the V2 token standard.
Use this guide to connect a fresh validator node to this network: TOKEN_STANDARD_V2_DEVNET.md
Watch this forum post to stay up to date on deployments and ask questions.
We will reset & redeploy the Token Standard V2 DevNet on Tuesday 7 exceptionally (instead of Monday 6, which is a holiday).
I will then also post the new splice version to use.
Starting reset&deploy of next version to Token Standard DevNet, will add another message once it’s done.
0.6.0-snapshot.20260407.2423.0.v98974cc3 is now deployed on the Token Standard v2 DevNet.
Heads-up: this week’s reset&deploy of the Token Standard DevNet will happen on Wednesday, as we’re awaiting Canton changes we want to include.
Starting reset&deploy of next version to Token Standard DevNet, will add another message once it’s done.
0.6.0-snapshot.20260415.2530.0.v13acc4fb is now deployed on the Token Standard v2 DevNet.
Please check the updated docs and download the latest release bundle.
Monday is a holiday in Zürich, so Token Standard DevNet will be reset & upgraded on Tuesday 21.
We won’t manage to deploy to Token Standard DevNet today due to technical issues, so we’re postponing the deployment to tomorrow Wednesday 22 April.
0.6.0-snapshot.20260422.2626.0.v5aaef00e is now deployed on the Token Standard v2 DevNet.
Please check the docs and download the latest release bundle.
root@Canton-Dev:~/splice-node/docker-compose/validator# docker pull ghcr.io/digital-asset/decentralized-canton-sync-dev/canton-participant:0.6.0-snapshot.20260422.2626.0.v5aaef00e
Error response from daemon: error from registry: denied
denied
I can’t pull it because it requires access. Could you grant me permission? GitHub username: tinhdowoss
Thank you!
@TinhDo
Try with:
docker pull ghcr.io/digital-asset/decentralized-canton-sync-dev/docker/canton-participant:0.6.0-snapshot.20260422.2626.0.v5aaef00e
Let me know if that works for you and I’ll update the docs.
Thank you, sir, it’s working fine now.
0.6.1-snapshot.20260427.2678.0.v86ff9ad5 is now deployed on the Token Standard v2 DevNet.
Please check the docs and download the latest release bundle.
0.6.3-snapshot.20260504.2741.0.v681c5054 is now deployed on the Token Standard v2 DevNet.
ATTENTION: the line canton.participants.participant.parameters.engine.contract-state-mode=NUCK MUST NOT be specified anymore, otherwise your validator will fail to startup
Please check the docs and download the latest release bundle.
0.6.4-snapshot.20260511.2808.0.vc0dc7ce8 is now deployed on the Token Standard v2 DevNet.
ATTENTION: the line canton.participants.participant.parameters.engine.contract-state-mode=NUCK MUST NOT be specified anymore, otherwise your validator will fail to startup
(this was already the case as of May 4th)
Please check the docs and download the latest release bundle.
0.6.5-snapshot.20260518.2872.0.vb91de5d4 is now deployed on the Token Standard v2 DevNet.
ATTENTION: the line canton.participants.participant.parameters.engine.contract-state-mode=NUCK MUST NOT be specified anymore, otherwise your validator will fail to startup
(this was already the case as of May 4th)
Please check the docs and download the latest release bundle.
25th May is a Holiday, so the Token Standard v2 DevNet deployment will happen on the 26th.
0.6.5-snapshot.20260526.2931.0.ve28a6722 is now deployed on the Token Standard v2 DevNet.
ATTENTION: the line canton.participants.participant.parameters.engine.contract-state-mode=NUCK MUST NOT be specified anymore, otherwise your validator will fail to startup
(this was already the case as of May 4th)
Please check the docs and download the latest release bundle.
0.6.7-snapshot.20260601.2982.0.v4f51a471 is now deployed on the Token Standard v2 DevNet.
ATTENTION: the line canton.participants.participant.parameters.engine.contract-state-mode=NUCK MUST NOT be specified anymore, otherwise your validator will fail to startup
(this was already the case as of May 4th)
Please check the docs and download the latest release bundle.