Allow setting a minimum gas used value to determine whether or not to use a block supplied by the builder API
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or entry points to begin with. First map how builder API blocks are evaluated and where validator configuration is handled, then define the minimum-gas setting and its acceptance behavior before implementing tests and the change.
Written by the indexing model from the issue text.
Description
In a similar spirit to https://github.com/flashbots/mev-boost/issues/273
I think users should be able to express an opinion about the fullness of a block. Currently, block builders will often leave transactions out of a block when volatility is high. The reasons for this are not fully known, however what is know is that blocks have a lower gas used than would otherwise be the case.
One of the purported benefits of delegating block building is that the block builder should be able to fill the block with more transactions than a solo validator.
This would allow solo validators to express their opinions.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 295
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flashbots/mev-boost
-
uint64 underflow in getHeader msIntoSlot: request arriving before slot start silently skips all relaysPossibly taken @vsaraikin claimed this 103 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug: JSON log format breaks on registerValidator due to *http.Request field containing func() typePossibly taken @dom-nie claimed this 227 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
`GET /eth/v1/builder/header/...` `duration > 950 ms`Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
All issues in flashbots/mev-boost
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
ViewData can pair the in-flight proposal with the prepared flag of another proposalPossibly taken @HagarMeir claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hyperledger/SmartBFT#710 ·
Maintainers usually reply within 1 day
-
agent-butler-finding chore
Difficulty 1/5 Under an hour Newbie friendliness 90/100
jordansmall/spindrift#5575 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
open-telemetry/opentelemetry-go-compile-instrumentation#1512 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
OpenPrinting/go-mfp#124 ·
Maintainers usually reply within 1 day