Sandbox testing has shown this fixes the issue of two async message in the same slot, where the 1st updates the bytecode of the target contract.
Before this fix, if the 1st async message updates the bytecode, then the second async message will take into account an out of date bytecode for the target address.
[ ] document all added functions
[x] try in sandbox /simulation/labnet
[ ] if part of node-launch, checked using the resync_check flag
[ ] unit tests on the added/changed features
[ ] make tests compile
[ ] make tests pass
[ ] add logs allowing easy debugging in case the changes caused problems
[ ] if the API has changed, update the API specification
Sandbox testing has shown this fixes the issue of two async message in the same slot, where the 1st updates the bytecode of the target contract.
Before this fix, if the 1st async message updates the bytecode, then the second async message will take into account an out of date bytecode for the target address.
resync_checkflag