eth2.0-specs/tests/formats/bls/fast_aggregate_verify.md

# Test format: BLS fast aggregate verify

Verify the signature against the given pubkeys and one message.

## Test case format

The test data is declared in a `data.yaml` file:

```yaml
input:
  pubkeys: List[BLS Pubkey] -- list of input BLS pubkeys
  message: bytes32 -- the message
  signature: BLS Signature -- the signature to verify against pubkeys and message
output: bool  --  true (VALID) or false (INVALID)
```

- `BLS Pubkey` here is encoded as a string: hexadecimal encoding of 48 bytes (96 nibbles), prefixed with `0x`.
- `BLS Signature` here is encoded as a string: hexadecimal encoding of 96 bytes (192 nibbles), prefixed with `0x`.

All byte(s) fields are encoded as strings, hexadecimal encoding, prefixed with `0x`.

## Condition

The `fast_aggregate_verify` handler should verify the signature with pubkeys and message in the `input`, and the result should match the expected `output`.
Add tests for the Altair BLS helpers 2021-08-04 01:55:18 +08:00			`# Test format: BLS fast aggregate verify`
Update BLS test suite to BLS standard draft v2 format 1. Make sure that BLS -Verify APIs would only return `True` or `False` , no exceptions. 2. Use `eth2spec.utils.bls` instead of py_ecc for test generator 3. Add assertions in test generator 4. Add some special test cases for the -Verify APIs 5. Clean up the test format documents 2020-05-15 00:45:26 +08:00
			`Verify the signature against the given pubkeys and one message.`

			`## Test case format`

			The test data is declared in a `data.yaml` file:

			```yaml
			`input:`
Apply PR feedback from Danny and clean up the BLS test format docs 2021-08-06 16:39:35 +08:00			`pubkeys: List[BLS Pubkey] -- list of input BLS pubkeys`
Update BLS test suite to BLS standard draft v2 format 1. Make sure that BLS -Verify APIs would only return `True` or `False` , no exceptions. 2. Use `eth2spec.utils.bls` instead of py_ecc for test generator 3. Add assertions in test generator 4. Add some special test cases for the -Verify APIs 5. Clean up the test format documents 2020-05-15 00:45:26 +08:00			`message: bytes32 -- the message`
Apply PR feedback from Danny and clean up the BLS test format docs 2021-08-06 16:39:35 +08:00			`signature: BLS Signature -- the signature to verify against pubkeys and message`
			`output: bool -- true (VALID) or false (INVALID)`
Update BLS test suite to BLS standard draft v2 format 1. Make sure that BLS -Verify APIs would only return `True` or `False` , no exceptions. 2. Use `eth2spec.utils.bls` instead of py_ecc for test generator 3. Add assertions in test generator 4. Add some special test cases for the -Verify APIs 5. Clean up the test format documents 2020-05-15 00:45:26 +08:00			```

Apply PR feedback from Danny and clean up the BLS test format docs 2021-08-06 16:39:35 +08:00			- `BLS Pubkey` here is encoded as a string: hexadecimal encoding of 48 bytes (96 nibbles), prefixed with `0x`.
			- `BLS Signature` here is encoded as a string: hexadecimal encoding of 96 bytes (192 nibbles), prefixed with `0x`.

Update BLS test suite to BLS standard draft v2 format 1. Make sure that BLS -Verify APIs would only return `True` or `False` , no exceptions. 2. Use `eth2spec.utils.bls` instead of py_ecc for test generator 3. Add assertions in test generator 4. Add some special test cases for the -Verify APIs 5. Clean up the test format documents 2020-05-15 00:45:26 +08:00			All byte(s) fields are encoded as strings, hexadecimal encoding, prefixed with `0x`.
Apply PR feedback from Danny and clean up the BLS test format docs 2021-08-06 16:39:35 +08:00
			`## Condition`

			The `fast_aggregate_verify` handler should verify the signature with pubkeys and message in the `input`, and the result should match the expected `output`.