urbit
Cannot use legacy token with Metamask?
Describe the bug After I send the transaction to breach I'm taken to the keyfile download page, but the button to download is grayed out, claiming: "Derived networking keys do not match on-chain details".
The main keyfile download button on the OS dashboard is also grayed out saying "if you set networking keys with an older version of Bridge, try logging in again with "Use Legacy Token'".
The last time I breached this point was about a year ago so I understand I need to use the legacy token, however I don't see an option to use this with Metamask. The point is on L1, secured on a Ledger.
Am I missing something or can we only apply the legacy token in the Recovery Phrase and Master Ticket login cases?
I've attempted this using the urbit.org and self-hosted versions via Firefox and Brave to no avail.
Screenshots
Desktop (please complete the following information):
- OS: Ubuntu 22.04.2 LTS
- Browser: Brave & Firefox
Login method (please complete the following information): Metamask 0x877922fCD01F029adc6a68eC5265823FBcafDBb0
Additional context The point is an L1 star with an L2 spawn proxy.
could i get some eyes on this? basically stuck in limbo here...
i've tried entering in my ledger's recovery phrase, but it only accepts 14 words; mine is 24.
pls lmk if there's any other steps i should try.
i tried changing sponsors, but am getting an error when i attempt to run the tx:
like the star, i also can't download my planet's keyfile:
since the latest version of bridge is the issue, would it be advisable to attempt on an older version?