Pith. sign in

REVIEW 1 cited by

Data Availability Sampling in Ethereum: Analysis of P2P Networking Requirements

Not yet reviewed by Pith; the record is open.

This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.

SPECIMEN: schema-true, not a live event

T0 review · schema-true

One-sentence machine reading of the paper's core claim.

pith:XXXXXXXX · record.json · timestamp

arxiv 2306.11456 v1 pith:HLBACPPK submitted 2023-06-20 cs.NI cs.CR

Data Availability Sampling in Ethereum: Analysis of P2P Networking Requirements

classification cs.NI cs.CR
keywords dataethereumavailabilitynetworkingrequirementssamplingvalidationamount
verification ladder T0 review T1 audit T2 compute T3 formal T4 reserved
0 comments
read the original abstract

Despite their increasing popularity, blockchains still suffer from severe scalability limitations. Recently, Ethereum proposed a novel approach to block validation based on Data Availability Sampling (DAS), that has the potential to improve its transaction per second rate by more than two orders of magnitude. DAS should also significantly reduce per-transaction validation costs. At the same time, DAS introduces new communication patterns in the Ethereum Peer-to-Peer (P2P) network. These drastically increase the amount of exchanged data and impose stringent latency objectives. In this paper, we review the new requirements for P2P networking associated with DAS, discuss open challenges, and identify new research directions.

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Forward citations

Cited by 1 Pith paper

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score.

  1. Polynomial Multiproofs for Scalable Data Availability Sampling in Blockchain Light Clients

    cs.CR 2026-04 unverdicted novelty 6.0

    Polynomial multiproofs verify multiple sampled cells with one aggregated proof over a shared micro-domain, cutting proof bytes, verifier resources, and infrastructure costs by up to 45% in the Avail case study.