Previously, the #129 referendum proposal has been passed and is in the dispatch queue. Still, after the Bifrost team tested it, it was found that if the total weight of XCM messages in a single block exceeds ump_service_total_weight, they will be discarded, resulting in a loss of funds.
Fortunately, the original value of ump_service_total_weight is 100_000_000_000; there are not enough XCM messages to trigger this issue. However, if proposal #129 is executed, ump_service_total_weight will be reduced to 5_000_000_000. Thus there will be a high probability of triggering hidden issues, so Bifrost proposes to cancel the implementation of the proposal #129. Before the final conclusion, in order to minimize the harm, Bifrost proposed this referendum proposal to readjust ump_service_total_weight to 100_000_000_000, Fortunately, the proposal #129 has been revoked by the council through motion, so this proposal (#133) no longer needs to be executed. It can be rejected, thanks to everyone.
Thanks to the Acala team for cooperating with the test, and related issues have been raised for repair.
Expect Chaos
A proposal called #129 was passed but had a problem. If too many messages were in one block, some would be lost, causing a loss of money. The Bifrost team found this issue and suggested not to use proposal [#129] because it would make the problem more likely to happen. Instead, they wanted to change a number called ump_service_total_weight back to a bigger number to avoid the problem. But then, proposal [#129] was stopped by the council, so the new proposal [#133] is not needed anymore. Thanks to the Acala team for helping with the test, and a problem was found that needs to be fixed.