optimistic view claim rendering

[Keyrxng]

This should make the UI appear quicker because we are no longer awaiting the transaction to be confirmed onchain before allowing the tx be viewed on a block explorer. The loading mechanic once the wallet prompt is confirmed should disappear almost instantly as we have the tx.hash already.

• render the view claim button before we await the tx
• still produce the success toast after we await the tx

[ubiquity-os-deployer]

90b2ede

a23b602

cba5b51

3850fef

[github-actions]

Preview Deployment
90b2ededd43013800b1fdfd69c4c7629ea665383
cba5b51e801eea74594d50b34fb7019b9f8692ee
3850fef9c1ae07a73cf166deecb058c4d79d0249

[0x4007]

I can't test from mobile. Perhaps somebody else can

[0x4007]

@Keyrxng @whilefoo auto merge and self assign plugins need to only accept collaborator reviews not contributor. Can you guys address this

[Keyrxng]

I can't test from mobile. Perhaps somebody else can

I tried earlier but idk what I'm looking for honestly (and I messed it up and used prod).

Could you attempt to detail exactly where the bottlenecks you experience are whenever it happens again please as it would make it slightly easier to think of other fixes or if this is going to make any difference, thanks.

• time to load everything prior to clicking claim
• After clicking claim but before metamask has popped up
• Once metamask prompt has been confirmed
• Time between tx sent and tx confirmed

[0x4007]

1. Claim button press to metamask prompt
2. ...until transaction complete but perhaps that depends on the blockchain speed (optimistic rollup, such as Optimism, UX will probably be best)

[0x4007]

Green toast is misleading. Let's just add a new info, grey, toast for as soon as the transaction is initiated to share the transaction link.

Then retain the original behavior of showing green once it's completed.

[0x4007]

@Keyrxng This shouldn't have been merged. Can you fix?

[gentlementlegen]

Need ubiquity-os-marketplace/daemon-merging#19 in to fix this problem.

[Keyrxng]

Green toast is misleading. Let's just add a new info, grey, toast for as soon as the transaction is initiated to share the transaction link.

Then retain the original behavior of showing green once it's completed.

I was confused by this originally but look at my local notifications. The logic is as you describe, the notifications arrangement wasn't changed, previously we showed the link after the tx resolved and just before the success toast. Now we show the link after the tx is fired but before we await it.

The first info call is made inside transferFromPermit() then we display the link to the explorer and then inside waitForTransaction() we make the success call.