October monthly digest: FLEX DEX, Evercloud API and REMP improvements

EverX
5 min readOct 27, 2022

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

EverX is an independent infrastructure and ecosystem developer for the Everscale Network