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

Zilliqa: Consensus data on Block view #2288

Open
fedor-ivn opened this issue Oct 15, 2024 · 2 comments · May be fixed by #2375
Open

Zilliqa: Consensus data on Block view #2288

fedor-ivn opened this issue Oct 15, 2024 · 2 comments · May be fixed by #2375
Assignees
Labels
enhancement New feature or request

Comments

@fedor-ivn
Copy link

Associated PR in backend repo.

UI Customizations

Regular Block Table

On the Block view page, the block table should include the following new entry:

  • View: Integer field
    • Tooltip: "The iteration of the consensus round in which the block was proposed."

Quorum Certificate

Each block in Zilliqa has an associated Quorum Certificate entity containing several fields. We need a layout to display this entity in a structured and user-friendly way. The fields in the Quorum Certificate are:

  • Signers: Currently, this should display as a list of integers representing validator indexes. However, future enhancements may link these integers to validator addresses. So it would become a list of addresses.
  • Signature: A hex string of 194 characters (similar to a block hash, but longer).
  • View: Integer field indicating the consensus round, similar in appearance to a block number.

Data example

Field Tooltip Example Value
View "The view number of the quorum certificate, indicating the consensus round." 1137866
Signature "Aggregated BLS signature representing the validators' agreement." 0xa78c7f3e07e1df963ddeda17a1e5afd97c7c8a6fc8e0616249c22a2a1cc91f8eef6073cab8ba22b50cc7b38090f1ad9109473d30f24d57858d1f28c6679b3c4deeb800e5572b5e15604596594d506d3103a44d8b707da581f1a4b82310aeecb6
Signers "An array of integers representing the indices of validators who participated in the quorum (indicated by the cosigned bit vector)." [0, 1, 3, 8]

Aggregate quorum certificate

Some blocks in Zilliqa have an Aggregate quorum certificate. This certificate structure is nested, requiring a clear display strategy. The fields in this entity include:

  • View: Similar to the Quorum Certificate.
  • Signature: Same as in the Quorum Certificate.
  • Signers: Same as in the Quorum Certificate.
  • Nested Quorum Certificates: A list of nested Quorum Certificates, each with fields similar to the Quorum Certificate but with an additional small integer field named Proposed by Validator.

Aggregate quorum certificate data example:

Field Description Example Value
View "The view number of the aggregate quorum certificate, indicating the consensus round." 1137866
Signature "Aggregated BLS signature representing the validators' agreement." 0x820f591cd78b29a69ba25bc85c4327fa3b0adb61a73a4f0bd943b4ab0b97e061eae9ac032d19fbfab7efb89fac2454ab0b89fea83185c0dac749ff55b0e2c21535a2b712872491577728db868d11939461a6bfde0d94d238f46b643bbe19767e
Signers "An array of integers representing the indices of validators who participated in the quorum (indicated by the cosigned bit vector)." [1, 2, 3, 8]
Nested Quorum Certificates - See example table below

Nested quorum certificates data example:

Field Tooltip Example Value
View "The view number of the quorum certificate, indicating the consensus round." 1137863
Signature "Aggregated BLS signature representing the validators' agreement." 0xa78c7f3e07e1df963ddeda17a1e5afd97c7c8a6fc8e0616249c22a2a1cc91f8eef6073cab8ba22b50cc7b38090f1ad9109473d30f24d57858d1f28c6679b3c4deeb800e5572b5e15604596594d506d3103a44d8b707da581f1a4b82310aeecb6
Signers "An array of integers representing the indices of validators who participated in the quorum (indicated by the cosigned bit vector)." [0, 1, 3, 8]
Proposed by Validator "Validator index proposing the nested quorum certificate" 1
@tom2drum tom2drum added the need design For issues that wait for design updates label Oct 15, 2024
@fedor-ivn
Copy link
Author

fedor-ivn commented Nov 5, 2024

@fedor-ivn fedor-ivn added enhancement New feature or request and removed need design For issues that wait for design updates labels Nov 5, 2024
@tom2drum tom2drum self-assigned this Nov 8, 2024
@tom2drum
Copy link
Collaborator

tom2drum commented Nov 8, 2024

Examples:

@tom2drum tom2drum linked a pull request Nov 8, 2024 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants