Bridge December update: v3.3.0 #1151
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was originally opened for the purpose of for making more robust improvements to Bridge. Given that the current Bridge codebase is so messy, and the landscape of Azimuth (and Urbit ID more broadly) management is diversifying, we are going a different route. The new approach is to slowly deprecate bridge instead, closing off routes to broken features (e.g. transaction history) and route to other Urbit ID management interfaces (e.g. network.urbit.org).*
Other options (will) include:
Perigee - Self-hostable interface for Azimuth (L1 and L2) written in Go, from Native Planet (hosted version coming soon to perigee.urbit.org)
Etherscan - General purpose block explorer which can readily interact with L1 Azimuth actions
Neoscape/Zodiac - COMING SOON (L1 points only)
Urbit.Box|house - COMING SOON (L1 points only)
Zenith - COMING SOON (L1 and L2; UX Changes TBD, likely only to impact Stars & Galaxies)
These other systems may support more streamlined flows, specified UX affordances, or security considerations, but the purpose of Bridge is to support the baseline functionality of both L1 and L2 Azimuth points to the extent that they interact with Urbit OS.
The purpose here is to make sure that the core flows of Azimuth actions are supported and maintained across the supported wallets, point types, and consensus mechanisms (Mainnet Ethereum, L2 Naive Rollup).
As such, this PR makes basic updates to begin pointing in this direction, fixing basic messaging and adding initial notices alluding to functionality being deprecated.
dev environment setup
Updates included close the following Issues:
PRs to merged in and include in release:
Functionality Removed/Modified and Rationale
Remove recovery phrase pathway from bridge.urbit.org hosted version (recommend user to Metamask path, as typing your seed phrase into the browser is bad.)Aborted due to recovery phrase usage being the default testing flow, retained for the time being.Invite code generation will route to 'spawn to an address' flow.