Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typo suggestions for Update README.md #335

Merged
merged 1 commit into from
Dec 20, 2024
Merged

Typo suggestions for Update README.md #335

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions app/upgrades/v1/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ different block headers. So, the upgrade data will be divided into 2

Devnets that are only for internal testing should just replace the upgrade
data files in testnet and build the binary with `make build-testnet`. No need
to push the devenet data into the github repository.
to push the devnet data into the github repository.

## Upgrade data as string

Expand All @@ -47,7 +47,7 @@ This upgrade accepts insertion of multiple
due to Babylon Phase-1 and Phase-2 launch will be a few months apart, so
during Phase-1 Babylon accepts BTC delegations without Babylonchain running.
At the time of launching the Babylonchain it is needed all the BTC block
headers that has passed since babylon started to accept BTC staking messages,
headers that have passed since babylon started to accept BTC staking messages,
and to avoid giving too much work for
[vigilante](https://github.com/babylonlabs-io/vigilante)
to submit all of those missing headers.
Expand Down
Loading