The explorer right now assumes a default validator set for all messages, which means that if a message is sent via SC with a different validator set, it will not accurately indicate progress on the timeline view. Thus, the explorer should be able to
understand ISMs of message recipients
parse out the validators signers necessary
look up the storage locations on the origin ValidatorAnnounce contract
fetch info from there
There is a good chance that a bunch of this logic should exist in the SDK for reuse
nambrot
commented
4 months ago
The explorer right now assumes a default validator set for all messages, which means that if a message is sent via SC with a different validator set, it will not accurately indicate progress on the timeline view. Thus, the explorer should be able to
There is a good chance that a bunch of this logic should exist in the SDK for reuse