Attention to all DEVNET Validators and Dapp Server owners!
Devnet is going through an update that will lead to a breaking change in account format which may cause your nodes to stop working.
The network is already updated, the switch of the format will happen very soon.
You need to update your Devnet validators and Dapp Servers to the latest version now.
https://github.com/tonlabs/evernode-ds/releases/tag/0.1.5
Devnet is going through an update that will lead to a breaking change in account format which may cause your nodes to stop working.
The network is already updated, the switch of the format will happen very soon.
You need to update your Devnet validators and Dapp Servers to the latest version now.
https://github.com/tonlabs/evernode-ds/releases/tag/0.1.5
Attention to all DApp developers!
DevNet has been updated to support new account structure that now has
This feature has been a breaking change for tvm and transaction executor. So, not to cause breaking of all your applications we now temporarily support each account in 2 formats: old and new. Starting from SDK 1.31 new version of boc is downloaded.
Support of 2 boc versions is temporary. You need to migrate your applications on DevNet to the new SDK 1.31 version asap.
When the sunset period is over, API will start returning the new boc version only for all client versions. The sunset period is not defined yet, we will keep you informed.
Watch for deprecation scedule.
Read more in deprecation guides.
DevNet has been updated to support new account structure that now has
init_code_hash
field. You can check it in playgrounds. This feature has also been added to Evernode SE and DS. This feature has been a breaking change for tvm and transaction executor. So, not to cause breaking of all your applications we now temporarily support each account in 2 formats: old and new. Starting from SDK 1.31 new version of boc is downloaded.
Support of 2 boc versions is temporary. You need to migrate your applications on DevNet to the new SDK 1.31 version asap.
When the sunset period is over, API will start returning the new boc version only for all client versions. The sunset period is not defined yet, we will keep you informed.
Watch for deprecation scedule.
Read more in deprecation guides.
Release SDK 1.32
New
-
-
-
way when the application sends many GraphQL requests in parallel.
Fixed
- Debot module:
- If
New
-
network.queries_protocol
config parameter allows selecting protocol the SDK uses to communicate with GraphQL endpoint:-
HTTP
โ SDK performs single HTTP-request for each request.-
WS
โ SDK uses single WebSocket connection to send all requests. This protocol is a preferableway when the application sends many GraphQL requests in parallel.
Fixed
- Debot module:
- If
DEngine
received a non-zero exit_code
while emulating a transaction while sending a message, DEngine
will call onErrorId
callback of the message.๐ข Dear Developers and Partners!
We are ready to enable new TVM instructions in Everscale Main Net.
โผ๏ธThis update will lead to a BREAKING CHANGE in account format which may cause your nodes to stop working. โผ๏ธ
To avoid such problems - you need to UPDATE your DApp Servers and Validator Nodes to the latest version:
โ DApp server โฅ0.1.5 version - https://github.com/tonlabs/evernode-ds/releases
โ Validator Node - latest master commit https://github.com/tonlabs/ton-labs-node
At the moment we support both Account format versions in Public API and in DApp Server API so that applications can smoothly migrate to the new account version. To do it just update SDK to the latest version (โฅ1.31.0). If you work with API directly, enable the new http header. We encourage you to do it ASAP because we will support both account formats temporarily.
๐Docs:
New TVM instructions (extension)
Developer migration guide
TON-SDK release with new Account Format
How to use new TVM features in Solidity: tvm.code, tvm.initCodeHash
More about protocol changes in EverX Node
We are ready to enable new TVM instructions in Everscale Main Net.
โผ๏ธThis update will lead to a BREAKING CHANGE in account format which may cause your nodes to stop working. โผ๏ธ
To avoid such problems - you need to UPDATE your DApp Servers and Validator Nodes to the latest version:
โ DApp server โฅ0.1.5 version - https://github.com/tonlabs/evernode-ds/releases
โ Validator Node - latest master commit https://github.com/tonlabs/ton-labs-node
At the moment we support both Account format versions in Public API and in DApp Server API so that applications can smoothly migrate to the new account version. To do it just update SDK to the latest version (โฅ1.31.0). If you work with API directly, enable the new http header. We encourage you to do it ASAP because we will support both account formats temporarily.
๐Docs:
New TVM instructions (extension)
Developer migration guide
TON-SDK release with new Account Format
How to use new TVM features in Solidity: tvm.code, tvm.initCodeHash
More about protocol changes in EverX Node
๐ข Attention to all Everscale developers!
โผ๏ธThis is a scheduled friendly reminder that net*.ton.dev and main*.ton.dev endpoints will be switched off on 16th of May. Please migrate your application to the new endpoints. โผ๏ธ
Deprecation schedule:
https://tonlabs.gitbook.io/evernode-platform/reference/breaking-changes/deprecation-schedule
You can find the actual list of public endpoints in the documentation
https://tonlabs.gitbook.io/evernode-platform/products/cloud/public-api
โผ๏ธThis is a scheduled friendly reminder that net*.ton.dev and main*.ton.dev endpoints will be switched off on 16th of May. Please migrate your application to the new endpoints. โผ๏ธ
Deprecation schedule:
https://tonlabs.gitbook.io/evernode-platform/reference/breaking-changes/deprecation-schedule
You can find the actual list of public endpoints in the documentation
https://tonlabs.gitbook.io/evernode-platform/products/cloud/public-api
๐ข Attention to all Everscale developers!
๐ ๐ ๐ This is a friendly reminder about coming feature sunsets in Evernode Public API. ๐ ๐ ๐
These features will be switched off on 1st of June - 40 days left.
Take time to migrate your applications to the new features following the migration guides.
June 1 2022 API Sunset list:
-
-
-
-
- all
See the deprecation schedule for migration guides and other sunset dates!
https://tonlabs.gitbook.io/evernode-platform/reference/breaking-changes/deprecation-schedule
๐ ๐ ๐ This is a friendly reminder about coming feature sunsets in Evernode Public API. ๐ ๐ ๐
These features will be switched off on 1st of June - 40 days left.
Take time to migrate your applications to the new features following the migration guides.
June 1 2022 API Sunset list:
-
getAccountsTotalBalance
-
getTransactionsCount
-
getAccountsCount
-
when
argument in all joined fields (for example, `transaction.in_message`'s when argument)- all
explain*
methodsSee the deprecation schedule for migration guides and other sunset dates!
https://tonlabs.gitbook.io/evernode-platform/reference/breaking-changes/deprecation-schedule
Release SDK 1.33
New
-
-
- UNSTABLE.
New
-
allow_partial
flag in all abi.decode_*
functions. This flag controls decoder behavior whether return error or not in case of incomplete BOC decoding-
REMP
supported. ProcessingEvent
enum is extended with REMP
statuses (enum of events posted into processing.wait_for_transaction
function callback )- UNSTABLE.
first_remp_status_timeout
and next_remp_status_timeout
parameters in network config๐ Subscriptions backend redesigned ๐
Many of you reported us feedback about poor websocket subscriptions quality: frequent websocket reconnections, missed data, stalling and so on.
We invested significant amount of time in the complete redesign of the subscriptions backend and deployed it to production 2 weeks ago. Some of our clients have already made tests on their side and confirmed that no reconnects and no data loses occur any more.
You don't need to migrate to the new subscriptions. If you are using subscriptions now, they already work on the new backend!
If you used 'pull' approach because of subscriptions unreliability,
now you can switch to websockets and become more real-time and responsive to your users.
Thank you for your feedback and we are happy to hear more of it to improve and give you better service. โค๏ธ
https://docs.everos.dev/evernode-platform/products/cloud/public-api
Many of you reported us feedback about poor websocket subscriptions quality: frequent websocket reconnections, missed data, stalling and so on.
We invested significant amount of time in the complete redesign of the subscriptions backend and deployed it to production 2 weeks ago. Some of our clients have already made tests on their side and confirmed that no reconnects and no data loses occur any more.
You don't need to migrate to the new subscriptions. If you are using subscriptions now, they already work on the new backend!
If you used 'pull' approach because of subscriptions unreliability,
now you can switch to websockets and become more real-time and responsive to your users.
Thank you for your feedback and we are happy to hear more of it to improve and give you better service. โค๏ธ
https://docs.everos.dev/evernode-platform/products/cloud/public-api
Release SDK 1.34
New
-
-
-
-
-
-
then core creates more than one internal context per single TonClient
instance. As a side effect of this is that a Nodejs process didn't
finish even when
Improved
- Added documentation for TransactionFees type.
- Documentation now includes enum types descriptions.
To achieve it we updated
New
-
client.config
function that returns the current client config-
run_executor().fees
is extended with detailed fields-
main
and dev
endpoints aliases for Evernode Cloud Mainnet and Devnet endpoints-
binding-gen
: enum of types produces its own type for each enum variant.-
lib-web
: large numbers in transaction fees are rounded now (previously they caused errors).-
core
: if an application calls first client core functions in parallelthen core creates more than one internal context per single TonClient
instance. As a side effect of this is that a Nodejs process didn't
finish even when
client.close
was called.Improved
- Added documentation for TransactionFees type.
- Documentation now includes enum types descriptions.
To achieve it we updated
binding-gen
: enum of types now produces its own type for each enum variant.Channel name was changed to ยซEverscale DEV Tools / SDK / APIยป
Deleted accounts available in Evernode Public API
Many of you requested us to see the deleted accounts in Cloud public API.
We added this feature and also processed all the transaction history to recover old deleted accounts.
All the deleted accounts are now available in API and https://ever.live/
Thank you for your feedback and if you have any please leave it in channels or Everscale telegram channel
Many of you requested us to see the deleted accounts in Cloud public API.
We added this feature and also processed all the transaction history to recover old deleted accounts.
All the deleted accounts are now available in API and https://ever.live/
Thank you for your feedback and if you have any please leave it in channels or Everscale telegram channel
Release everdev 1.2.0
New
- Add new option
If you compiled your own giver,
You can specify which interface your giver implements by specifying the
- Add new sub command
Improved
- For
New
- Add new option
--type
to the everdev network giver
command.If you compiled your own giver,
everdev
may refuse to use it because it doesn't know what interface it implements.You can specify which interface your giver implements by specifying the
--type = GiverV1 | GiverV2 | GiverV3 | SecureMultiSigWallet | SetcodeMultisigWallet
- Add new sub command everdev contract decode-data file [options]
. This command decodes data from a contract deployed on the network.- Add new sub command
everdev contract decode-tvc file
. This command decodes TVC into code, data, libraries and special options.Improved
- For
everdev sol compile
and everdev clang compile
commands, you can specify a variable number of input files, for example:$ everdev sol compile Contract1.sol Contract2.sol Contract3.sol # It works
$ everdev sol compile *.sol # It works too
Release evernode-se 0.31.0
New
-
-
-
- PoA consensus was removed from source code.
- Source code drastically simplified and reorganized.
- Randomization added for block generation
- Extra thread creation was removed
- Tokio crate dependencies were removed
- Extra crate dependencies were removed
Fixed
-
New
-
log_path
config field for configuring node log file location.-
/se
REST endpoint for SE realtime control.-
/se/increase-time?delta=<seconds>
feature to move time forward.- PoA consensus was removed from source code.
- Source code drastically simplified and reorganized.
- Randomization added for block generation
- Extra thread creation was removed
- Tokio crate dependencies were removed
- Extra crate dependencies were removed
Fixed
-
tvm.random()
now generates random valuesCommunity-driven development ๐ฌ
Dear Everscale developers and Evernode Platform users,
we have a big announcement for you today!
For over two years the Evernode Platform team has been developing its products based on the requirements of the ecosystem and the wishes of the the community.
Up until now the community feedback was collected in Telegram channels and personal conversations with developers. The Evernode Platform roadmap was published on our website in January 2022.
Now we want to bring our communication with the community to the next level.
We changed the structure of our website to better reflect community-driven approach and turned the roadmap into a more convenient kanban board.
We also added a way to submit your ideas, vote for and comment on the ideas of others.
Links to the roadmap and the ideas page are now in the header of the website.
Our website: https://docs.everos.dev/evernode-platform/
Thank you for choosing Evernode Platform.
Let's make it together
Dear Everscale developers and Evernode Platform users,
we have a big announcement for you today!
For over two years the Evernode Platform team has been developing its products based on the requirements of the ecosystem and the wishes of the the community.
Up until now the community feedback was collected in Telegram channels and personal conversations with developers. The Evernode Platform roadmap was published on our website in January 2022.
Now we want to bring our communication with the community to the next level.
We changed the structure of our website to better reflect community-driven approach and turned the roadmap into a more convenient kanban board.
We also added a way to submit your ideas, vote for and comment on the ideas of others.
Links to the roadmap and the ideas page are now in the header of the website.
Our website: https://docs.everos.dev/evernode-platform/
Thank you for choosing Evernode Platform.
Let's make it together
Release SDK 1.36.0
New
- ABI specification v2.3 is supported
- parameter
New
- ABI specification v2.3 is supported
- parameter
address
is added to abi.encode_message_body
functionRelease Evernode-DApp-Server 0.1.8
New
- support
Improvements
- updated ton-q-server from 0.48.1 to 0.52.1
- updated ton-labs-node from
- changed arangodb-messages-sink configuration to update messages instead of replacing
- added 20 new indexes to arangodb
Fixed
- fixed
New
- support
query { blockchain { .. } }
GraphQL API queries in Evernode DApp ServerImprovements
- updated ton-q-server from 0.48.1 to 0.52.1
- updated ton-labs-node from
49a724639a175752f44bcda65d907f2ca3ad97aa
to 5438eaab4db17c0c78869debf3e936078d9d7150
- updated kafka-connect-arangodb to custom solution with additional overwritemode
parameter- changed arangodb-messages-sink configuration to update messages instead of replacing
- added 20 new indexes to arangodb
Fixed
- fixed
master.shard_hashes.shard
in master blocks in one-shard scenario (only v0.1.7 was affected)โค๏ธ Dear Evercloud users and Everscale developers,โค๏ธ
โ ๏ธ This is an important announcement.โ ๏ธ
Starting from September 1st 2022, Evercloud API access will only be available for the authorized users.
Read more here -->> https://tonlabs.notion.site/Authorization-and-dashboard-5ff7ad94999a49ec9cfaeedf34285146
โ ๏ธ This is an important announcement.โ ๏ธ
Starting from September 1st 2022, Evercloud API access will only be available for the authorized users.
Read more here -->> https://tonlabs.notion.site/Authorization-and-dashboard-5ff7ad94999a49ec9cfaeedf34285146
Release SDK 1.37
New
- client sends
- client accepts endpoints with
-
So main thread never freezes โ it is fine for UI. But in some cases (e.g. when worker already exists in application or extension)
separate worker is a bad approach. In this case application can suppress this with
Fixed
- Updated `
New
- client sends
config.network.access_key
as Authorization: Basic ...
or Authorization: Bearer ...
header. - client accepts endpoints with
/graphql
suffixes specified in config.-
lib-web
option disableSeparateWorker
. By default, lib web starts a separate worker that will utilize core (wasm). So main thread never freezes โ it is fine for UI. But in some cases (e.g. when worker already exists in application or extension)
separate worker is a bad approach. In this case application can suppress this with
libWebSetup({disableSeparateWorker: true})
.Fixed
- Updated `
zstd
` in order to fix building.