The EOS node discussed whether to adjust the REX not-reserved reserve rate. The current plan has been adjusted from 20% to 0%.

Recently, with the explosion of the EOS main network CPU, REX has a problem of insufficient leaseable resources. The EOS node discussed the parameters of the REX non-rental reserve rate of 20% for many times. BM also said on Twitter today that the original parameters are conservative settings and are being considered for adjustment. At present, Ey Cafe team leader Syed has submitted changes on Github to 0%. Teams such as MEET.ONE Labs and EOS Nation have reviewed the code and look forward to more node attention. Link: