We at EOS Authority believe that a successful deployment of REX will be a huge step forward for the EOS community and will be a significant achievement within the blockchain community as a whole. We decided to allocate a significant portion of our technical resources to do a full analysis of the REX code and test its inner workings by pushing REX to its limits. We have uncovered issues in the past with the first code review of REX in January where we identified a critical issue with REX. The second round of reviews & tests lasted over 14 days and the results were published. The third round of reviews and tests lasted about 2 weeks. We are happy to announce today that all our REX tests are complete and they have all passed!

All REX tests complete!

We managed to complete all our tests on the stable version of REX released by Block.one on 29th March 2019. This was after several months of EOS REX testing of all the release candidates. The EOS Authority team tested REX on internal machines and Testnets (like Jungle, BOS TestNet, etc). This time we also covered tests on the initialization parameters described by Block.one and they all work as expected.

What are the next steps?

REX deployment is a three-step process. As with all system changes, 15 out of 21 Block Producers will have to approve each step.

The first step is to create the account eosio.rex.
The second step is to update the eosio.token contract.
Finally, once both those steps are complete we can load up the REX smart contracts.

We have just proposed the first stage of deployment and it can be tracked on the BP multi-sig page on REX.

At the end of the 3 step process, REX deployment on the EOS Mainnet will be complete. We have a professional interface for REX and much more. The final version is ready, you will love it!. We can't wait for the community (token holders and DApps) to get their hands on REX. What if… we will deliver something more with REX? Stay tuned..

Learn all about EOS REX and track progress on https://eosauthority.com/rex/.