Migrate RFC 017 to RFC 100#450
Conversation
|
|
||
| The blocksync reactor featuring light client verification is being actively worked on (tentatively | ||
| for v0.37). So it is best if this RFC does not try to delve into that problem, but just makes sure | ||
| The blocksync reactor featuring light client verification is among the CometBFT team' current priorities. |
There was a problem hiding this comment.
This was what I worked on last year, do we still plan to go ahead with this ? In any case, not relevant for approving this particular PR.
There was a problem hiding this comment.
Good question :-)
I've just checked and I can't see any issue in CometBFT on this. IIRC it's because we only migrated those issues we'd need for Q1.
An idea would be to go back to the Tendermint Core repo, dig up the set of issues/PRs related to this, and write a tracking issue containing all that info. Then, we could use that issue to prioritize w.r.t. to other things we have on our plate.
jmalicevic
left a comment
There was a problem hiding this comment.
I just reviewed the last commit and I assume these are just minor edits before you actually update it with the final version in a subsequent PR.
Exactly |
Contributes to #444
This PR is the first step to finishing the RFC containing vote extension propagation.
This first step simply consists in copying RFC017 over to RFC100 and updating all the references to Tendermint Core, retracted/unreleased versions (
v0.35.x,v0.36.x) and links to the repo.IMPORTANT Note for reviewers: when switching to the "Files changed" tab to review, please review the last commit only. The first commit represents text already reviewed and approved last year, so I don't it is worth going through it again.
PR checklist
.changelog(we use unclog to manage our changelog)docs/orspec/) and code comments