-
CapSignatureWithId
capability is supported.
Network signature ID is used by VM in signature verifying instructions if capability
CapSignatureWithId
is enabled in blockchain configuration parameters.
This parameter should be set to global_id
field from any blockchain block if network can
not be reached at the moment of message encoding and the message is aimed to be sent into
network with CapSignatureWithId
enabled. Otherwise signature ID is detected automatically
inside message encoding functions.
Overwrite priority: ExecutionOptions.signature_id -> ClientConfig.network.signature_id -> last network block
ClientConfig.network.signature_id
optional parameter is added. Specify it in case of offline work for all message signing operations to use.ExecutionOptions
is extended with signature_id
optional parameter. Specify locally for a particular run_tvm
or run_executor
call.net.get_signature_id
function returns global_id
if CapSignatureWithId
capability is enabled,
-
message_id
and message_dst
fields are added to all ProcessingEvent
variants
-
Config parameter binding: { library: string, version: string }
. Binding authors should define
this parameter at context initialization.
-
tonclient-binding-library
and tonclient-binding-version
GraphQL request headers.
-
Error.data.binding_library
and Error.data.binding_version
error data fields.
-
specifying binding info in core initialization.