Network keys set / not set - confusing error message screen

[morgrichards]

When I was setting my networking keys for my L1 star, ~panbel, I got the attached error message. I tried again and got the same result. I checked etherscan and the transcations had been confirmed. I stared at the screen for half an hour then gave up and went to bed. In the morning I was going to try again but found that they had now been set (twice).

The error message is confusing and contradictory. If setting keys can be subject to long delays this would be good to communicate in the Bridge UI.

Screenshots

Desktop (please complete the following information):
MacOS Ventura 13.0
Chrome 107.0.5304.87
Metamask Chrome extensions + ledger wallet
Eth address 0x20e6d376c6db6a76de7e4c6199a69fdfdff50c52

Bonus feedback
Also, would be good to have consistent title case and terminology across Bridge. Is it:

• Keyfile
• Key file
• keyfile
• key file

[tomholford]

@morgrichards Thanks for the feedback, agreed that the inconsistent naming is confusing.

Which version of Bridge were you using? We pushed a release last week with a fix for stale network keys, perhaps this would resolve the issue?