This PR maybe makes the ChainPay operation a bit nicer from the user perspective.
When the intermediary observes the mined TX, she now uses the protocol ack pipe to return this txHash. (This is a hack - this ack pipe has been used until now only to return signatures - but the UserOperation protocol doesn't require a returned signature for a state update).
When the client receives the txHash, the client wallet pops a snackbar which displays the txHash.
If the approach is good, we could polish with:
making the returned txHash a clickable link to the l1 block explorer (if such an explorer is configured)
putting a spinner on the L1 Pay button while we wait for the hash
This PR maybe makes the ChainPay operation a bit nicer from the user perspective.
When the intermediary observes the mined TX, she now uses the protocol ack pipe to return this txHash. (This is a hack - this ack pipe has been used until now only to return signatures - but the UserOperation protocol doesn't require a returned signature for a state update).
When the client receives the txHash, the client wallet pops a snackbar which displays the txHash.
If the approach is good, we could polish with:
Screencast from 2023-10-20 12:15:13 PM.webm