chore: replace bbl with bbn and gitignore #98
Merged
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
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.
As per the last engineering meeting, bbn will be more widely used compared to bbl. Vigilante implementation has already started using bbn rather than bbl. In order to test vigilante that talks to Babylon, Babylon will need to use bbn as well for the account prefix, denom, and many more.
Thus, this PR replaces bbl with bbn in account prefix, denom and comments. There are still some bbl occurrences in the code, mostly in the naming of imported dependency. Didn't replace these in order to avoid merge conflicts in the presence of our rapid development.
In addition, this PR also makes git to ignore
.testnet/, which is a folder generated when starting a Babylon node by using the code in README.