Authority changes were stored in reverse order (newest to oldest, rather than oldest to newest). This meant that if you iterated through the MessageSpan<AuthorityChangeReceived> changes assuming it would be oldest to newest, the state could end up in correct.
This PR rectifies this issue by ensuring they are ordered in the way we receive them.
Description
Authority changes were stored in reverse order (newest to oldest, rather than oldest to newest). This meant that if you iterated through the
MessageSpan<AuthorityChangeReceived>
changes assuming it would be oldest to newest, the state could end up in correct.This PR rectifies this issue by ensuring they are ordered in the way we receive them.
Tests
Documentation