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
feat: updates bundle prep to track the rollup tx hash (#176)
# feat: updates bundle prep to track the rollup tx hash
This PR updates the bundle preparation functions to track the rollup block's transaction hash through to landing on chain.
There are also some drive-by refactors and doc updates to the bundle prep loop and documentation surrounding env var configuration.
Copy file name to clipboardExpand all lines: README.md
+14-21Lines changed: 14 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,9 +73,7 @@ When the deadline is reached, the simulator is stopped, and all open simulation
73
73
74
74
### ✨ Submit Task
75
75
76
-
If Flashbots endpoint has been configured the Flashbots submit task will prepare a Flashbots bundle out of that Signet block, and then submits that bundle to the Flashbots endpoint.
77
-
78
-
If a Flashbots endpoint has _not_ been configured, the Builder uses the [builder helper contract] and to craft a rollup block transaction and submits that to the default mempool. This mode of operation is only for testing on private networks and should not be used in production, since it can leak sensitive transaction data from the Signet block.
76
+
The Flashbots submit task prepares a Flashbots bundle out of the Signet block and its host transactions and then submits that bundle to the Flashbots endpoint. It sends the hash of the rollup block transaction for to the Metrics task for further tracking.
79
77
80
78
If the block received from simulation is empty, the submit task will ignore it.
81
79
@@ -88,32 +86,29 @@ Finally, if it's non-empty, the submit task attempts to get a signature for the
88
86
The Builder is configured via environment variables. The following values are supported for configuration.
`BUILDER_PORT` | Yes | HTTP port for the Builder (default: `8080`)
103
-
`SEQUENCER_KEY` | Yes | AWS KMS key ID _or_ local private key for sequencer signing
95
+
`SEQUENCER_KEY` | No | AWS Key ID _OR_ local private key for the Sequencer; set IFF using local Sequencer signing instead of remote (via `QUINCEY_URL`) Quincey signing
96
+
`TX_POOL_URL` | Yes | Transaction pool URL (must end with `/`)
97
+
`FLASHBOTS_ENDPOINT` | No | Flashbots API to submit blocks to
98
+
`ROLLUP_BLOCK_GAS_LIMIT` | No | Override for rollup block gas limit
99
+
`MAX_HOST_GAS_COEFFICIENT` | No | Optional maximum host gas coefficient, as a percentage, to use when building blocks
104
100
`BUILDER_KEY` | Yes | AWS KMS key ID _or_ local private key for builder signing
101
+
`AWS_ACCESS_KEY_ID` | No | AWS secret access key ID (required if not using `BUILDER_KEY`)
102
+
`AWS_SECRET_ACCESS_KEY` | No | AWS secret access key (required if not using `BUILDER_KEY`)
103
+
`AWS_DEFAULT_REGION` | No | AWS region for the KMS key in question (required if not using `BUILDER_KEY`)
104
+
`BUILDER_PORT` | Yes | HTTP port for the Builder (default: `8080`)
0 commit comments