As a user i want to know when a VAA was redemeed on another chain.
Currently event-watcher captures the PublishMessage log that indicates a new vaa was created.
This story is to implement the other side of the transaction, when a vaa is relayed to another chain
and is redeemed the contract on the other side publish a message in the log called transferRedeemed .
This contract version is not deployed in all chains (Sept '23).
Base is one of the chain with the last version of the contract, here you can see when a completeTransfer() method is executed a message in the log is printed
Implement in the event-watcher the observation of the transferRedeemed message on the log for EVMs
Update the globalTransactions collection with the data from the redeem.
Update the wormholeTx collection with the data from the redeem
Push an event into the SNS queue (not applicable)
Criteria
globalTransactions collection:
If the document does not exist -> insert the document with data available from logs
If the document does exist
2.1. if destinationTx field does not exist -> insert the destinationTx field into the document with data available from logs
2.2 if destinationTx field exists -> none
As a user i want to know when a VAA was redemeed on another chain.
Currently
event-watcher
captures thePublishMessage
log that indicates a new vaa was created. This story is to implement the other side of the transaction, when a vaa is relayed to another chain and is redeemed the contract on the other side publish a message in the log calledtransferRedeemed
.In this case, the token bridge contract is the one publishes the message.
Here is a link to the contract implementation for EVM.
This contract version is not deployed in all chains (Sept '23).
Base is one of the chain with the last version of the contract, here you can see when a
completeTransfer()
method is executed a message in the log is printedLink to the log
The scope of this story is to:
event-watcher
the observation of thetransferRedeemed
message on the log for EVMsglobalTransactions
collection with the data from the redeem.wormholeTx
collection with the data from the redeemPush an event into the SNS queue(not applicable)Criteria
globalTransactions
collection:destinationTx
field does not exist -> insert thedestinationTx
field into the document with data available from logs 2.2 ifdestinationTx
field exists -> none