An Ethereum 2.0 Relay for proposer-builder separation (PBS) with MEV-boost. Commissioned, built, and put to sea by Blocknative.
go get, or download the latest release here.
$ go install github.com/blocknative/dreamboat
$ dreamboat --help
Documentation can be found here.
What is Dreamboat?
Dreamboat is a relay for Ethereum 2.0, it ships blocks from builders to validators. Dreamboat is for anyone who wants to strengthen the Eth network by running their own relay. Dreamboat’s all-in-one design, modular code base and stunning performance will dazzle beginners and seasoned hackers alike. All aboard!
Eventually Dreamboat will vanish, as if a dream, once in-protocol PBS is live. Until then, it sails the ephemeral seas of block space, delivering its trusted cargo of blocks to validators, guided simply by a lighthouse.
Special thanks to Flashbots for their commiment to open source. This project was orginally based on the relay in Flashobot’s boost-geth-builder and mev-boost-relay. We hope to continue to diverge in implementation over time to help strengthen #RelayDiversity as we continue to work on Dreamboat’s core design goals:
- Extensibility. Dreamboat provides well-factored interfaces that make it easy to change its behavior. We use Go Datastore for its persistence layer, so you can swap out the default BadgerDB store with your favorite database, and provide a clean separation between core relay logic, the beacon-chain client, and the HTTP server.
- Reliability. Work is ongoing implement a supervision-tree architecture in Dreamboat, so that you never miss a block.
- Performance. We have put significant engineering effort into tuning Dreamboat’s performance, and have much, much more in store. The HTTP server’s hot paths are 100% lock-free, concurrency is carefully tuned, and there are ongoing efforts to optimize the garbage collector and speed up signature validation. The result is a ship that doesn’t just sail… it glides.
- Transparency. Dreamboat implements the Relay Data API, so you can audit past proposals. But we take a much broader view of transparency, which includes code transparency. A major cleanup effort is underway to make — and keep — Dreamboat’s code legible. We believe this is an essential part of ensuring transparency and reliability.
We are continuously improving Dreaboat’s runtime performance, standards compliance, reliability and transparency.
Planned Features & Enhancements
The following features and enhancements are in-progress.
- Support for multiple storage backends (Redis, Postgres, BadgerDB, Filesystem, etc.)
- Runtime profiling & tracing endpoint
- Parallel validator-signature verification
- Contention-free execution along hot paths
- Support for multiple beacon clients (in testing stage)
- Support for multiple external block builders
Stuck? Don’t despair! Drop by our discord to ask for help, or just to say hello. We’re friendly! 👋
$ go run cmd/dreamboat
Proposer Builder Separation is a solution to shield validators from the centralizing force the black hole of MEV has released. The next chapter in this saga is to protect builders from too extreme of centralizing forces.
Dreamboat follows semantic versioning. Changes to the REST API are governed by the Flashbots specifications.
main branch is NOT guaranteed to be stable. Use the latest git tag in production!