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: README.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,11 +13,7 @@ The Builder orchestrates a series of asynchronous actors that work together to b
13
13
1.**Env** - watches the latest host and rollup blocks to monitor gas rates and block updates.
14
14
2.**Cache** - polls bundle and transaction caches and adds them to the cache.
15
15
3.**Simulator** - simulates transactions and bundles against rollup state and block environment to build them into a cohesive block.
16
-
4.**Submit** - creates a blob transaction from the built block and sends it to the configured submit task.
17
-
18
-
1. Flashbots - builds a Flashbots bundle out of the Signet block which contains Signet transactions, host transactions, and host fills, and submits it to the configured Flashbots endpoint.
19
-
2. Builder Helper - builds a transaction call with the builder helper contract and submits that as a transaction.
20
-
16
+
4.**Submit** - handles preparing and submitting the simulated block.
21
17
5.**Metrics** - records block and tx data over time.
FB ==> | No | HelperSubmit["🏗️ Builder Helper Submit"]
45
-
46
41
end
47
42
48
43
%% Signing
@@ -76,7 +71,7 @@ flowchart TD
76
71
HelperSubmit ==tx hash==> Metrics
77
72
```
78
73
79
-
### Simulation Task
74
+
### 💾 Simulation Task
80
75
81
76
The block building loop waits until a new block environment has been received, and then kicks off the next attempt.
82
77
@@ -86,11 +81,11 @@ Transactions enter through the cache, and then they're sent to the simulator, wh
86
81
87
82
When the deadline is reached, the simulator is stopped, and all open simulation threads are cancelled. The built block is then bundled with the block environment and the previous host header that it was simulated against, and all three are passed along to the submit task.
88
83
89
-
### Submit Task
84
+
### ✨ Submit Task
90
85
91
86
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.
92
87
93
-
If a Flashbots endpoint has _not_ been configured, the Builder will create a raw contract call and submits the transaction 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.
88
+
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.
94
89
95
90
If the block received from simulation is empty, the submit task will ignore it.
96
91
@@ -103,14 +98,14 @@ Finally, if it's non-empty, the submit task attempts to get a signature for the
103
98
The Builder is configured via environment variables. The following values are supported for configuration.
0 commit comments