# Development next steps for PBS, roundtable at DevCon

**URL:** https://collective.flashbots.net/t/development-next-steps-for-pbs-roundtable-at-devcon/438
**Category:** Events
**Tags:** mev-boost
**Created:** [October 3, 2022, 9:38pm UTC](https://collective.flashbots.net/t/development-next-steps-for-pbs-roundtable-at-devcon/438 "2022-10-03T21:38:35Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![guayabyte](https://collective.flashbots.net/user_avatar/collective.flashbots.net/guayabyte/32/4_2.png) [@guayabyte](https://collective.flashbots.net/u/guayabyte)
#### Post date: [October 3, 2022, 9:38pm UTC](https://collective.flashbots.net/t/development-next-steps-for-pbs-roundtable-at-devcon/438/1 "2022-10-03T21:38:36Z")

</div>

# Hosts

@guayabyte, @kailin, @jtraglia and @ralexstokes

# Date

October 14th, 2 pm to 5 pm, Bogotá Time.

# Venue

[Hilton Corferias](https://www.hilton.com/en/hotels/bogcchh-hilton-bogota-corferias/), Rocío Room  
A small working space with limited seating.

# Attendees

Invitation only. If you want to participate, contact @kailin.

- 1 or 2 developers from every consensus and execution client team.
- 10 seats for developers, testers and security researchers from Ethereum Foundation.
- 5 seats for people from other organizations who have collaborated with mev-boost and PBS.

# Proposed agenda

- Present the current status of the MEV-Boost architecture and the adoption numbers. 15 minutes.
- Summary of the open research questions for PBS. 15 minutes.
- Development next steps for decentralization and censorship resistance. 1 hour 30 minutes.
- Security risks and mitigations. 1 hour.

---

<div class="post-metadata">

### Author: ![kailin](https://collective.flashbots.net/user_avatar/collective.flashbots.net/kailin/32/54_2.png) [@kailin](https://collective.flashbots.net/u/kailin)
#### Post date: [October 3, 2022, 9:54pm UTC](https://collective.flashbots.net/t/development-next-steps-for-pbs-roundtable-at-devcon/438/2 "2022-10-03T21:54:35Z")

</div>

2 invitees to add interested in contributing from Blocknative:

Murat Akdeniz (@muralight - product manager) and Taylor Dawson (@drapier - engineer)

---

<div class="post-metadata">

### Author: ![kailin](https://collective.flashbots.net/user_avatar/collective.flashbots.net/kailin/32/54_2.png) [@kailin](https://collective.flashbots.net/u/kailin)
#### Post date: [October 26, 2022, 4:42pm UTC](https://collective.flashbots.net/t/development-next-steps-for-pbs-roundtable-at-devcon/438/4 "2022-10-26T16:42:45Z")

</div>

Flashbots met with Ethereum ecosystem partners and contributors of MEV-Boost during DevCon Bogotá to align on decentralizing proposer/builder separation as a community. Below is a summary of discussed priorities, updates since Devcon, and next steps we’ll continue to collaborate toward. _Please comment with any additional updates or information!_

## Summary of Priorities

- [Inclusion list / partial block auction implementation](https://hackmd.io/5rrA0KfBTFS7uvIEg41Lag)
- [Block scoring and payment proofs](https://collective.flashbots.net/t/block-scoring-for-mev-boost-relays/202/16)
- Local and remote block comparison
- Relay Monitor
- Consequences for misbehavior relays
- SSZ encoding
- MEV-Boost security audit
- ValidatorRegistration and [Data API Privacy](https://collective.flashbots.net/t/privacy-concerns-with-data-api/568/2)

## Updates Since Devcon

- Flashbots continues to maintain MEV-Boost via an ‘open R&D’ process, where releases and updates will be shared openly on the [Flashbots Forum.](https://collective.flashbots.net/c/relays/15)
- We are iterating on inclusion list or partial block auction design decisions which ideally will not require consensus client integration.
- We’ve doubled the boost-relay builder block submission rate limit to 600/5min (2/sec), which is pretty optimal for block builders.
- [Announced mev-boost-relay v0.11.0 - notable feature: block submission cancellations](https://collective.flashbots.net/t/announcing-mev-boost-relay-v0-11-0-notable-feature-block-submission-cancellations/604).
- [We’ve open sourced our sync-proxy](https://collective.flashbots.net/t/open-sourcing-sync-proxy/626), which allows EL clients (i.e. geth, nethermind, etc.) to be driven by multiple beacon nodes for greater redundancy.

## Community Updates

- [Prysm](https://github.com/prysmaticlabs/prysm/pull/11557) (Terence) and [Geth](https://github.com/ethereum/go-ethereum/pull/25998) (Marius) prototyping features to enable the proposer to select between a local block and a builder block with the highest fee.
- New relay and builder entrants: The [@Rook](https://twitter.com/Rook) relay undergoing load testing, [Builder0x69](https://medium.com/@builder0x69/first-10-000-blocks-and-new-features-8b3bb0e5b4a7) considering entering.
- BloXRoute [discussion regarding validator specified censorship](https://collective.flashbots.net/t/discussion-regarding-validator-specified-censorship/615).
- Forum: [A Full-Block-Censoring FlashBots Relay For Censorship-Sensitive Proposers](https://collective.flashbots.net/t/request-a-full-block-censoring-flashbots-relay-for-censorship-sensitive-proposers/593)

## Requested Next Steps

- Continue discussion on [incentivizing relays](https://collective.flashbots.net/t/ideas-for-incentivizing-relays/586) to increase competition.
- Align on the standardization of block scoring and [adding bid proofs](https://github.com/ethereum/builder-specs/pull/51) to the builder bid response [https://collective.flashbots.net/t/block-scoring-for-mev-boost-relays/202/16](https://collective.flashbots.net/t/block-scoring-for-mev-boost-relays/202/16).
- Continue iteration of [inclusion list or partial block auction design decisions](https://hackmd.io/5rrA0KfBTFS7uvIEg41Lag) by answering open questions.
- Contribute toward the [MEV-Boost development philosophy](https://collective.flashbots.net/t/mev-boost-development-philosophy/505).
- Implement the changes required for local and remote block building comparison.
- Review the inclusion list proposal: [How much can we constrain builders without bringing back heavy burdens to proposers?](https://ethresear.ch/t/how-much-can-we-constrain-builders-without-bringing-back-heavy-burdens-to-proposers/13808)

## Resources

- Vitalik’s ETHResearch Post: [How much can we constrain builders without bringing back heavy burdens to proposers?](https://ethresear.ch/t/how-much-can-we-constrain-builders-without-bringing-back-heavy-burdens-to-proposers/13808)
- Forum: [Toward an open research and development process for MEV-Boost](https://collective.flashbots.net/t/toward-an-open-research-and-development-process-for-mev-boost/464)
- Forum: [MEV-Boost Development Philosophy](https://collective.flashbots.net/t/mev-boost-development-philosophy/505)
- Forum: [Ideas for Incentivizing Relays](https://collective.flashbots.net/t/ideas-for-incentivizing-relays/586)
- Forum: [Privacy Concerns with Data API](https://collective.flashbots.net/t/privacy-concerns-with-data-api/568)
