According to MEET.ONE, EOS Authority today launched the “Update Eosio.token Contract” proposal (the second step of REX deployment). The previous block node had initiated the proposal and obtained a valid vote of 15 votes, but failed to successfully update the contract due to failed execution on the chain. After several days of repair, the proposal has been resubmitted to 21 outbound nodes for voting. At present, only 1 valid vote is obtained, and 14 votes are still required to be approved. In addition, EOS Authority is particularly grateful to Block.one's Bart for helping diagnose the RAM problem of eosio.token.