Skip to content

Commit

Permalink
chore: fix link to registry fp (#106)
Browse files Browse the repository at this point in the history
  • Loading branch information
RafilxTenfen authored Aug 8, 2024
1 parent f642caa commit e0048d0
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/PULL_REQUEST_TEMPLATE/new_finality_provider.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
## Checklist

- [ ] I have followed the finality provider information registry
[guide](https://github.com/babylonlabs-io/networks/blob/ef18868512b0b9c823c653cdabc975f88b6fc7a2/bbn-1/finality-providers/README.md#L1)
[guide](https://github.com/babylonlabs-io/networks/blob/main/bbn-1/finality-providers/README.md)
- [ ] I have backed up my mnemonic
- [ ] I have read and agree to the [Babylon Ecosystem Participant License](https://docs.babylonlabs.io/assets/files/babylon-ecosystem-participant-license.pdf) and the [Babylon Ecosystem Participant Agreement](https://docs.babylonlabs.io/assets/files/babylon-ecosystem-participant-agreement.pdf).

Expand Down
2 changes: 1 addition & 1 deletion bbn-1/finality-providers/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -342,7 +342,7 @@ The pull request should follow the below template:
## Checklist
- [ ] I have followed the finality provider information registry
[guide](https://github.com/babylonlabs-io/networks/blob/ef18868512b0b9c823c653cdabc975f88b6fc7a2/bbn-1/finality-providers/README.md#L1)
[guide](https://github.com/babylonlabs-io/networks/blob/main/bbn-1/finality-providers/README.md)
- [ ] I have backed up my mnemonic
- [ ] I have read and agree to the [Babylon Ecosystem Participant License](https://docs.babylonlabs.io/assets/files/babylon-ecosystem-participant-license.pdf) and the [Babylon Ecosystem Participant Agreement](https://docs.babylonlabs.io/assets/files/babylon-ecosystem-participant-agreement.pdf).
Expand Down

0 comments on commit e0048d0

Please sign in to comment.