Ethereum's Portal Network

Building Ethereum Execution & Conensus Lightclients | account managed by @Kolby_ML

[Ethereum's Portal Network @ethportalnet]

We are making progress on our Rust Ethereum Execution client "Trin Execution" when it can keep up with the head of the chain, we will start gossiping head archival state onto our Portal State testnet!, The goals of Portal State is varied but one used case will be as a wallet 1/3

[Kolby ML (Moroz Liebl) @Kolby_ML]

I finished implementing syncing to the latest finalized block using the beacon-api through the CL client I am running for syncing Trin Execution a new Ethereum Execution client being built to use Portal as the P2P layer instead of devp2p enabling lighter Execution clients to be built.

Now I just need to implement the handling for the ~64 non-finalized blocks, handling re-orgs, sidechains etc. After that is done, we will start gossiping latest Ethereum head state to the

[Ethereum's Portal Network @ethportalnet]

@RuzhyoX @peter_szilagyi That is what EF’s Portal is for distributing block history, state, etc to divide the storage requirements amongst the node set instead of requiring each node to hold a full copy individually. Maintaining access for all but will a lower individual storage cost

[Ethereum's Portal Network @ethportalnet]

@lightclients Portal solves this for a majority of users/usercases. The fact is today the only way to access authenticated chain data is by running a fullnode which isn’t that accessible to the average user. Portal will be integrated into user facing apps. Which solves the UX

[Ethereum's Portal Network @ethportalnet]

@zkcat_eth @gakonst Helios uses a centralized JSON-RPC but runs a consensus light client to prove data. I mean a wallet with an embedded Portal Client. Which exposes the full json-rpc decentralized. https://t.co/p7w1ewY722

[Ethereum's Portal Network @ethportalnet]

@peter_szilagyi @TimBeiko Hence our only “hardcoded” solution is for pre-merge blocks.

[Ethereum's Portal Network @ethportalnet]

@peter_szilagyi @TimBeiko We have solutions for post-merge the PR’s are still not merged yet, we are planning to merge then after devcon. You can use the beacon chain historical accumulators for post merge blocks, so not duplicating that would be good as you can just request it from the CL client

[Ethereum's Portal Network @ethportalnet]

@Sebasti04989541 @moo9000 At EF Portal will give mobile devices full access to the Ethereum protocol very lighly. So I think Portal solved these problems airgap problems for mobile devices

[Ethereum's Portal Network @ethportalnet]

@moo9000 @Sebasti04989541 What is the specific shortcomings if you don’t mind me asking

[Ethereum's Portal Network @ethportalnet]

@peter_szilagyi Check this out! https://t.co/KWC1fIPhIc and you can read our history spec to learn how we use it in https://t.co/Am5rE2Tq57

[Ethereum's Portal Network @ethportalnet]

@peter_szilagyi Yes EF Portal’s Portal History network does this already

[Kolby ML (Moroz Liebl) @Kolby_ML]

@ethportalnet using Trin Execution we are now able to sync to almost latest. I have implemented the initial layout of the engine api, soon we should be able to gossip latest state on the State Portal Network and track latest while not using devp2p #eip-4444

[Ethereum's Portal Network @ethportalnet]

@0xemre EIP-4444’s manages History growth not State Growth. We want EIP-4444’s too!

[Ethereum's Portal Network @ethportalnet]

@trent_vanepps @5dayoldburrito @pipermerriam I don’t think Piper wants to use Twitter, but questions can be directed towards @ethportalnet

[trent.eth @trent_vanepps]

gas limits increase this, slot times decrease that..

how about EIP-4444 first - then let's talk?

[Kolby ML (Moroz Liebl) @Kolby_ML]

My talk "Decentralizing access to Ethereum utilizing Ethereum's Portal Networks" was accepted under the Core Track at @EFdevcon!

Portal @ethportalnet will empower Ethereum's Protocol to be more accessible

See you in Bangkok, November 12-15
https://t.co/ylxiCmxbUd

[Ethereum's Portal Network @ethportalnet]

@drownwave @drmllr @icpp_pro 3) every full node doesn’t need to store a copy of blocks to maintain access to them, this responsibility can be distributed lowering the cost to access Ethereum in a decentralized manner for everyone. To continue scaling Ethereum we need to innovate and this is one innovation

[Ethereum's Portal Network @ethportalnet]

@drownwave @drmllr @icpp_pro 2) Instead of each full node storing the full block history they will store a subsection and be able to look up history they don’t have on the Portal Network. An R&D project trying to remove the constraints of devp2p well lowering the barrier to participate in Ethereum

[Ethereum's Portal Network @ethportalnet]

@drownwave @drmllr @icpp_pro On the roadmap you can see a requirement for History Expiry (EIP-4444) is Alternative History Providers (Portal). This is Portal’s Twitter account @ethportalnet we are a project at the EF. One of goals is to distribute Ethereums History,State,etc to multiple p2p networks.