docs: fix broken link to bug bounty #1496
Open
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
guckool
requested review from
rach-id and
evan-forbes
and removed request for
a team
rach-id
reviewed
Sep 22, 2024
Co-authored-by: CHAMI Rachid <chamirachid1@gmail.com>
|
IMO we should remove the entire |
Or should we remove the entire docs and leave only a readme in spec/ that points to the cometBFT spec repo? |
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.
Description
The link to the bug bounty mentioned in this readme is no longer valid, so I have updated it with the correct link which matches to the latest link mentioned in the cometbft spec: https://docs.cometbft.com/v0.38/spec/
PR checklist
.changelog(we useunclog to manage our changelog)
docs/orspec/) and code commentsNo further tests is needed as only doc is modified