-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Labels
C:p2pComponent: P2P pkgComponent: P2P pkgS:proposalStatus: ProposalStatus: ProposalT:breakingType: Breaking ChangeType: Breaking ChangeT:designType: Design work is neededType: Design work is needed
Description
From #2435 (comment)
Current thinking is no, under the assumption that we want to be able to sync a peer across multiple app versions. But this also means we don't know if we're actually compatible with a peer when we connect to them, since they could be on an old height/version, and we won't find out until we actually disagree on blocks somewhere.
More prudent might be to consider tracking the correct version for each height, and enforcing that on peers, and having peers update each other when their version changes, but this sounds a bit complected, so maybe our initial assumption needs to be challenged.
How will we communicate AppVersion changes?
Do we need to convergent and sync to a unified one?
- lay out pros and cons for different approaches
- compile solution with most merrit into ADR
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C:p2pComponent: P2P pkgComponent: P2P pkgS:proposalStatus: ProposalStatus: ProposalT:breakingType: Breaking ChangeType: Breaking ChangeT:designType: Design work is neededType: Design work is needed