You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tests/formats/kzg_7594/recover_cells_and_kzg_proofs.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,17 +8,17 @@ The test data is declared in a `data.yaml` file:
8
8
9
9
```yaml
10
10
input:
11
-
cell_ids: List[CellID] -- the cell identifier for each cell
11
+
cell_indices: List[CellIndex] -- the cell indices
12
12
cells: List[Cell] -- the partial collection of cells
13
13
output: Tuple[List[Cell], List[KZGProof]] -- all cells and proofs
14
14
```
15
15
16
-
- `CellID` is an unsigned 64-bit integer.
16
+
- `CellIndex` is an unsigned 64-bit integer.
17
17
- `Cell`is a 2048-byte hexadecimal string, prefixed with `0x`.
18
18
- `KZGProof`is a 48-byte hexadecimal string, prefixed with `0x`.
19
19
20
20
All byte(s) fields are encoded as strings, hexadecimal encoding, prefixed with `0x`.
21
21
22
22
## Condition
23
23
24
-
The `recover_cells_and_kzg_proofs` handler should recover missing cells and proofs, and the result should match the expected `output`. If any cell is invalid (e.g. incorrect length or one of the 32-byte blocks does not represent a BLS field element), any proof is invalid (e.g. not on the curve or not in the G1 subgroup of the BLS curve), or any `cell_id` is invalid (e.g. greater than the number of cells for an extended blob), it should error, i.e. the output should be `null`.
24
+
The `recover_cells_and_kzg_proofs` handler should recover missing cells and proofs, and the result should match the expected `output`. If any cell is invalid (e.g. incorrect length or one of the 32-byte blocks does not represent a BLS field element), any proof is invalid (e.g. not on the curve or not in the G1 subgroup of the BLS curve), or any `cell_index` is invalid (e.g. greater than the number of cells for an extended blob), it should error, i.e. the output should be `null`.
Copy file name to clipboardExpand all lines: tests/formats/kzg_7594/verify_cell_kzg_proof.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,18 +9,18 @@ The test data is declared in a `data.yaml` file:
9
9
```yaml
10
10
input:
11
11
commitment: Bytes48 -- the KZG commitment
12
-
cell_id: CellID -- the identifier for the cell
12
+
cell_index: CellIndex -- the cell index
13
13
cell: Cell -- the cell
14
14
proof: Bytes48 -- the KZG proof for the cell
15
15
output: bool -- true (correct proof) or false (incorrect proof)
16
16
```
17
17
18
18
- `Bytes48` is a 48-byte hexadecimal string, prefixed with `0x`.
19
-
- `CellID`is an unsigned 64-bit integer.
19
+
- `CellIndex`is an unsigned 64-bit integer.
20
20
- `Cell`is a 2048-byte hexadecimal string, prefixed with `0x`.
21
21
22
22
All byte(s) fields are encoded as strings, hexadecimal encoding, prefixed with `0x`.
23
23
24
24
## Condition
25
25
26
-
The `verify_cell_kzg_proof` handler should verify that `commitment` is a correct KZG commitment to `cell` by using the cell KZG proof `proof`, and the result should match the expected `output`. If the commitment or proof is invalid (e.g. not on the curve or not in the G1 subgroup of the BLS curve), `cell` is invalid (e.g. incorrect length or one of the 32-byte blocks does not represent a BLS field element), or `cell_id` is invalid (e.g. greater than the number of cells for an extended blob), it should error, i.e. the output should be `null`.
26
+
The `verify_cell_kzg_proof` handler should verify that `commitment` is a correct KZG commitment to `cell` by using the cell KZG proof `proof`, and the result should match the expected `output`. If the commitment or proof is invalid (e.g. not on the curve or not in the G1 subgroup of the BLS curve), `cell` is invalid (e.g. incorrect length or one of the 32-byte blocks does not represent a BLS field element), or `cell_index` is invalid (e.g. greater than the number of cells for an extended blob), it should error, i.e. the output should be `null`.
Copy file name to clipboardExpand all lines: tests/formats/kzg_7594/verify_cell_kzg_proof_batch.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,4 +25,4 @@ All byte(s) fields are encoded as strings, hexadecimal encoding, prefixed with `
25
25
26
26
## Condition
27
27
28
-
The `verify_cell_kzg_proof_batch` handler should verify that `row_commitments` are correct KZG commitments to `cells` by using the cell KZG proofs `proofs`, and the result should match the expected `output`. If any of the commitments or proofs are invalid (e.g. not on the curve or not in the G1 subgroup of the BLS curve), any cell is invalid (e.g. incorrect length or one of the 32-byte blocks does not represent a BLS field element), or any `cell_id` is invalid (e.g. greater than the number of cells for an extended blob), it should error, i.e. the output should be `null`.
28
+
The `verify_cell_kzg_proof_batch` handler should verify that `row_commitments` are correct KZG commitments to `cells` by using the cell KZG proofs `proofs`, and the result should match the expected `output`. If any of the commitments or proofs are invalid (e.g. not on the curve or not in the G1 subgroup of the BLS curve), any cell is invalid (e.g. incorrect length or one of the 32-byte blocks does not represent a BLS field element), or any `cell_index` is invalid (e.g. greater than the number of cells for an extended blob), it should error, i.e. the output should be `null`.
0 commit comments