Everscale SDK / Graphql API / Dev Tools

Release SDK 1.43

New

- network.network_retries_count config parameter is finally deprecated and not used in SDK.
max_reconnect_timeout is used instead
- Message monitoring errors received by subscription are returned from
processing.fetch_next_monitor_results function
- Message monitor buffers new messages for delayed start of the subscription. New subscription
starts when 1 second has passed since the last addition or when 5 seconds has passed since last sending
- Message monitor uses more than one subscription.
- Version of ton_types upped to 2.0.0
- Fixed code for changed dependencies api
- Removed logic related to client-server clock sync
- boc.encode_tvc and boc.decode_tvc are renamed to boc.encode_state_init
and boc.decode_state_init.
- boc.decode_tvc decodes TVC BOC according to the TVC spec.
- DeploySet.tvc supports new TVC file format (according to new TVC spec).
Old tvc files (with serialized state init) are also supported.
- DeploySet.state_init allows to specify serialized state init.
- DeploySet.code allows to construct state init from provided serialized code.
- DeploySet's fields tvc, state_init and code are mutually exclusive (so you should
provide value for one of these fields).
- ProcessingEvent::MessageExpired is sent to callback in case of retry in processing.process_message

Release Evernode-SE 0.38.0

New

- Added node time mode seq – sequential. In this mode node produces single block for
each transaction. All blocks have gen_utime equals to the gen_utime of the previous
block + 1 sec.
Use /se/seq-mode-on endpoint to turn the mode on.
Read more in SE live control (REST API) section
- New forward fee config from Everscale mainnet.

Improved

- Internal structure was simplified.
- TonNodeEngine was isolated from API services.
- Added MemDocumentsDb – to use TonNodeEngine without ArangoDB but with access to produced parsed artefacts.
- Added ShardStorage based on the single and simple KVStorage as a shardstate internal storage instead of four independent storages.
- Added MemStorage and FSStorage as two main shard storage implementations.
- Added TonEngine.time with responsibility for a block time management.
- TonNodeEngine can be used as an in-memory blockchain emulator. It is useful for example for smart contract testing.

Release SDK 1.42.0

New

- Added message monitoring functions to the processing module: monitor_messages,
fetch_next_monitor_results, get_monitor_info, cancel_monitor****.
- Added processing.send_messages function.
- Improved error resolving for deleted accounts
- net.first_remp_status_timeout config parameter default value set to 1 ms in order to start
fallback scenario together with REMP statuses processing while REMP is not properly tuned yet.
- Network errors are returned on subscription creation if occured

Fixed

- ParamsOfSubscribe was not public.
- subscribe did not trim subscription query text. It is required for some graphql servers
expecting that query text starts from operation text.

Release evernode-se 0.37.0

New

- Produces masterchain block for each workchain block.
- Added ability to update blockchain config with node restart (without killing the database). After changing the config stop and start the node to apply it. It will produce new key block from the new config.
- CapSignatureWithId capability is supported: global_id parameter is used as a signature_id if CapSignatureWithId cap is turned
on in the blockchain config.

Fixed
- global_id parameter in ton-node.conf.json is written into blocks.

New

- 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.signatureid -> ClientConfig.network.signatureid -> 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.

Client breaking changes
- abi.get_signature_data function ouput parameter hash is renamed to unsigned for consistency with other crypto functions parameters

Possible breaking change on binding side
- Changed type of the dictionary parameter or mnemonic crypto functions and crypto config. Now it uses MnemonicDictionary enum type instead of number. MnemonicDictionary numeric constants are compatible with previous values.

Deprecated
- debot engine module is deprecated. Debot engine development has migrated to a separate repository (soon will be published). So, in order to reduce sdk binary size, we will remove debot engine module from sdk in the next releases.

Dear Evercloud users,

List of public endpoints was updated.
Everscale Test Network (aka FLD) endpoints are added.

If you are interested in testing new network features 🌚 - Test FLD Network gives you this opportuity 🛠

https://docs.evercloud.dev/products/evercloud/networks-endpoints

Release SDK 1.40.0

New

- abi.get_signature_data function that returns signature from message and hash to verify the signature

Improvement

- local endpoints with port specified are expanded with http protocol instead of https (e.g.
localhost:8033 in expanded to http://localhost:8033/graphql)