2021-08-05 03:12:36 +00:00
|
|
|
# Test format: Ethereum-customized BLS pubkey aggregation
|
2021-08-03 17:55:18 +00:00
|
|
|
|
2021-08-05 03:12:36 +00:00
|
|
|
A BLS pubkey aggregation combines a series of pubkeys into a single pubkey.
|
2021-08-03 17:55:18 +00:00
|
|
|
|
|
|
|
|
## Test case format
|
|
|
|
|
|
|
|
|
|
The test data is declared in a `data.yaml` file:
|
|
|
|
|
|
|
|
|
|
```yaml
|
|
|
|
|
input: List[BLS Pubkey] -- list of input BLS pubkeys
|
2021-08-06 08:39:35 +00:00
|
|
|
output: BLSPubkey -- expected output, single BLS pubkeys or empty.
|
2021-08-03 17:55:18 +00:00
|
|
|
```
|
|
|
|
|
|
|
|
|
|
- `BLS Pubkey` here is encoded as a string: hexadecimal encoding of 48 bytes (96 nibbles), prefixed with `0x`.
|
|
|
|
|
- No output value if the input is invalid.
|
|
|
|
|
|
|
|
|
|
## Condition
|
|
|
|
|
|
2021-08-05 03:20:49 +00:00
|
|
|
The `eth_aggregate_pubkeys` handler should aggregate the signatures in the `input`, and the result should match the expected `output`.
|
