Eth1.X Notes

Candid place to work through ideas focused on 1.X

Set of things for Eth1.X to focus. Piper has one, but there are other things to focus.

Piper - Focus on Stateless Ethereum that transitions into Eth2.

Eth1.X clients are too difficult to get online. The engineering is non-trivial.

We can change this.

https://notes.ethereum.org/cISMnGRMR6-EWka8QLLlYw

Expectations

- Logs are one of the more used features, and the idea that logs are historical
- History of all transactions on the network always availible
- The original Trie structure

The Turbo Geth

Common Problem and individual teams are working on them independantly. By the time that a team is ready to share both have a solution in the works. They may not be ready to integrate and throwing away which ones.

Splitting time between making a client that works and these longer term communication issues.

This split focus doesn't allow us to effectivly work together.

The solution is a proposed structure. Dedicated resources for this research effort and Eth1.x Collaboration.

Seperate teams with specific mandates.

Alexey - Early identified the problem is missing people who are dedicated to the research.

Would be good to have the

Dedicated teams for research that get an implementation to a certain state. The client teams then are handed a semi-finished state solution. And the client teams can focus on one point

Peter -

EIPs. Account abstraction EIP. Very detailed, but the whole thing could not be implemented because of how clients work at a network level. If the research and client teams are too seperate then they will work to develop solutions that are missing information that client devs would know.

Solution is to get knowledgeable people to be in this position.

They can also be built with the right coaching. Solid developers that are capable of doing this stuff. They can learn the blockchain later.

Focus:

- Long term high level vision.
- Short term iterative deliverables.

Required Units of work

Optional units of work

Things that will make it easier for more clients to get on the network.

BeamSync- (Link to jason.carver)

BeamSync gives better user experience for clients. Clients can work soon from booting up.

### The ETH network be less opinionted about database layout.

Get node data is dependant on certain data structures and limits clients on how they can handle the data.

Data providing for witness data. Will we need benevolant data providers to provide for the network.

If there are perverse insentives baked in, it could lead into problems.

Doesn't overly tax the network. Network participants that have an inherent motivation to have the state and provide it.

Alexey - The witnesses will be traveling along the blocks. But who will produce them. Clearly follows that miners should provide this. If they don't provide the witness for their blocks.

Martin - Malicious miners can bloat the proofs if we soley rely on them.

Peter -

Alexey - Witness production could be

Discussion about the pros and cons.

Two problems:

- I want to make a transaction
- some incentivization can solve this to have witness providers.
- If I have 200 transactions then I don't want 200 proofs
- solved by miners.

These problems don't seem like there isn't a solution, but is one we can work on together. Through research

Beam sync is a small step towards stateless clients. It is an opportunity to test the ideas in a safer way.

The zero step, no brainer step is that we should generate witnesses to mainnet blocks. How large are they? What are they like?

Alexey's format it was about 1 Megabyte before the block gas limit

**Try things and fail at them in safe ways.**

If witnesses are 1MB then it is a failed experiment.

Alexey - There are three different paths to reduce the size. This is part of my research limit.

If we doubled the blocktime, and doubled the gas limit would that solve it?

Alexey - Research Topic list
https://ledgerwatch.github.io/Ethereum_1_Research_topics.html

Piper - Research Topic list
https://notes.ethereum.org/cISMnGRMR6-EWka8QLLlYw

What is a safe data size?

https://ethereum-magicians.org/t/eip-2028-transaction-data-gas-cost-reduction/3280/24

Geth -
Finding people to hire is a problem.
If we source some quality engineers.
Sure, but it is hard to do this.

- It would be awesome to have someone to work on these things.

Sourcing talent.

Besu -
Budget for a new person is 95% there. Finding the right people is the problem.

Will -

Alexey -

Peeling off to other people. Remove himself as the bottleneck, and then will look for more people to join.

Trinity -
Working on it

Dedicated resources is one of the biggest things to make this successful.

Research

Context of Eth2 - processess are informing one another.

At least one - actor would need the whole state on their machine. This is long term unsustainable.

Alex - three topics we are more interested in. 1.0 and 2.0
- Particle Gas Cost
- Usecase on Eth1.x using wasm
- Changes that will be needed to transition between 1.0 and 2.0 networks.

Wei
- Versionless EVM