Alpha 3.3: Convenience endpoint to generate topology transactions for external signing
Expected to be stable in 3.5
You may use this endpoint to generate the common external topology transactions which can be signed externally and uploaded as part of the allocate party process
Note that this request will create a normal namespace using the same key for the identity as for signing. More elaborate schemes such as multi-signature or decentralized parties require you to construct the topology transactions yourself.
Documentation Index
Fetch the complete documentation index at: https://docs.canton.network/llms.txt
Use this file to discover all available pages before exploring further.
Ledger API standard JWT token
Synchronizer-id for which we are building this request. TODO(#27670) support synchronizer aliases
Required
The actual party id will be constructed from this hint and a fingerprint of the public key
Required
Public key
Required
If true, then the local participant will only be observing, not confirming. Default false.
Optional
Other participant ids which should be confirming for this party
Optional: can be empty
Confirmation threshold >= 1 for the party. Defaults to all available confirmers (or if set to 0).
Optional
Other observing participant ids for this party
Optional: can be empty
Response message with topology transactions and the multi-hash to be signed.
The generated party id
Required
The fingerprint of the supplied public key
Required
The serialized topology transactions which need to be signed and submitted as part of the allocate party process
Note that the serialization includes the versioning information. Therefore, the transaction here is serialized
as an UntypedVersionedMessage which in turn contains the serialized TopologyTransaction in the version
supported by the synchronizer.
Required: must be non-empty
the multi-hash which may be signed instead of each individual transaction
Required: must be non-empty