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: simulators/eth2/dencun/suites/builder/TESTS.md
+18-32
Original file line number
Diff line number
Diff line change
@@ -65,12 +65,12 @@ Test canonical chain includes deneb payloads built by the builder api.
65
65
66
66
- For each blob transaction on the execution chain, the blob sidecars are available for the beacon block at the same height
67
67
- The beacon block lists the correct commitments for each blob
68
-
- After all other verifications are done, the beacon chain is able to finalize the current epoch
69
68
- Verify that the builder, up to before Deneb fork, has been able to produce blocks and they have been included in the canonical chain
70
-
- Circuit breaker correctly kicks in and disables the builder workflow
71
-
- Implicitly verified by missed-slot count
72
-
- Builder workflow is re-enabled after the circuit breaker timeout
73
-
- There are no more than 10 missed slots on the latest epoch
69
+
- After Deneb fork, the builder must be able to include blocks with blobs in the canonical chain, which implicitly verifies:
70
+
- Consensus client is able to properly format header requests to the builder
71
+
- Consensus client is able to properly format blinded signed requests to the builder
72
+
- No signed block contained an invalid format or signature
73
+
- Test fails with a timeout if no payload with blobs is produced after the fork
74
74
75
75
### - Deneb Builder Builds Block With Invalid Beacon Root, Correct State Root
76
76
@@ -116,12 +116,10 @@ building payloads with invalid parent beacon block root.
116
116
117
117
- For each blob transaction on the execution chain, the blob sidecars are available for the beacon block at the same height
118
118
- The beacon block lists the correct commitments for each blob
119
-
- After all other verifications are done, the beacon chain is able to finalize the current epoch
120
119
- Verify that the builder, up to before Deneb fork, has been able to produce blocks and they have been included in the canonical chain
121
-
- Circuit breaker correctly kicks in and disables the builder workflow
122
-
- Implicitly verified by missed-slot count
123
-
- Builder workflow is re-enabled after the circuit breaker timeout
124
-
- There are no more than 10 missed slots on the latest epoch
120
+
- After Deneb fork, the builder starts producing invalid payloads, verify that:
121
+
- None of the produced payloads are included in the canonical chain
122
+
- Since action causes missed slot, verify that the circuit breaker correctly kicks in and disables the builder workflow. Builder starts corrupting payloads after fork, hence a single block in the canonical chain after the fork is enough to verify the circuit breaker
125
123
126
124
### - Deneb Builder Errors Out on Header Requests After Deneb Transition
127
125
@@ -167,13 +165,9 @@ returning error on header request after deneb transition.
167
165
168
166
- For each blob transaction on the execution chain, the blob sidecars are available for the beacon block at the same height
169
167
- The beacon block lists the correct commitments for each blob
170
-
- After all other verifications are done, the beacon chain is able to finalize the current epoch
171
168
- Verify that the builder, up to before Deneb fork, has been able to produce blocks and they have been included in the canonical chain
172
-
- After Deneb fork, the builder must be able to include blocks with blobs in the canonical chain, which implicitly verifies:
173
-
- Consensus client is able to properly format header requests to the builder
174
-
- Consensus client is able to properly format blinded signed requests to the builder
175
-
- No signed block contained an invalid format or signature
176
-
- There are no more than 1 missed slots on the latest epoch
169
+
- After Deneb fork, the builder starts producing invalid payloads, verify that:
170
+
- None of the produced payloads are included in the canonical chain
177
171
178
172
### - Deneb Builder Errors Out on Signed Blinded Beacon Block/Blob Sidecars Submission After Deneb Transition
179
173
@@ -219,12 +213,10 @@ returning error on unblinded payload request after deneb transition.
219
213
220
214
- For each blob transaction on the execution chain, the blob sidecars are available for the beacon block at the same height
221
215
- The beacon block lists the correct commitments for each blob
222
-
- After all other verifications are done, the beacon chain is able to finalize the current epoch
223
216
- Verify that the builder, up to before Deneb fork, has been able to produce blocks and they have been included in the canonical chain
224
-
- Circuit breaker correctly kicks in and disables the builder workflow
225
-
- Implicitly verified by missed-slot count
226
-
- Builder workflow is re-enabled after the circuit breaker timeout
227
-
- There are no more than 10 missed slots on the latest epoch
217
+
- After Deneb fork, the builder starts producing invalid payloads, verify that:
218
+
- None of the produced payloads are included in the canonical chain
219
+
- Since action causes missed slot, verify that the circuit breaker correctly kicks in and disables the builder workflow. Builder starts corrupting payloads after fork, hence a single block in the canonical chain after the fork is enough to verify the circuit breaker
228
220
229
221
### - Deneb Builder Builds Block With Invalid Payload Version
230
222
@@ -270,13 +262,9 @@ version is outdated (capella instead of deneb).
270
262
271
263
- For each blob transaction on the execution chain, the blob sidecars are available for the beacon block at the same height
272
264
- The beacon block lists the correct commitments for each blob
273
-
- After all other verifications are done, the beacon chain is able to finalize the current epoch
274
265
- Verify that the builder, up to before Deneb fork, has been able to produce blocks and they have been included in the canonical chain
275
-
- After Deneb fork, the builder must be able to include blocks with blobs in the canonical chain, which implicitly verifies:
276
-
- Consensus client is able to properly format header requests to the builder
277
-
- Consensus client is able to properly format blinded signed requests to the builder
278
-
- No signed block contained an invalid format or signature
279
-
- There are no more than 1 missed slots on the latest epoch
266
+
- After Deneb fork, the builder starts producing invalid payloads, verify that:
267
+
- None of the produced payloads are included in the canonical chain
280
268
281
269
### - Deneb Builder Builds Block With Invalid Beacon Root, Incorrect State Root
282
270
@@ -327,10 +315,8 @@ produced locally and results in an empty slot.
327
315
328
316
- For each blob transaction on the execution chain, the blob sidecars are available for the beacon block at the same height
329
317
- The beacon block lists the correct commitments for each blob
330
-
- After all other verifications are done, the beacon chain is able to finalize the current epoch
331
318
- Verify that the builder, up to before Deneb fork, has been able to produce blocks and they have been included in the canonical chain
332
-
- Circuit breaker correctly kicks in and disables the builder workflow
333
-
- Implicitly verified by missed-slot count
334
-
- Builder workflow is re-enabled after the circuit breaker timeout
335
-
- There are no more than 10 missed slots on the latest epoch
319
+
- After Deneb fork, the builder starts producing invalid payloads, verify that:
320
+
- None of the produced payloads are included in the canonical chain
321
+
- Since action causes missed slot, verify that the circuit breaker correctly kicks in and disables the builder workflow. Builder starts corrupting payloads after fork, hence a single block in the canonical chain after the fork is enough to verify the circuit breaker
- Since action causes missed slot, verify that the circuit breaker correctly kicks in and disables the builder workflow. Builder starts corrupting payloads after fork, hence a single block in the canonical chain after the fork is enough to verify the circuit breaker`)
0 commit comments