v0.1.0

canton-token-forge-0.0.1.dar is the whole dependency. It bundles all 6
splice-api-token-* interface packages it links against, at the package-ids
it was compiled with, so a consumer does not vendor Splice, does not run our
setup, and does not need to match SPLICE_TAG.

Consuming it

Download canton-token-forge-0.0.1.dar and save it as vendor/canton-token-forge.dar, then in your daml.yaml:

data-dependencies:
  - vendor/canton-token-forge.dar
build-options:
  - --target=2.1
  - --package=splice-api-token-holding-v1-1.0.0
  - --package=splice-api-token-metadata-v1-1.0.0
  - --package=splice-api-token-transfer-instruction-v1-1.0.0
  - --package=splice-api-token-allocation-v1-1.0.0
  - --package=splice-api-token-allocation-instruction-v1-1.0.0
  - --package=splice-api-token-burn-mint-v1-1.0.0

The --package lines are required. The bundled interface packages are hidden
by default, and importing Splice.Api.Token.* without them fails with
"member of the hidden package".

Requirements

Daml SDK	3.4.11
LF target	2.1
Built against Splice	0.6.7
Splice commit	c8d8d977794c514ed2ee9eb64de322a6779898f3

Verifying this asset

The DAR is byte-reproducible from a clean tree, so you can rebuild it at
v0.1.0 and compare rather than trust it.

sha256      147835e775e523f78c784996c43500c57e1ed97bcab97c97df6515b65f9332da
package-id  20d54824dc4d76694c70ac51dd5f0b9e063ab789ffa02d07432abb848c8360cc

Not included

splice-api-token-allocation-request-v1 is declared by this package but never
implemented, so it is not bundled. A consumer needing AllocationRequest takes
it from Splice directly.