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.

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

chore: add recovery message types #1608

Open
wants to merge 11 commits into
base: feature/recovery
Choose a base branch
from

Conversation

evan-forbes
Copy link
Member

Description

still needs validate basic and tests

@evan-forbes evan-forbes added WS: Big Blonks 🔭 Improving consensus critical gossiping protocols recovery labels Feb 10, 2025
@evan-forbes evan-forbes self-assigned this Feb 10, 2025
}

// ToProto converts PartMetaData to its protobuf representation.
type HavePart struct {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be HavePart or HaveParts?

@evan-forbes evan-forbes marked this pull request as ready for review February 12, 2025 21:00
@evan-forbes evan-forbes requested a review from a team as a code owner February 12, 2025 21:00
@evan-forbes evan-forbes requested review from rootulp and ninabarbakadze and removed request for a team February 12, 2025 21:00
@evan-forbes
Copy link
Member Author

I'll defer to you @rach-id on when its okay to merge to the feature branch

@rootulp rootulp removed their request for review February 12, 2025 21:24
Copy link
Member

@rach-id rach-id left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

Left some optional changes that can be handled here or in a subsequent PR

"github.com/tendermint/tendermint/types"
)

// TxmetaData keeps track of the hash of a transaction and its location with the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// TxmetaData keeps track of the hash of a transaction and its location with the
// TxMetaData keeps track of the hash of a transaction and its location within the

Comment on lines +16 to +17
Start uint32
End uint32
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit]
would be nice to specify how inclusive/exclusive there ranges are. Maybe just a comment saying that the range is [start, End)

Comment on lines +41 to +43
if t.Start > t.End {
return errors.New("TxMetaData: Start > End")
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so the range is [start, end]?

type CompactBlock struct {
Height int64 `json:"height,omitempty"`
Round int32 `json:"round,omitempty"`
BpHash []byte `json:"bp_hash,omitempty"`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit]
what does bpHash stand for? maybe a comment specifying it's the block propagation hash

Comment on lines +114 to +115
// index, along with the proof of inclusion to either the PartSetHeader hash or
// the BPRoot in the CompactBlock.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how do we know whether this part's proof is for the partsetheader or the bproot?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
recovery WS: Big Blonks 🔭 Improving consensus critical gossiping protocols
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants