Each message type attested by Paloma needs to implement VerifyAgainstTX to ensure the reported evidence actually matches the expected evidence.
For each message type - UploadSmartContract, UpdateValset and SubmitLogicCall we implement the VerifyAgainstTX method. It reconstructs the transaction data from the original message in the same way as Pigeon does and compares the resulting bytecode against what's reported in the evidence.
Testing completed
[x] test coverage exists or has been added/updated
[x] tested in a private testnet
Breaking changes
[x] I have checked my code for breaking changes
[x] If there are breaking changes, there is a supporting migration.
Related Github tickets
Background
Each message type attested by Paloma needs to implement
VerifyAgainstTXto ensure the reported evidence actually matches the expected evidence.For each message type -
UploadSmartContract,UpdateValsetandSubmitLogicCallwe implement theVerifyAgainstTXmethod. It reconstructs the transaction data from the original message in the same way as Pigeon does and compares the resulting bytecode against what's reported in the evidence.Testing completed
Breaking changes