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

ABCI++ vote extensions & FinalizeBlock #12

Closed
15 of 17 tasks
Tracked by #9 ...
sergio-mena opened this issue Dec 23, 2022 · 1 comment
Closed
15 of 17 tasks
Tracked by #9 ...

ABCI++ vote extensions & FinalizeBlock #12

sergio-mena opened this issue Dec 23, 2022 · 1 comment
Assignees
Labels
P:new-use-cases Priority: Enable new use cases for application developers
Milestone

Comments

@sergio-mena
Copy link
Contributor

sergio-mena commented Dec 23, 2022

This is the continuation of the work started in tendermint/tendermint#9053: backport ABCI++ implementation, which lives in the v0.36.x branch.
Once this tracking issue is completed, the whole ABCI++ interface should be ready for QA process, and then release.

Proposed Path to Done. Summary

The main idea behind this plan is to proceed in the same way as tendermint/tendermint#9053.
The main approach is:

The work is structured very similarly to #9053. It consists of two main parts (further described below):

  • (1) Preliminary work
  • (2) Core feature work

(1) and (2) can mostly proceed in parallel.

protobufs will be managed as in v0.37.x → They will evolve with the code

Proposed Path to Done. Details

(1) Preliminary Work

We could have two threads here, but as all these tasks serialized are shorter than the critical path in "Core Feature Work", there's no point

(2) Core feature work

We have three threads that can proceed in parallel:

  • Vote extensions (*)
  • FinalizeBlock (*)
  • Spec and doc work

(*) Only when vote extensions and FinalizeBlock are done, can we proceed with the fourth part:

  • Final adjustments
    • tasks here could be further parallelized

Vote Extensions

FinalizeBlock

Final adjustments

Most of these tasks can be done in parallel, but they are quite short.

Spec and doc work

Low risk, can proceed completely in parallel with the rest

Original issue: tendermint/tendermint#9396

@sergio-mena sergio-mena self-assigned this Dec 23, 2022
sergio-mena pushed a commit that referenced this issue Feb 7, 2023
* Bump version to v0.34.26

Signed-off-by: Thane Thomson <connect@thanethomson.com>

* Prepare changelog for v0.34.26 release

Signed-off-by: Thane Thomson <connect@thanethomson.com>

---------

Signed-off-by: Thane Thomson <connect@thanethomson.com>
@adizere adizere added this to the 2023-Q2 milestone Mar 28, 2023
@sergio-mena sergio-mena removed this from the 2023-Q2 milestone Mar 29, 2023
@thanethomson thanethomson added the P:new-use-cases Priority: Enable new use cases for application developers label Jun 20, 2023
@adizere adizere assigned adizere and unassigned sergio-mena Jan 11, 2024
@adizere adizere added this to the 2024-Q1 milestone Jan 11, 2024
@adizere adizere modified the milestones: 2024-Q1, 2024-Q2 Apr 1, 2024
@adizere
Copy link
Member

adizere commented Jul 4, 2024

Closing this as it's pretty much done. The only item left is issue 25, which is tracked separately.

@adizere adizere closed this as completed Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P:new-use-cases Priority: Enable new use cases for application developers
Projects
Status: Done
Status: In Progress
Development

No branches or pull requests

4 participants
@thanethomson @adizere @sergio-mena and others