Skip to content

PeerDAS - Tracking Issue #4983

@AgeManning

Description

@AgeManning

Description

This is a tracking issue for the work that is being undertaken on building out Data Availability Sampling.

This will be updated and edited as we go.

Instructions for running a DAS devnet can be found in this gist.

Main PR to unstable:

Devnet 5

TODO(das)

Initial implementation

Data format and distribution (#5050)

  • Add ColumnSidecar type
  • Extend blobs horizontally with dummy data (0x{random_uniq_bits}...{col_id}) and distribute to column subnets
  • Create 32 column subnets NUM_COLUMN_SUBNETS
  • Compute subnets to subscribe to based on node_id (see att example here)
  • Node to subscribe to only CUSTODY_REQUIREMENT column subnets

Data Column Custody

Sampling

Syncing

Misc

peerdas-devnet-1

peerdas-devnet-2

peerdas-devnet-3

Post-Pectra (Sampling, 2D PeerDAS etc)

Current behaviour not specified by consensus-specs

  • Only supernode performs reconsturctions once >50% of columns received
  • LossyDAS implementation
  • Re-process DataColumnsByRoot requests and respond when columns are ready

Metadata

Metadata

Assignees

Labels

NetworkingdasData Availability Samplingmajor-taskA significant amount of work or conceptual task.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions