Greetings, dear EverX Community!

It’s been a while since we last connected, but rest assured, we’ve been busy, tirelessly working to bring you exciting updates and developments from our SDK team. So, let’s dive in!

SDK Updates

• messageMonitor and send_messages functions added to ever-sdk 1.43.0. Now you can process up to 200 external messages per second from 1 client. Available in Evercloud in Mainnet and Devnet;
• New tvc format was supported in ever-sdk 1.43.0 version;
• encode_tvc and decode_tvc functions were renamed to encode_state_init and decode_state_init, so that namings are reflecting the actual data formats. TVC or TON Virtual machine Code represents the actual contract code with metadata about the contract itself and toolchain used to compile it;
• deploy_set structure now supports old tvc format, new tvc format as well as state_init and code, i.e. you can deploy contracts if you have only code on your hands;
• @eversdk TON JS library with native support of Cells and use-cases covering TON network working on top of GraphQL API has been released https://github.com/tonlabs/eversdk-ton;
• Evernode-SE now supports sequential mode where 1 block is generated for 1 transaction and time delta between blocks is 1 second which allows to test time-sensitive contract systems https://github.com/tonlabs/evernode-se#se-live-control-rest-api.

EverCloud

• Venom devnet network is supported;
• TON testnet network is supported;
• Total refactoring of Evernode Dapp Server has been done, 1.0.0 version is released. https://github.com/tonlabs/evernode-ds.

⌨️ Don’t forget, that you can ask team any question here!

Keep yourself updated by staying tuned with us and following us on social media! 🔥

Twitter

LinkedIn

Telegram

❤ We appreciate your attention!

🤝 Interested in joining a brilliant team of talented developers? Check out our open positions here.

Greetings, dear EverX community!

We are excited to present our latest developments and share them with you below.

Flex DEX

In March, the Flex team focused on the following tasks:

Completed and released the first version of the Flex Web UI for public beta testing.

• Available at stage.flexdex.fi
• Production release is expected in April, along with further improvements to the Surf Keeper extension (trusted dapp)

Continued testing the new DEX contracts in Devnet in preparation for the DEX upgrade in Mainnet.

• Optimized price contracts for order capacity
• Optimized Flex wallets with new replay protection and increased queue capacity (rolling id)

Began developing a new contract specifically for Market Makers, which will allow for optimized work with liquidity in the order book.

💬 Join the group chat on all things Flex DEX here.

Node team

EverX node has released performance improvements for operating with large shard states in local databases, which is especially necessary for high load scenarios.

The testing of REMP protocol functionality and performance is ongoing, along with the implementation of additional improvements for protocol stability. In the development network, the REMP feature was switched on in mid-March.

Additionally, a new feature for estimating the required fees amount on sequences of linked smart contract calls has been released. It allows for the nomination of all fees in gas units (with respect to the current gas price) and greatly simplifies the process of fee estimation for smart contract developers.

EverCloud

• Venom testnet was supported in Evercloud (but it is not yet present in the dashboard, only in docs)
• REMP was enabled in Devnet, rempReceipts subscription is available.

Read these guides how to use remp receipts in your DApps:

https://docs.everscale.network/develop/tutorial/ever-sdk-quides/remp

https://docs.everscale.network/develop/tutorial/graphql-api-guides/remp

• FT API updates:

Ability to filter tokens by token creator added;

Even tokens with 0 total supply and tokens that have no transfers can now be queried;

Holder tokens now can be filtered by an array of token addresses.

• New accounts collection search abilities:

Added indexes by {init_code_hash, id}, {prev_code_hash,id} for accounts. Now you can search and paginate accounts by init_code_hash and prev_code_hash.

• New release of Evercloud dashboard includes new features as:

FLD network, which allows testing early network protocol updates, is available in Evercloud dashboard. No authorization yet;

Free token faucets were added to Evercloud dashboard. Now you can request tokens in Devnet and FLD networks;

Password reset functionality added;

getting started panel added;

GraphQL icons are small and colourful to attract attention.

Also, the team is finishing the account and project analytics ATM.

⌨️ If you have a question ask the team right here.

Toolchain

Proud to announce a new release of the Everscale Solidity Compiler, dubbed “0.67”. The compiler is a cornerstone of the smart-contract development for the Everscale blockchain ecosystem, effectively enabling utilization of benefits of the de-facto industry standard, high-level programming Solidity language, thus unlocking an enormous potential of the platform. Keeping the compiler source code base up-to-date with the cutting edge is a non-trivial task. Fortunately, the new release closes the gap between state-of-the-art and Everscale implementations.

A couple of changes are required to compile the source code with the new version (refer to https://github.com/tonlabs/TON-Solidity-Compiler/blob/master/Changelog_TON.md for details). The good news is that the code generated is conforming to ABI v2.3, making it binary compatible with the already deployed contracts compiled with the previous version of the compiler.

For an exhaustive list of the changes and improvements, please refer to https://github.com/ethereum/solidity/blob/develop/Changelog.md, 0.6.3 to 0.8.17.

Quality of the release has been thoroughly verified on a subset of 300+ distinct smart-contracts, with a result of 0 outstanding issues found. If you are interested in a pre-compiled binary, or in a complete developer tools package, check out https://github.com/tonlabs/TON-Solidity-Compiler/releases/tag/0.67.0.

That’s all for this month’s update from the EverX development squad, folks! If you want to stay in the loop on all things EverX, make sure to follow us on social media!

Twitter

LinkedIn

Telegram

✅ Thank you for your continued support!

🤝 Interested in joining a brilliant team of talented developers? Check out our open positions here.

Hello, beloved community of EverX!

As the last month of winter drew to a close, our team put in a tremendous amount of effort and dedication towards work process. We are thrilled to announce our latest updates and share them with you below.

Node team

The following are 3 updates from the Node team:

• The EverX node released the source code containing support for the REMP protocol. However, the protocol itself is not yet enabled on the main network, as the implementation is under conducting testing and implementing performance improvements. Nonetheless, the source code is publicly available for investigation.
• The Node team has conducted a comprehensive refactoring of operations related to data cells in our local node database. This has been done to significantly improve performance on high load scenarios. This update is set to be released in March.
• Source codes for solidity-based elector were published. This is a pre-release currently, and is going to be finalized soon after evaluation experiment on devnet.

Flex DEX

The Flex team is constantly striving to enhance their product, and as such, they have provided the following digest of their latest updates:

Throughout February, the Flex team dedicated themselves to enhancing the web version of Flex DEX. The focus was on establishing a stable connection with the Surf extension and optimizing the overall user interface and experience.

Several flows were initiated during February and are expected to be finalized in March.

• These include the implementation of the “delete user” and “recover gas” flows, as well as onboarding processes that involve wallet selection and installment.

The Flex team’s primary focus with regards to the DEX contracts was to optimize gas consumption before the DEX upgrade. The team worked tirelessly to ensure that this aspect was thoroughly addressed.

💬 Join the group chat on all things Flex DEX here.

SDK

A brief squeeze of news from sdk:

• Solc and Sold binaries available in everdev has been rebuilt from public tags. Before, there were some old version binaries, built from private repositories, which caused problems for contract verification. Also, warning messages were added to everdev solc version, everdev sold version commands, recommending to see the list of stable solidity versions in repository changelog (not all Solidity versions are stable).
• debot module was deprecated in ever-sdk client libraries. It will be removed in the next library releases
• CapSignatureWithId capability is supported in ever-sdk 1.41.0 and everdev 1.6.0. Read more here https://github.com/tonlabs/ever-sdk/blob/master/CHANGELOG.md#1410--2023-02-13
• Ability to change network config without dropping the database is added to Evernode-SE. Simply update the config and then restart the container.
• The list of givers was refactored. New GiverV3 was published in SE repository https://github.com/tonlabs/evernode-se/tree/master/contracts and supported in everdev 1.6.0

EverCloud

What’s new?

UNSTABLE MessageMonitor API — released only in devnet now

• recentExtInMessageStatuses query — returns processing statuses (finalized/timeout/undefined) for external messages sent not earlier than 1 hour ago
• recentExtInMessageStatuses subscription — returns processing statuses for messages (same as in query)+ and subscribes for events about processed messages until all messages final statuses (finalized/timeout) are received.

Deprecations/Breaking changes

• timeout parameter of query {blocks, accounts, transactions, messages} max value will be set to 40 seconds starting from 1st of April. Use subscriptions if you need longer waiting period https://docs.evercloud.dev/reference/breaking-changes/deprecation-schedule

Improvements

• Evercloud changelog has been updated and will be up-to-date since now https://docs.evercloud.dev/reference/changelog/evercloud

⌨️ If you have a question ask the team right here.

With that, we come to the end of this month’s update from the EverX development team. Our team is committed to continuously bringing you the latest and greatest advancements, and we encourage you to stay tuned for more exciting updates in the future. To stay informed and up-to-date with all things related to EverX, please follow our social media accounts.

Twitter

LinkedIn

Telegram

✅ Thank you for your continued support!

🤝 Interested in joining a brilliant team of talented developers? Check out our open positions here.

Greetings dear EverX community!

It has been quite some time since we last reached out to you. With the holidays now behind us and the crisp chill of winter giving way to new beginnings, our dedicated team has been working tirelessly to bring you some significant news and updates. So without further ado, let’s dive into what’s been happening.

Flex DEX

In December Flex launched trading activities with professional market making and liquidity in the Orderbook

• Currently it has 5 pairs of major coins and stablecoins with EVER and is looking to find the most promising usecases;
• Liquidity in all traded pairs follow the oracle prices from several exchanges.

There was an AMA session of the Flex busdev team and tech team at the end of December where the team answered questions from the community about the project, its status and their further plans.

If you missed the AMA session, please check it out here: https://youtu.be/LBbkTq4_dzA

In Jan the main focus of the team is on the web version of the Flex Dapp:

• It includes refactoring of Auth and Deposit/Withdraw user flow with wallet extension;
• This refactoring will be partially applicable to the desktop app as well to improve and unify the overall UI;
• In Feb we’ll complete refactoring of the remaining flows in the web version (recover gas flow, contracts update flow, etc.)

Also the Flex team works on optimization of the existing DEX contracts in terms of capacity and gas consumption. Plans are to make migration to the new DEX contracts later in Feb.

💬 Join the group chat on all things Flex DEX here.

NODE

There are several updates from the NODE team:

In January, the EverX node December 2022 release underwent testing on the community network before being rolled out to the main EverX network.

The EverX devnet was then updated to reflect these changes. The latest release addressed various bugs and issues identified by the community.
A substantial improvement in the performance of the Node’s local database has been also made. 🤓

EverPlatform

We hope you have been eagerly awaiting these updates from the team. Here they are!

The SE now supports the “CapBounceMsgBody” and “CapFullBodyInBounced” capabilities.The SE Explorer has also undergone an update, adding new features and improvements.

Additionally, the abi.getMessageSignatureData function has been introduced to make ABI signature verification easier and more streamlined.

EverCloud

The EverCloud team has been hard at work and has brought some substantial updates to the table.

• Flex API add-on has been added! 🤩 Now, anyone can integrate with Flex Dex! https://docs.evercloud.dev/reference/evercloud-api-add-ons/flex-api
• Price API was added to Evercloud. Now you can get Ever price, market cap and 24h volume.

• TON beta endpoint has been added to the list of supported networks. Want to integrate with TON? Now it is possible with the same Everscale dev tools. https://docs.evercloud.dev/products/evercloud/networks-endpoints
• FLD Network (where new blockchain features are tested) endpoints have been added to the list of supported networks. If you want to test new protocol updates — welcome to FLD! https://docs.evercloud.dev/products/evercloud/networks-endpoints
• We released the first beta version of cost API which performs static query cost calculation based on used queries and requested data. Cost calculations are still in the process of tuning and will change before billing introduction. But the API is already available.

Result:

The EverCloud team continues working on project analytics and user segmentation for future billing plans and to provide EverCloud users with API usage logs and stats.

Also the team continues working on a new message processing API for multiple simultaneous messages processing on backend.

⌨️ If you have a question ask the team right here.

And that concludes this month’s digest of updates from the EverX development team. We are always working to bring you the latest and greatest advancements, so be sure to stay tuned for more exciting updates in the future. To stay informed and up to date with all EverX things, be sure to follow our social media accounts and stay connected with our community.

Twitter

LinkedIn

Telegram

✅ Thank you for your continued support!

🤝 Interested in joining a brilliant team of talented developers? Check out our open positions here.

It may be getting chillier outside as the market doubles down, but while we’re waiting for that bear to enter hibernation, we’ve assembled some updates that will keep you feeling warm and fuzzy inside. We strive to be informative and to provide transparency regarding our team’s activities each month, and for them to be shared publicly to the Everscale ecosystem and our investor network.

From the Flex DEX to EverLive and many updates from EverPlatform–we’ve picked the top news that defined the past few weeks here at EverX. So go grab that last slice of pumpkin pie and dive into our highlights for the month of November 2022.

Flex DEX

The FLEX team recently listed three additional pairs on the platform for traders, which tallies six in total on the current list of traded pairs, being:

• WBTC/EVER
• WETH/EVER
• EVER/USDT
• EVER/USDC
• EVER/DAI
• USDC/USDT

✅ In the Flex GUI the team added an option to make Market orders in addition to Limit orders:

✅ Also a new feature is an option to set custom trader keys (useful for developers who work with Flex SDK):

After extensive and rigorous testing with the market makers of the Flex SDK library and Flex API, it has finally been updated to include additional methods as well as replacing float numbers with decimal numbers for greater accuracy.

Additional updates include the team having continued to make improvements under the hood both in GUI and DeBots while also continuing to work on the Flex Tokenomics contracts.

💬 Join the group chat on all things Flex DEX here.

LIVE

This month the team added a few new features and improvements to LIVE thanks to the Token API 2.0, which was released by the EverPlatform team. The features include:

• Filter by token name in the catalog of TIP-3.2 tokens
• Statistics for the number of TIP-3.2 tokens
• Statistics for the number of holders for a particular token
• Optimized display of long lists of tokens in account details

They’ve also made a refactoring of explorer’s navigation to React Router as well as other fixes and optimizations

NODE

REMP protocol testing and optimization is in progress. 🎉

A couple of redesign decisions were implemented to improve performance and efficiency: three rounds of implementation and testing were passed on both internal environment and the community network. The following round is slated to start ASAP.

The Node team has also completed other various updates such as:

• Deployment of SMFT (new consensus) implementation was started on a dedicated community network.
• Formal verification process for Solidity elector and config smart contracts was initiated.
• EverX Devnet has been restored after an incident of one shards stopping on November 17th due to a mistake which occurred in the state of one smart contract from approximately one year ago. A dedicated patch was applied to all validator nodes to clean up the broken contract state.

EverPlatform

A fair amount of optimizations are currently being made in SDK/API which will be included in version 1.39.0. SDK and will perform less requests, the websocket protocol will support retries, and plenty of bugs will be fixed.

The GOSH team has been helping the EverPlatform team test multiple message processing use-cases, which revealed the problems stated previously. These optimizations along with a new API (see below) is essential when REMP is enabled.

• Multiple message processing API is being designed. The current design causes high infrastructure load on the backend when there is a case of many parallel messages processing.
• Gosh has been experiencing problems with the current message processing mechanisms due to many parallel message processings taking place simultaneously.
• Once Flex migrates to the new replay protection it will also face this problem–because the throughput of messages will be higher.
• After REMP is enabled, it will automatically allow anyone to send multiple parallel messages to many contracts, which will cause the infrastructure to bottleneck.
• The team has decided to move the processing mechanisms to the backend which will drastically improve the infrastructure throughput.

Flex support

The EverPlatform team has also implemented a lot of new features, improvements and fixes on the Flex SDK/API side. They’ve improved makeOrder/cancelOrder functionality by adding a light-weight framework behavior, so that users can understand the order processing status and result. They’ve also removed Float type from API completely, so that they do not have problems with roundings.

A Top Up mechanism and getters for Flex balance and User Index info were also added to the SDK.

Evercloud

The Flex API is currently being added to Evercloud. Throughout the month working with their integrating partners, the team created an extensive Flex integration guide for all users, so stay tuned for further announcements!

✅ That’s it for this month’s digest. Stay tuned for more updates from the dev team at EverX! Be sure to follow our accounts to stay up to date:

Twitter

LinkedIn

Telegram

🤝 Interested in joining a brilliant team of talented developers? Check out our open positions here.

Dear EverX community,

From the FLEX DEX to the Evercloud API and improved REMP performance–we’ve got your pumpkin spiced updates that defined our October here at EverX! 🎃

FLEX

The Flex DEX team–the folks behind one of the most anticipated projects on Everscale–never stops developing. Over the past month, the Flex team worked on improving and optimizing the DEX contracts, for example, added support of ABI 2.3 in C++ compiler and in the contracts.

The team also completed development of new Flex token wallets with rolling ID replay protection. Further updates include:

• Successfully performed stress tests;
• Now supported in Dengine and SDK.

They’ve also continued to work on new high capacity price contracts with optimized data structures as well as migrations of the production DEX contracts:

• Performed the first migration in the Flex history concerned the renewal of the userDataConfig contract;
• Redeployed the DEX contracts to support ABI 2.3 before public launch;
• Next migration planned at a later date will include: (1) high capacity price contracts; and (2) flex token wallets with rolling id replay protection.

Based on user feedback (thanks, community!), the team also rolled out a new logo and updated the website as well as the Flex GUI app. Other small improvements include squashing bugs🪲 and error handling.

Now for the juicy part: the public launch of Flex is expected in the coming weeks 🎉 and exact date depends on the integration of the Market Makers with the DEX.

⚡Join the Flex DEX Beta group and jump into the conversation https://t.me/flexdexbeta

Live

This month, the Live team was focused on the transition to the Evercloud Token API. The most important improvement in the explorer was the replacement of the data source for tokens from the cache to the Evercloud Token API. As a result, users get instant access to information on their tokens in real time. Currently, the Token API only supports the TIP-3.2 standard, which means older standards are no longer supported in the explorer–with the exception of KWT tokens.

All available information in the Token API will be added to the explorer including token catalog, token details, token balances and token transfers. There will also be search of tokens by symbol or name in the search bar, token filters and stats.

Important work has been done so that the explorer can be deployed on custom dapp servers without access to Firebase. Fallback functions have been added in many places in the code so that the application can continue to work without normal database access.

The Live team is also continuing to work on rewriting application components in React and fixing bugs.

Ever Platform (formerly Evernode Platform)

Update: The Evernode Platform’s name has been shortened to “Ever Platform”.

The team behind the Ever Platform reported that the Token API is in production with functionality such as: getting the token list, transfers and balances from GraphQL API. Here you can check the documentation.

After authorization was enabled we received feedback about developers’ desire to have the ability to explore the API before registration. We love our users, so we have delivered a demo-devnet endpoint with no authorization. The tradeoffs are: you can not use it in production because it provides no SLA, and request rate limits are pretty low. But it’s just enough to experience and study the ecosystem.

Further updates include the ability to check the network capabilities in a human-readable form: capabilities_flags field was added to config.p8 in the GraphQL API.

Loads of optimization work has been done on the backend side, and the team will continue the following work during the next sprints:

• Subscriptions now work reliably without daily reconnections;
• Work via websocket protocol do not cause memory leaks now;
• Reach maximum http and wss request throughput with best performance to define component scaling in production;
• q-server code refactoring (a lot of unused code was removed) and unused API deprecation, to ease maintenance.

Gosh instructions were supported in SDK, TONOS-CLI and Evernode-SE, the Ever Platform team is supporting the Node team with REMP high load testing on FLD and internal networks. On the Flex side several improvements were made to Flex-SDK-JS library to speed up the order processing functionality.

Finally, the team finalized the Dedicated Cloud specification and pricing so that anyone who needs a Dedicated Node or Cloud maintained by our team can come to us and we will provide the conditions. 👩‍💻

🍒 For the cherry on top, we truly understand how important the trust of customers is. We published the list of projects that use our services and products, so you can be sure you can rely on our tools.

Node

The EverX Node team is currently focused on improvement of performance characteristics for Node protocols, in particular, REMP. REMP (Reliable External Messaging Protocol) guarantees that a message received by validators is included in a block in the order it was received. Tracking the order prevents front-running attacks, where the re-ordering of users’ transactions allows someone else to collect arbitrage. Because there is no re-organizing in the message queue, users can be sure of how their transaction will be executed. Therefore, messages can be considered finalized with a very high probability within 0.2 seconds.

REMP also has built in DDoS protection by banning users who spam messages that fail upon execution for ever-increasing periods of time. REMP’s code has been written and is close to launch.

The team is thrilled to announce that the REMP protocol performance was increased 6 times (from 1000 to 6000 TPM) during experiments over the community test network. Even though it is not the final number, it’s an intermediate result while testing the REMP implementation and finding improvement points.

In addition, several advancements to the EverX blockchain broadcast protocol were developed and evaluated in a real (test) network. The main goal of these advancements is to significantly reduce the protocol load without data transfer degradation. The results of evaluation are shown below:

✅ That’s it for this month’s digest. Stay tuned for more updates from the dev team at EverX! Be sure to follow our accounts to stay up to date:

Twitter

LinkedIn

Telegram

🤝 Interested in joining a brilliant team of talented developers? Check out our open positions here.

EverX September Digest: Drive Chain, FLEX DEX, Ever.Live and more updates.

Dear EverX community,

The summer days are coming to a close and the days are getting shorter, but things are really ramping up over here at EverX. Over the past 30 days the developers have been working hard in their project teams and reporting on milestones. We’re pleased to share our latest updates with you below.

Node Team

The Node team have been mainly focused on finalizing Drivechain. Drivechains, decentralized storage devices in the Everscale network, are essentially workchains that are optimized in order to store large amounts of data. Drivechains have unique smart contracts located on them and in order to store a file on a drivechain, you need to deploy a “file index” smart contract.

Memory optimization of Node:

By introducing a new method of cell storage and a new garbage collector mechanism the team have been able to improve memory consumption.

• ‘Old version’: the previous version before optimization used up to 100gb memory
• The ‘New version’ is optimized, but because it doesn’t utilize ‘low memory mode’ of cell storage it can work well up to 35GB
• The ‘New version’ in ‘Low memory’ mode works slower, uses memory cache but only uses up to 6GB

The team is also in the process of testing REMP (Reliable External Messaging Protocol) with the community.

FLEX Team

Great news! The FLEX team recently implemented a new container along with other elements which work to increase the capacity for order queues. The team has reported that they previously logged 240 orders in one queue in a price contract, but with the new updates they’re able to log a 100x improvement over the initial capacity.

Deployment of new DEX on mainnet

FLEX is officially on mainnet (though temporarily in incognito mode 😎). In preparation for launching on mainnet, the team took care to review the deployment scripts in order to reduce cost of deployment.

The FLEX DEX now features three pairs available for trading on mainnet: EVER/USDT, WBTC/EVER and WETH/EVER. The team is ready to deploy the rest of the pairs according to information from market makers, which will make 10 pairs in total. They are taking care not to list pairs without proper liquidity.

Tagging on to the exciting news, we want to underpin the value of one of the most important features of FLEX: the Limit Order functionality. When a user places an order at the best price in the Orderbook, the order will immediately be executed at the best price. But when a user places their order at a price different from the best price — the Orderbook prices will then be analyzed and the order will be executed at the best available price when possible. 🤑

Flex Electron Dapp — FLEX’s little secret 🤫

Flex has been released on mainnet as a Dapp, which currently trades with real tokens, but access has currently been limited to a select few to ensure the quality and experience is met. Flex DEX contracts have been deployed on mainnet and they are immutable. Any changes to the DEX contracts are only possible through the migration procedure to the new version of the DEX. Access to the Flex DEX is possible through different versions of the Dapp, which provide UI for traders.

Currently, access is only available through a desktop Flex Dapp for various platforms, but more options will be available at a later date. Dapps may also include DeBots under the hood (or another other technology). Dapp contracts are not immutable, and new features will be added to UI more often than DEX updates. When the Flex API will be open, anyone will be able to make a Dapp to provide UI for trading on Flex DEX.

The Dapp is currently available for Windows, Linux and Mac users and will be available to the public shortly. 🥳

Ever.Live Team

The Ever.Live team was focused on two main topics this month:

1. Refactoring from React Native to React. React Native is like React, but it uses native components instead of web components as building blocks. The goal was to remove React Native from the bundle to reduce the size as every step improves performance and reduces the time needed to render pages. The team demonstrated how Ever.Live now loads quicker and can render a long list with images without delay.

1. The team implemented components on mainnet such as a navigation bar, software version details, a new filter for messages from accounts, along with the ability to filter the messages by internal or external. These new UI component are helpful for realizing account messages.

Quick updates from the Evernode Platform Team

Evercloud

From 09.09.22 Evercloud has only been available for authorized users. Please proceed to https://evercloud.dev/ to get your credentials.

The Token API is on the way to production with the release expected for the middle of September. Keep an eye out for the announcement!

Evernode-SE

We have huge news! We’re thrilled to announce that the team has increased SE speed up to 70–400%, depending on the test logic. Everscale development is much faster now 🥳

https://github.com/tonlabs/evernode-se/releases/tag/0.33.1

SDK

Flex SDK https://github.com/tonlabs/flex-sdk-js has been updated to the latest Flex contracts version–and yes, the DEX itself is not yet available to the public–but it will be soon.

The team also kicked off the development of the MVP version of Wallet SDK https://github.com/tonlabs/wallet-sdk-js which will cover such use-cases as deployment of different types of owner wallets, getting token balances and implementing token transfers.

What’s next?

• Release of Flex API to Evercloud
• Support of Gosh VM features in SE and SDK
• Wallet SDK
• “Make a snapshot”/ “Revert to snapshot” commands in SE that will allow to save local node state and return to it.
• REMP release to production
• And much more!

✅ This sums up the last few weeks from the dev teams at EverX! Be sure to follow our accounts to stay up to date:

Twitter

LinkedIn

Telegram

🤝 Interested in joining a brilliant team of talented developers? Check out our open positions here.

Hello EverX fans! There’s been a lot of action since our last update in July as the teams within EverX work diligently on improving reliability, efficiency and the quality of our products.

A few weeks ago, the key developers of the Everscale network held an important conference to discuss the organizational aspects of Everscale’s development. This conference highlighted the decision to divide the EverX team into several product teams, all of which are already becoming independent teams within the EverX company with their own team leads.

You can read more about the important and positive changes to the structure of the core team of EverX here.

Let’s take a look at the latest developments by some of our teams:

#Evernode Platform/SDK

#Ever.Live

#Node

#FLEX

Ever.Live: Reliable Algorithms and Improving Experience

The Ever.Live team continues to work on replacing React Native components with React components in order to completely switch to React, which increases the speed of UI. One of the recent changes is a new date-time picker component based on a React library and other components under the hood.

The Ever.Live team recently updated the elections time algorithm that shows time of the next 2 elections for a new more robust version. The previous version was not able to show the time when the network stops (or in other unusual situations). The new algorithm can show this reliable information in critical situations, which is not only useful on the mainnet but other networks as well.

The team has also:

• Sped up statistics for accounts;
• Swapped the the old datepicker out for a more comprehensive version from the React library and adapted it for Ever.Live;

One functionality of this new datepicker is particularly useful for developers: one can now search a specific timeframe, even down to a few seconds, to find specific information.

Node: New Shard States Storage

With the help of the Everscale community, the Node team has been taking necessary actions to prepare for working on the node version update. Synchronizing these efforts is critical because this update itself is critical. It requires long-term operation with the database in order to restore it, therefore it’s crucial to arrange the order in which the validators will do the update on the node.

Currently the situation with the main network is due to the update process. Approximately 50% of the validators are running the new node and the remaining 50% are running the old node.

Also discussed by the team has been new functionalities to be embedded into the node blockchain, such as a decentralized elector and centralized file data storage (DriveChain). In order to understand the best way to implement the concepts and design a more reliable procedure while ensuring they can be stable in such a short amount of time, the team conducted multiple brainstorms.

Improvements in Operation with Blockchain State Data

The Node team has also implemented a new shard state storage, which is directly related to working with the shard state. This change improves memory consumption, stability and performance. Above you can see how a shard state can be seen as a graph of cells: mainnet contains 35 million unique cells, where each block updates x numbers of cells in the shard state. The shard state must save new cells from each new block very quickly and of course clear cells that we don’t need anymore.

Further updates include automated garbage collection, which is complex in itself as it must work as fast or slow to meet the demand of cells that exist. The minted cells in the image above are shown as white cells; the collector will remove all unmarked cells (red cells).

Luckily the algorithms work faster and use less memory, allowing the team to cut down on database usage, in comparision to the previous model.

Low Memory Mode and Fast Mode

Following hot on the tails of improvement and efficiency is the implementation of two variants: Low Memory and Fast Mode realization of a shard state. Thinking back to the previous cell image above, let’s imagine we download the shard state as a “Bag of cells”. It’s compact but we still need to deserialize, which is memory-intensive. Because it is impossible to create the same fast and slow memory algorithms, we created two variants. The first variant is the Fast Mode, which uses a lot of memory but works faster due to its optimization. The second is the Low Memory Mode, which uses approximately 5GB of memory, and is possible to adjust it to use even less memory.

Current topics the team is working on include:

• Shard state storage and optimization: currently model has a very heavy garbage collection mechanism
• Persistent state deserialisation: saving into shard state while the nodes boot
• Stabilizing the REMP solution: thanks to the community’s suggestions, the team has began working on topics related to deploying a solution for slashing, and want to apply it to current main network
• Currently in the design stage: a solution for using multiple workchains in one network
• Finalizing drive chain solution

Infrastructure: GOSH Testnet

For those who aren’t yet up to speed on one of the latest ventures, GOSH is a decentralized community Git blockchain, purpose-built for securing the software supply chain, while allowing developers to build consensus around their code. GOSH is the first and only formally verified Git implementation. Recently, there has been a wave of security breaches and malware attacks affecting numerous projects that store their code on GitHub, underlining the importance of using decentralized git storage.

Testnet

The GOSH infrastructure team recently rolled out a small testnet for testing GOSH updates. It’s a network consisting of only three validators and a single host. The team has also improved the blockchain data storage system and how it is distributed between big data, which also stores data more efficiently.

GOSH CI

The GOSH CI on temporary network recently underwent a sprint where the GOSH testnet and GOSH pipeline ensures the team is able to make changes, execute the pipeline and confirm that any changes or actions in testnet does not affect the real network.

Flex: Updates Galore, Limit Orders and More

While half the team enjoys summer holidays, the other half is busy with finishing the necessary features for launching Flex DEX in the Mainnet.

We would like to remind everyone that the current version of Flex is architecturally made for the work of institutional teams. It implies that several traders can register their pubkeys with their manager (by sending a QR code to him/her) and receive funds from a central wallet. As a result, the number of contracts to be deployed at the initial authorization is more than it could be in case of a single trader only (and the whole flow obviously looks a bit complex).

While the Flex public beta in Devnet is currently available as a web app, the Mainnet institutional version will be distributed as a desktop app for security reasons. The team is now working on the system to build, distribute and update the desktop app based on the Electron technology. According to the Flex team’s roadmap, they also plan on making a simpler web version of Flex working with a wallet extension–targeting a single trader case.

Limit Orders

The Limit Order feature was recently released on public beta. Limit orders are common methods and are favored by experienced traders.

For demonstration purposes, we’ll take the action of buying .5 ETH for 8500 EVER.

• We see the order doesn’t actually execute at 8500: the DeBot fills the order at 8320–buying from the orderbook at the best price available.
• The concept is clear how orders are filled with the best available price and that one order can be filled from several prices.

Gas Recovery via DeBot

Another interesting feature completed is the DeBot which allows a user to recover gas by following a very simple process:

Step 1. Log in to your Surf account and run the FLEX DeBot

Step 2. Select Account Management. Here you’ll be able to see all your trades.

Step 3. Select User ID and Wallets to recover the gas.

Helpful Instructions

The FLEX instructions have been updated to include information such as How to Trade, How to Withdraw, Recover Gas Balances and more.

3, 2, 1….🚀

As the latest version of the FLEX public beta has been released to the community, the Flash Exchange crew has been heads-down conducting stress tests, finalizing the UI, and implementing all the remaining features and feedback from the community in order to make sure FLEX is ready to make its official debut. 🥳

Evernode Platform/SDK

Evercloud

Over the past few weeks the Evernode team has completed two milestones: Authorization and the Developer Dashboard.

Authorization

Authorization to Evercloud will be mandatory starting on the first of September (09/01). Be sure to get your credentials and read through the Get Started guide.

Developer Dashboard

If you’ve read through the Get Started guide you have most likely discovered the Developer Dashboard which we will continue developing as a product. Other than access credentials and security settings, the roadmap includes project analytics and, in the near future, handy developer web tools.

Client Libraries

Core (Rust)

• Improved the time synchronization mechanism;
• Basic Auth key was supported in network config.

Rust Changelog

JavaScript

• lib-web option disableSeparateWorker.By default, lib web starts a separate worker that will utilize core (wasm). So the main thread never freezes — it is sufficient for UI. Although in some cases (e.g. when a worker already exists in an application or extension) a separate worker is a bad approach. In this case the application can suppress this with libWebSetup({disableSeparateWorker: true}).
• The team also fixed some issues with memory allocation in the web version for zip/unzip operations.

JavaScript Changelog

Evernode-SE

The team added a REST API endpoint/se with several management functions to their famous blockchain emulator.

/se/increase-time?delta=<seconds> — feature to move time forward

/se/time-delta — returns current gen_time_deltaproperty value

/se/reset-time— resets gen_time_delta to 0

Evernode-SE Changelog

Evernode-DS

The team also released node version upgrades and bug fixes.

Evernode-DS Changelog

✅ This sums up the last few weeks at EverX! Be sure to follow our accounts and stay up to date

Twitter

LinkedIn

Telegram

🤝 Interested in joining a brilliant team of talented developers? Check out our open positions here.

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.

To get your credentials, please go to https://dashboard.evercloud.dev/ and follow the guide https://docs.everos.dev/evernode-platform/products/evercloud/get-started

From the Evernode Platform team

We are continuously working on improving our products and authorization was a natural step forward. Authorization allows us to apply different limit policies for different types of users, add billing and, therefore, have the opportunity for further platform improvements because of eliminated API abuse and collected funds.

Reliable scalable public infrastructure is a crucial instrument for the onboarding of new developers with a good argument to try our network: after a quick registration you’ll get the endpoint for free.

Billing will be introduced in the near future and, of course, it will be a Freemium subscription, so projects with a low number of requests will continue to have free access and newcomers can always try our ready-to-go infrastructure for free.

About the dashboard

Currently, the dashboard will only provide you with access credentials for your projects. In the near future project security settings and analytics will be added. We will continue expanding the dashboard with cool new features for developers.

Evercloud availability, response time and limits

Together with authorization we introduce balancing endpoints for each network: no need to implement balancing on the client side any more!

For the last year the availability has been 99.99 (downtime caused by network issues is not included in this calculation). Medium response time is 50ms.

There is a limit of 100 connections per second from 1 IP. No additional limit policy is introduced yet, but soon we will introduce query cost based limit policy.

Important changes to the Everscale network’s technical development process

On Tuesday the 26th of July, 2022, the key developers from the Everscale network held an important conference to discuss the organisational aspects of Everscale’s development.

It’s no secret that all teams involved in the ecosystem, such as EverX, Broxus, and ITGold, have a lot of people and ongoing projects. All of which require coordination and careful planning — but also requires autonomy. That’s why we want to highlight some important and positive changes to the structure of the core team of Everscale developers — EverX. The decision has thus been made to divide the EverX team into several product teams.

Currently, the main EverX products are:

1. Ever Node
2. Ever Platform
3. Toolchain
4. Surf
5. FLEX
6. GOSH

All of them are now becoming independent teams within the EverX company with their own team leads. Mitja Goroshevsky continues to lead the development process of GOSH in his team, while the development of the whole Everscale blockchain is becoming more optimized. Six team leads have more time than one, and we’ll be able to advance as fast as possible.

Ever Node is one of the most significant products, and we have to keep in mind the business interests of many parties, especially our validators and other teams. That’s why the development is now going to be coordinated by the architectural committee, led by Pavel Prigolovko and Vladimir Maslyakov, and including Broxus and ITGold members. The process is going to become more transparent to the community — we’ll keep everyone updated on what’s going on inside EverX.

Among all its other goals, Everscale is a business-oriented blockchain, and we have a set roadmap and priorities for making our ecosystem attractive as an industrial solution. It has to be fast, scalable, decentralized, and secure. We have achieved many goals, and Everscale is already far more advanced than the majority of our competitors — but there is still a lot to be done. The architectural committee will serve as an entity setting short-term and mid-term tasks for dev teams according to business priorities. The team will create a draft of the plan for each task, and the committee will review and approve it. This kind of approach will help everyone stay on the same page, and we’re sure that Everscale will benefit from it.

This scheme has been already tested at EverX for one month, and the results were pretty solid, so we’re confident about continuing to use it. We’ll be sure to keep you updated!