onflow / onflow/flow

Spock aggregation

Open
#1,515 0 comments 0 reactions 1 assignee View on GitHub

@tarakby is already working on this.

Since Oct 3, 2024.

Dominant language
Go
Stars
361
Forks
159
PR merge metrics
No merged PRs in 30d

Description

Why

SPoCK proofs is how Flow mitigates the Verifiers Dilemma and is required for a mature network. SPoCK security has been already proved in a research paper.
SPoCK aggregation is a way to compress many proofs in one in order to scale the verification nodes and keeping a reasonable block size. This is a long duration research project (12+ months), the result of which will be a security proof and a paper which demonstrates the provability of the approach.

How will we measure success

This is a long duration research project (12+ months), the result of which will be a security proof and a paper which demonstrates the provability of the approach

  • Tech lead, Alex and Dete are happy with the progress
  • More specifics TBD as time permits

DACI

D: Tarak
A: Alex
C: Dete
I: N/A

Problem definition

SPoCK aggregation is important for verification node scaling and keeping a reasonable block size.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.