According to WhaleEx, the EOS community has been testing the version for a long time since the Block.one developer submitted a stable EOSIO contract containing REX. After a series of inspections and tests, EOS Authority just launched a REX (Step 1) proposal on the EOS main network. Once the proposal is approved, an unprivileged account, eosio.rex, will be created. This account is required before the REX system contract is officially loaded. In place. At present, the proposal has obtained 4 valid votes for approval, and it is required to obtain 11 valid votes in order to pass.