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: docs/flashbots-auction/advanced/gas-fee-refunds.md
+11-59Lines changed: 11 additions & 59 deletions
Original file line number
Diff line number
Diff line change
@@ -4,37 +4,37 @@ title: Gas Fee Refunds
4
4
5
5
## Introduction
6
6
7
-
Searchers and private transaction API users are automatically eligible to receive gas fee refunds. If Flashbots can include a bundle on chain for a lower price, you are eligible to receive a refund.
7
+
Searchers and private transaction API users are automatically eligible to receive gas fee refunds. If a bundle can be included on chain for a lower price, you are eligible to receive a refund.
8
8
9
9
Gas fee refunds do not change how bundles are executed and searchers do not need to make any changes to be eligible for them.
10
10
11
11
## Where do refunds come from
12
12
13
13
Gas fee refunds include both priority fees and coinbase transfers.
14
14
15
-
In an optimal case, searchers are refunded the difference between their bid and the bid of the next-best bundle or transaction targeting the same state. Ie. the refund effectively results in the searcher paying the second price. In practice, searchers will receive some fraction of this amount depending on how much profit the Flashbots builder makes.
15
+
In an optimal case, searchers are refunded the difference between their bid and the bid of the next-best bundle or transaction targeting the same state. Ie. the refund effectively results in the searcher paying the second price. In practice, searchers will receive some fraction of this amount depending on how much profit BuilderNet makes.
16
16
17
17
## Which bundles receive refunds
18
18
19
-
Flashbots provides refunds for bundles in blocks landed by the Flashbots block builder. Whether a bundle receives a refund depends on a few factors that vary from block to block:
19
+
Flashbots provides refunds for bundles in blocks landed by BuilderNet. Whether a bundle receives a refund depends on a few factors that vary from block to block:
20
20
* How much network congestion and competition there was
21
-
* Whether the Flashbots builder made a profit and how much
21
+
* Whether BuilderNet made a profit and how much
22
22
* How much the specific bundle contributed to the value of the block
23
-
* If the bundle was sent directly to Flashbots, or shared with other block builders by the searcher
23
+
* If the bundle was sent directly to Flashbots or BuilderNet, or shared with other block builders by the searcher
24
24
25
25
Note that transactions seen in the public mempool are excluded and bundles containing only public mempool transactions do not receive refunds.
26
26
27
27
## How to maximize both refunds and speed
28
28
29
-
Transactions which are sent directly to the Flashbots Builder via the Bundle Relay, and not multiplexed _by the searcher_ to other block builders, are likely to receive higher refunds. This is because they increase the profit of the Flashbots builder which is used to provide refunds.
29
+
Transactions which are sent directly to the Flashbots Bundle Relay or BuilderNet, and not multiplexed _by the searcher_ to other block builders, are likely to receive higher refunds. This is because they increase the profit of BuilderNet which is used to provide refunds.
30
30
31
-
The Flashbots block builder does not land 100% of blocks. In order to land bundles in all blocks, searchers can ask Flashbots to share their bundles with other block builders in cases where the Flashbots builder does not win a block. Flashbots will automatically share with all specified builders on the searcher's behalf.
31
+
BuilderNet does not land 100% of blocks. In order to land bundles in all blocks, searchers can ask Flashbots to share their bundles with other block builders in cases where BuilderNet does not win a block. Flashbots will automatically share with all specified builders on the searcher's behalf.
32
32
33
33
### Smart multiplexing
34
34
35
35
To share bundles with other builders, add the `builders` field to your `eth_sendBundle` request. The `builders` field accepts a list of strings which correspond to the "name" tags of [registered builders](https://github.com/flashbots/dowg/blob/main/builder-registrations.json).
36
36
37
-
All `eth_sendBundle` requests are shared with the Flashbots builder. They are multiplexed to other block builders at the end of the slot if the Flashbots builder determines it will not win that block.
37
+
All `eth_sendBundle` requests are shared with BuilderNet. They are multiplexed to other block builders at the end of the slot if BuilderNet determines it will not win that block.
38
38
39
39
For example:
40
40
@@ -55,7 +55,7 @@ For example:
55
55
}
56
56
```
57
57
58
-
Searchers can also use `mev_sendBundle` to multiplex bundles if they prefer. Though this method is more complex and not necessary for gas fee refunds.
58
+
Searchers can also use `mev_sendBundle` to multiplex bundles if they prefer. This method is more complex and not necessary for gas fee refunds.
59
59
60
60
_Note: Smart multiplexing has a 1% rate of false positives, meaning that in 1% of MEV-Boost blocks there is a risk that searcher bundles will not be landed._
61
61
@@ -65,63 +65,15 @@ To view bundle stats on multiplexed `eth_sendBundle` requests, use the `flashbot
65
65
66
66
## How are refunds calculated
67
67
68
-
The Flashbots builder uses a refund rule to retroactively calculate refunds for all bundles landed in its blocks.
69
-
70
-
The refund rule aims to have bundles make the minimum net payment so that bidding optimally is as straight forward as possible. We do this by measuring the contribution of bundles above the other bundles the builder has received, and refunding as much of that as possible.
71
-
72
-
Bundles sent by the same signer will be treated as non-competitive.
73
-
74
-
See the [explainer](https://collective.flashbots.net/t/refund-rule-wat-dis-how-to-and-faq/4049/2) for more details about how to bid and interact with the refund rule.
75
-
76
-
### The Flat Tax Rule
77
-
78
-
-**$B(T)$** is the most profitable block produced from bundles in $T$.
79
-
-**$v(T)$** is the value of $B(T)$.
80
-
-**$b_i(T)$** is the payment of all bundles sent by identity $i$ if block $B(T)$ is realized.
81
-
-**$\mu_i(T) = \min\{b_i(T), v(T) - v(T \setminus \{i\})\}$** is the marginal contribution of all bundles sent by identity $i$ if $B(T)$ is realized. We bound the marginal contribution so that the net payment can't be negative.
82
-
-**$c$** is the amount the builder pays to the proposer to win the block.
83
-
84
-
$$
85
-
\phi_i(T, c) = \frac{\mu_i(T)}{\sum_j \mu_j(T)} \min\{v(B(T)) - c, \sum_j \mu_j(T)\}
86
-
$$
87
-
88
-
So the net payment per identity (assuming it's included) is $p_i(T) = b_i(B(T)) - \phi_i(T, c)$.
89
-
90
-
Notice that if the block generates enough value after paying the proposer, everyone should be refunded their contribution, meaning everyone pays the minimum they need to pay to beat competition.
91
-
92
-
### Identity constraint
93
-
94
-
To avoid the rule being gamed by submitting bundles from multiple identities, we impose an additional constraint that no set of identities can receive in total more refunds than they contribute to the block.
to be the joint marginal contribution of the identities in $I$ to the block. Then we choose rebates that are minimally different from the flat-tax rule subject to the constraint that they don't rebate a set of bundles more in total than its joint marginal contribution. This means the vector of rebates $\psi(T, c)$ solves
\text{subject to} \sum_{i\in I} r_i \leq \mu_I(T) \text{ for each } I \subseteq B(T),
110
-
$$
111
-
112
-
$$
113
-
\sum_i r_i \leq v(T) - c
114
-
$$
115
-
116
-
where $\phi(T, c)$ are the orginal flat-tax rebates as defined above.
68
+
BuilderNet uses a refund rule to retroactively calculate refunds for all bundles landed in its blocks. For more information, see the [BuilderNet docs](https://buildernet.org/docs/refunds).
117
69
118
70
## Who receives refunds
119
71
120
72
By default, the refund recipient is the signer used on the `eth_sendBundle`, `mev_sendBundle`, or `eth_sendPrivateTransaction` request. You can delegate your recipient to a different address using the `flashbots_setFeeRefundRecipient` API.
121
73
122
74
## How to track refunds
123
75
124
-
Refunds are tracked from a start date of July 8, 2024. Refunds are sent to recipients in batches, the first batch originated from our builder address `0xdf99A0839818B3f120EBAC9B73f82B617Dc6A555` while newer batches originate from [`refunds.buildernet.eth`](https://etherscan.io/address/0x62a29205f7ff00f4233d9779c210150787638e7f).
76
+
Refunds are tracked from a start date of July 8, 2024. Refunds are sent to recipients in batches, the first batch originated from the Flashbots builder address `0xdf99A0839818B3f120EBAC9B73f82B617Dc6A555` while newer batches originate from [`refunds.buildernet.eth`](https://etherscan.io/address/0x62a29205f7ff00f4233d9779c210150787638e7f).
125
77
126
78
Track your refunds using the [`flashbots_getFeeRefundTotalsByRecipient`](/flashbots-auction/advanced/rpc-endpoint#flashbots_getfeerefundtotalsbyrecipient) RPC method or the [refund dashboard](https://app.hex.tech/9eb1e790-53f7-4c16-be76-4a22c1aa7d17/app/0c2d34ef-1304-481a-b3d6-b773ce9e0e19/latest) on Dune.
0 commit comments