Bridge/azimuth usability omnibus

[mrdomino]

Creating a catch-all for various bridge usability issues I encountered while trying to issue planets off a galaxy with bridge.

• [ ] as a galaxy-holder, I expect to be able to issue points under "issue point" for my galaxy. But I can't do that, and bridge generates transactions that fail, because the stars are in the lockup contract, and the lockup contract is back on an earlier screen where I wouldn't have noticed it. Sub-issues:
  • [ ] bridge shouldn't generate and send transactions to issue stars that can't be issued
  • [ ] the UI should clearly indicate that un-withdrawn lockup stars are not available under "issue point", e.g. by having a "withdraw unlocked stars" entry next to perhaps a renamed "issue point that has been withdrawn" entry
• [ ] as a galaxy-holder, I expect my spawn proxy to be able to unlock stars, not my ownership key. Solution: document this unfortunate state of affairs, e.g. on the star unlock page in bridge.
• [ ] when interacting with the lockup contract and unlocking a number of stars, bridge estimates gas at something like 0.25 ETH per transaction for 6 stars. In fact, each transaction winds up only costing something like 0.02 ETH in gas, an order of magnitude less.
• [ ] after accidentally funding the owner key with an obscene amount of ETH to cover the estimated costs of the withdraw operations, there is no obvious way to send the remaining large amount of ETH back. Possible solutions: implement basic ETH send/receive functionality in bridge, implement walletconnect server in bridge, provide a "export ETH private key from master shards" option in bridge.
• [ ] when trying to issue planets under a star owned by a hardware wallet connected via metamask, "set spawn key" and "issue point" are both greyed out with no indication of why this is. (There is a rumor circulating that this is because you need networking keys set to issue points.)
• [ ] "Set Keys" does nothing when clicked on while logged into metamask and operating on a star owned by it. It also provides no JavaScript errors. (It turns out that you actually want to go back from the "ID" page to the "OS" page, and probably "Set Keys" is perhaps trying to do this, but something is broken somewhere.)
• [ ] when opening web console vertically to see whether bridge is generating javascript errors, the screen shrinks. when the screen shrinks, the options to use a Ledger or Trezor are greyed out, because they are not supported on mobile devices, and bridge uses screen width to decide whether it's running on a mobile device. Solution: replace the entire internet with a new solid-state interpreter, OS, and programming language, so these sorts of things don't have to happen anymore.
• [ ] When trying to log in with a Ledger hardware wallet in Chrome, when I click "Authenticate", it fails with: Failed to sign with Ledger device: U2F DEVICE_INELIGIBLE. (This works in Firefox.)

[mrdomino]

(fwiw i don't think the right thing to do is to try and fix each of these individually; i think the right thing is more like "give bridge more attention and people, and basically redo it so it is good, and then make sure that these are non-issues afterwards by glancing at them". but want to log issues i run into as a matter of course.)

[Fang-]

Good list. To ease the pain/provide some commentary:

bridge shouldn't generate and send transactions to issue stars that can't be issued

Huh, I could swear we had checks for this at some point. Certainly the list of example point names it gives you should be pulled from not-yet-spawned points, and display a message if nothing is available.

as a galaxy-holder, I expect my spawn proxy to be able to unlock stars, not my ownership key. Solution: document this unfortunate state of affairs, e.g. on the star unlock page in bridge.

Secondary problem: you will not be able to visit the unlock page when logged in with addresses that don't control a lockup, because we cannot discover the relevant lockup details.

(There is a rumor circulating that this is because you need networking keys set to issue points.)

Turns our rumors are true sometimes!

"Set Keys"

This is not the "set networking keys" you were looking for. Thought this was also documented in some other issue since it's a long-standing pain-point with the current copy, but can't find it. I think this will be fixed in the L2 Bridge release.

When trying to log in with a Ledger hardware wallet in Chrome ...

Duplicate of #581.