sigp
Siren didn't register deposit
I'm using firefox with the frame extension and the frame wallet. I'm using a trezor attached to frame (although I dont think this is relevant information).
I submitted a deposit using frame. Frame acknowledges the block as confirmed. Siren is stuck on loading:
It looks like Siren is stuck in this permanent state, without a timeout, or cancel button.
Although the deposit has been made, it looks like Siren doesn't create the keystore or upload it. Not sure how siren is designed to recover from this state
I ended up doing multiple deposits at once after this and they all worked perfectly. Maybe this is a once off, but we probably need to handle this state
I've reproduced this. I suspect this is a timing issue.
For reference (I don't think its important tho, I'm using firefox with frame (set to metamask immitation) and using a trezor).
To reproduce,
- Click make a deposit to start a transaction in Siren
- Wait for 30 seconds to 1 minute before signing
- Sign the transaction
- Siren doesn't seem to register the result.
In this case, Siren doesn't upload the validator keys.
I think we need a timeout and the option for the user to upload the keys to the VC so they don't get lost in limbo.
I've just tried a topup with Frame, waited ~ 5mins to sign the Tx.
Siren picked it up nicely.
This was using Chrome with the Frame Companion extension, and a hot wallet within frame.
Frame, Brave, Frame Companion set to metamask imitation
Waited > 5 mins for signing a topup, and Siren did not pick it It up
same setup, Frame Companion set to Frame... no issues.
So it seems to be limited to Frame with MM compatibility.
but in my experience over the years, any transaction that is not signed or declined immediately is kinda doomed anyway? i may be making stuff up but I've trained myself to either insta-sign or reload any page right before signing 🙃