# High Latency Governance Ethereum governance is a delicate process that relies on rough social consensus of the community, core developers and EF researchers. Improvement proposals (EIPs) are the primary mechanism for proposing new features and communicating these proposed features with the Ethereum Community. ## EIP standardization process The EIP standardization process is a mechanism for proposing new features, for collecting community technical input on an issue, and for documenting the design decisions that have gone into Ethereum. ~EIP-5069 An EIP can be crafted following the EIP format (EIP-1). There are three types of EIPs, A Standard Track (core, networking, Interface & ERC), a Meta-EIP (process changes), and Informational EIPs (provides information or general guidelines). An EIP must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement. The proposed implementation, if applicable, must be solid and must not complicate the protocol unduly. ~ EIP-1 ## EIP Life-cycle ![](https://i.imgur.com/AQQTxNw.png) The first step is vetting your idea with the Ethereum community. Next, the EIP should be posted on ethereum-magicians for community feedback. Once the EIP is proposed and feedback is received, you must seek feedback from EIP editors, core developers, and other interested parties. Last call is set by an EIP reviewer for 14 days later. If the EIP calls for normative changes it will be kicked back to review if not it can be moved to final. If an EIP that sits in draft, review, or last call for more than 6 months is marked stagnant. Living EIPs like EIP-1 do not progress. Throughout the process of Draft→ Final, prototyping and testing may be done in collaboration with EL & CL client teams. Additional discussion and vetting will take place on EL (formerly ACD) & CL bi-monthly calls. If rough consensus can be found the EIP will be marked as CFI (considered for inclusion) for the next hardfork. This is not a guarantee the upgrade will ship. More testing from client teams will be done. In addition, priorities for EIP inclusion in the upcoming hardfork may change as more pressing upgrades may take precedence (see withdrawals & no EOF/4844). ## Advantages & existential risks The advantage to this approach is that only high conviction upgrades enter the protocol because ample time for deliberation and testing can cement social consensus. The downside to this approach is that upgrades take significant time because they require extensive client teams resources, co-ordination, and general community buy-in. There exists a graveyard of CFI EIPs that likely will never get implemented into the Ethereum protocol. In the long run client teams will be funded by private entities with specific preferences that may not overlap with the long-term health of Ethereum. This is an existential risk to Ethereum’s style of off-chain governance.
Last changed by  
 
apriori
262

Read more

Coordination is Power : cross-domain MEV & decentralized sequencing for rollups

This note is a work in progress and should not be mistaken for a finished project

1/2/2024
Mapping the Labryinth

In this article we will briefly reveiw the general types of application deployments to choose from and different types of applications that are interesting to build. Then we will propose a debate game application called the referee, the heart of the article. Finally, we conclude with a succinct analysis. General Types of application deployments App-chain- You have an application or an idea for a suite of applications and would like to guarantee sovereignty or a notion of it for your community who can hard-fork via social consensus should conflict arise. The Cosmos SDK is battletested and comes with IBC & Tendermint, some of the most battletested protocols in crypto. This could also be a rational L3 deployment and benefit from Ethereum’s liquidity. Smart Contracts - SC dapps inherent the security and limitations of the chain you deploy on. As an SC dapp you can focus on a specific PMF for your product. There are also robust security frameworks for auditing and formal verification for more mature languages like Solidity. Cross-chain communication amongst different instances of your dapp fragments liquidity and introduces new trust assumptions. Universal L1 - High DA throughput for specific needs like CLOB, on-chain gaming, Social Media, et al. The death spiral risk is acute early on but persists through the chain’s lifetime. Unknown attack vectors. Difficulty boot-strapping a community. Difficult to bootstrap inital token liquidity without venture funding. Rollups - Rollups move computation (and state storage) off-chain, but keep some data per transaction on-chain. To date, much of the work here focuses on building EVM equivalent rollups though formidable alternatives exist. A key distinction of enshrined rollups aside from on chain da and proof verification is the censorship resistance mechanism. Users have the ability to exit enshrined rollups to L1 via forced inclusion txs, escape hatches, or proposing blocks. Soveriegn rollups rely on social consensus or some form of governance to upgrade via a hard-fork. Both types of rollups can use fraud or validity proofs to guarentee/enforce the validity of the rollup, that its execution is compliant with the state transition function, $\sigma'$ $=$ $\gamma$$($ $\sigma$$,$ $T$$)$where $\sigma'$ is the new state $\gamma$ is the state transition function $\sigma$ is the previous state $T$ is a transaction

4/28/2023
Notes on Arbitrum: reviewing the sequencer

Arbitrum is a classic rollup on Etheruem that uses a Sequencer to collect user txs, order them and then submit batches of transactions to L1. Today, the Sequencers for Nitro and Nova operate as centralized entities maintained by the Arbitrum foundation. Despite this centralization, Arbitrum maintains a trust-minimized security model and censorship resistance. In the common case, the Arbitrum Sequencer receives user transactions and orders them in a sequence with a FCFS (first-come, first-serve) algorithm serving as an input to the execution stage of Arbitrum. Upon receiving the transaction the Sequencer will execute it and deliver the user a receipt or soft-confirmation. Shortly thereafter the Sequencer will collect enough transactions into a batch and post them to L1 by calling the Inbox method addSequencerL2Batch. Only the Sequencer has the authority to call this method. As a result this allows the Sequencer to provide instant soft-confirmations. The transactions have L1 finality once the batch is finalized. In the cases where Sequencer acts malicious, users would need to submit an L2 message via L1 to the delayed inbox. After 24 hours,forceInclusion is called moving the L2 message from the delayed inbox to the core SequencerInbox and is then finalized. Current Drawbacks Latency races Centralized Sequencer

3/21/2023
based MEV-Share

If you have "smart searchers" they could read the different Mempools and match orders. Then match the orders, bundle them and send them to a builder. So basically MEV-Share for all rollup mempools. In this way you would not need a sequencer for ordering, though a local fallback is always helpful. This idea on the surface appears similar to the idea put forth by a couple of Jedis here. Perhaps this lends some credence to the technical feasibality of the following discussion. Disc-V5 supports topics and is used on both CL and EL, so we could create separate p2p channels at any granularity we want (e.g. shared_sequenced_chain1_chain2_slot5, see e.g. how EIP-4844 blobs are each on separate topics. ~ @gakonst I would caution the reader that the following proposal is reductionist and may be technically infeasible and/or too left curve. Feel free to correct any misconceptions or comment. 4337, Private Mempools & Match-Making MEV-Share inserts an intermediate role between searchers and Builders. The Match maker plays a similar role to that of a solver in the Anoma framework. Can you match make userOperations for all rollups?

3/21/2023
Read more from apriori
Published on HackMD