feat: add basic chain aliasing and encoding for it #255
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Only caveat I would like to add is that the Oracle has no knowledge of aliases, but we don't really expect the Oracle to be sending register network messages, let alone alias messages |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a new message (RegisterNetworksAndAliases, tag 6) that allows to add a new network with a specific alias.
The intended use is to be able to allow for future proofing of chain aliases, while still allowing previously registered networks to be aliased through a preloaded aliases list (which includes all networks currently on any EBO, as well as most networks from hosted service)