What stakeholder category do you represent?
e.g. wallet devs, DEXs, bridges
RPC Providers
What do you view as the top priority theme in this fork & why?
e.g. censorship resistance, scaling the L1, improving UX, etc.
Scaling the L1 can bring additional traffic but may also increase infrastructure costs. Improving UX can onboard more users and attract new customers. Censorship resistance helps maintain Ethereum’s credible neutrality, making it attractive to institutions seeking to avoid counterparty risk.
Which EIP(s) do you favor as a headliner for Glamsterdam?
note: the process is aiming for one EIP each for the consensus and execution layers
We have no official stance.
If known, what specific impacts would this have on your community?
e.g. this EIP would enable our users to…
Provable RPC responses may provide some additional security and piece of mind to our customers knowing that the data they are receiving is unaltered. However, this EIP focuses mostly on logs and receipts where as most of our customer’s headaches comes from the outputs of poorly standardized methods like debug_traceBlockByX.
Does anything make this an urgent feature for you or your community?
e.g. not urgent, but it would streamline…
No.
The leading headliners among client teams are described in a series of blog posts listed here. Do you have any concerns about any particular proposal?
e.g. they’re all good eggs
No concerns.
Any additional comments?
![]()