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.π Build your web extension with ever-sdk π
The last 1.37.0 ever-js-sdk has introduced 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}).
SDK docs: https://docs.everos.dev/ever-sdk/
ever-js-sdk: https://github.com/tonlabs/ever-sdk-js
The last 1.37.0 ever-js-sdk has introduced 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}).
SDK docs: https://docs.everos.dev/ever-sdk/
ever-js-sdk: https://github.com/tonlabs/ever-sdk-js
Release EverDev 1.3.0
New
- Added command
- Fixed
New
- Added command
everdev network credentials
, to set credentials for network authentication, with options:--project, -p Your project IDFixed
--access-key, -k Your secret or JWT token
--clear Clear saved credentials (mutually exclusive with other options)
- Fixed
everdev contract decode-tvc --help
output.ππEvercloud Authorizationππ
Starting from September 22st 2022, Evercloud API access will only be available for the authorized usersπ .
After enabling authorized-only access to Evercloud it turned out that some important project had not migrated yet.
This is why we decided to turn it off for 1 more week, until 22.09.22 (Thursday).
Follow this guide to get your credentials:
https://docs.everos.dev/evernode-platform/products/evercloud/get-started
Read why we introduce the authorization here:
https://everx.medium.com/authorization-and-dashboard-28c544953a2b
Your feedback about announcements
We also collected your feedback about announcement process and give you this 2 most important links:
- Deprecation schedule - save this page, and you wonβt need to monitor any announcements. All the breaking changes, deprecation and sunset dates and links to migration guides are placed there beforehand. Just check it from time to time. https://docs.everos.dev/evernode-platform/reference/breaking-changes/deprecation-schedule
- Subscribe to our announcements channel and be the first to know about our new features, improvements and deprecations https://t.me/ever_sdk_channel
Starting from September 22st 2022, Evercloud API access will only be available for the authorized users
After enabling authorized-only access to Evercloud it turned out that some important project had not migrated yet.
This is why we decided to turn it off for 1 more week, until 22.09.22 (Thursday).
Follow this guide to get your credentials:
https://docs.everos.dev/evernode-platform/products/evercloud/get-started
Read why we introduce the authorization here:
https://everx.medium.com/authorization-and-dashboard-28c544953a2b
Your feedback about announcements
We also collected your feedback about announcement process and give you this 2 most important links:
- Deprecation schedule - save this page, and you wonβt need to monitor any announcements. All the breaking changes, deprecation and sunset dates and links to migration guides are placed there beforehand. Just check it from time to time. https://docs.everos.dev/evernode-platform/reference/breaking-changes/deprecation-schedule
- Subscribe to our announcements channel and be the first to know about our new features, improvements and deprecations https://t.me/ever_sdk_channel
Please open Telegram to view this post
VIEW IN TELEGRAM
πͺToken API is available in Evercloud! πͺ
ft root type is API that provides data about fungible tokens, transfers, holders.
Try it now!
Read full documentation with samples here: https://docs.everos.dev/ever-sdk/reference/ever-os-api/ft-fungible-token-api
ft root type is API that provides data about fungible tokens, transfers, holders.
Try it now!
query{
ft{
holder(address:"0:3666ef0af863317eafcea173b9a9fdd6d1e4aa6dd080a1f472b2ad217215e5c9"){
address
wallets(first:2){
edges{
node{
address
balance
token{
symbol
}
percentage
}
cursor
}
}
transfers(first:1){
edges{
node{
messageId
token{
symbol
}
fromWallet{
address
}
toWallet{
address
}
fromHolder{
address
}
toHolder{
address
}
transferType
timestamp
value
}
cursor
}
}
}
}
}
Read full documentation with samples here: https://docs.everos.dev/ever-sdk/reference/ever-os-api/ft-fungible-token-api
Release SDK 1.38
New
π€ Debot module:
- ABI specification v2.3 is supported in DEngine.
- Supported flags
Improvement
- Support cookies πͺ in net module for std mode (not wasm)
- Remove network aliases (main, dev, main.ton.dev, net.ton.dev) π§Ή
- No balancing logic in case of 1 endpoint
- Removed the check of REMP support on backend during client initialization. π§Ή
These changes will make client initialization faster π CLI tools that use SDK will work faster, web pages will load initial data faster.
- Changed 401 error message to response message from API
- Tests improvements: cryptobox tests made stable
New
π€ Debot module:
- ABI specification v2.3 is supported in DEngine.
- Supported flags
OVERRIDE_TS, OVERRIDE_EXPT, ASYNC_CALL
for external messages in DEngine.Improvement
- Support cookies πͺ in net module for std mode (not wasm)
- Remove network aliases (main, dev, main.ton.dev, net.ton.dev) π§Ή
- No balancing logic in case of 1 endpoint
- Removed the check of REMP support on backend during client initialization. π§Ή
These changes will make client initialization faster π CLI tools that use SDK will work faster, web pages will load initial data faster.
- Changed 401 error message to response message from API
- Tests improvements: cryptobox tests made stable
Evercloud downtime episodes postmortem
There were 2 30-mins downtime episodes this week in Evercloud.
The reason of this was in a not efficient failover mechanism that didnβt work in case of hardware unavailability in Auth service cluster.
To eliminate this issue we have changed the failover mechanics and now we are able to survive 2 unavailable hosts.
Sorry for this inconvenienceβ€οΈ.
We are constantly working on improving the quality of our services.
There were 2 30-mins downtime episodes this week in Evercloud.
The reason of this was in a not efficient failover mechanism that didnβt work in case of hardware unavailability in Auth service cluster.
To eliminate this issue we have changed the failover mechanics and now we are able to survive 2 unavailable hosts.
Sorry for this inconvenienceβ€οΈ.
We are constantly working on improving the quality of our services.
Evercloud maintenance
Dear developers,
Today we will perform Evercloud maintenance from 13.00 to 14.00 CET.
During this period 1 minute disconnection episode may occur.
Your Evernode Platform teamπ§π
Dear developers,
Today we will perform Evercloud maintenance from 13.00 to 14.00 CET.
During this period 1 minute disconnection episode may occur.
Your Evernode Platform teamπ§π