contribution.md

contribution.json

Due to the simplicity of this PoT setup, the full contribution is sent as a json file between the sequencer & participants. This allows the use of a RESTful API between the two and verification of certain aspects of the contribution.json file via the contributionSchema.json (see: JSON schema).

BatchContribution object

We define a BatchContribution object for ease of specification the structure of which is identical to that of the initialContribution.json.

PowersOfTau

@dataclass
class PowersOfTau:
    g1_powers: List[bls.G1Point]
    g2_powers: List[bls.G2Point]

Contribution

@dataclass
class Contribution:
    num_g1_powers: int
    num_g2_powers: int
    powers_of_tau: PowersOfTau
    pot_pubkey: Optional[bls.G2Point] = None
    bls_signature: Union[bls.G1Point, str, None] = None

BatchContribution

@dataclass
class BatchContribution:
    contributions: List[Contribution] = []
    ecdsa_signature: Union[bytes, str, None] = None