Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASA Idea
Do not introduce a new gossipsub topic for BALs. Instead encode BALs as BALs only rows of the EIP-8142 payload blobs and leverage existing PeerDAS data-column subnets plus gossipsub’s partial messages to propagate only the BAL-bearing cells early.
Concretely:
Builder constructs payload blobs as in BiB, but with a layout that keeps BALs in isolated blobs
Builder commits to its blobs with KZG commitments in the bid
Once the beacon block containing the accepted bid is available the builder advertises availability for the BAL bearing cells on all data column subnets. In contrast to other payload blobs it is safe to builder to start propagation of BAL cells before the attestation deadline
Peers that want early BAL access send request bitmaps for those BAL-bearing cells
After the remaining payload is safe to reveal the builder advertises the remaining payload cells as available
For example, for some peer its column’s view might be the following:
For its custody columns, it requests every cell it needs for normal PeerDAS custody:
request bitmap for C5: [1, 1, 1, 1, 1, 1, 1, 1, …]
request bitmap for C7: [1, 1, 1, 1, 1, 1, 1, 1, …]
For non-custody columns it requests only BAL-bearing cells:
request bitmap for non-custody columns: [1, 1, 0, 0, 0, 0, 0, 0, …]
From builder’s perspective it advertises only BAL-bearing cells for all columns before attestation deadline:
builder's avail bitmap for all columns: [1, 1, 0, 0, 0, 0, 0, 0, …]
After attestation deadline builder advertises all cells for all columns:
builder's avail bitmap for all columns: [1, 1, 1, 1, 1, 1, 1, 1, …]
Benefits:
Avoids introducing another global gossip topic solely for BALs
Reuses PeerDAS data-column propagation
Aligns with BiB model
May be more efficient than propagating the full BAL message especially for large BALs
Peers non-interested in receiving BALs can signal about that in their request bitmaps, thus saving bandwidth
Drawbacks:
Blob is 128KiB with effective capacity about 124KiB. If BALs are much smaller capacity is wasted
Peers interested in receiving BALs now need to subscribe to all column subnets
—
Brief partial messages and cell-level deltas context
Peers advertise which cells they have with availability bitmaps and which cells they want with request bitmaps
Each message contains a group id which in our case corresponds to the block root and helps peers identify which block the partial message corresponds to
Once peers have exchanged bitmaps, they can request the specific parts of the message they are interested in
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | EIPIP Meeting #128, July 08, 2026 | 0 | 7 | 08-07-2026 |
| 2 | ERC-8100: Representable Contract State | 0 | 5 | 08-07-2026 |
| 3 | ERC-8335: Account-Level Transfer With Authorization | 0 | 7 | 10-07-2026 |
| 4 | All Core Devs - Testing (ACDT) #87, July 13, 2026 | 0 | 5 | 10-07-2026 |
| 5 | All Core Devs - Consensus (ACDC) #182, July 9 2026 | 0 | 7 | 10-07-2026 |
| 6 | EIP-7906: Transaction Assertions via State Diff Opcode | 0 | 3 | 08-07-2026 |
| 7 | RPC Standards # 30, July 13, 2026, | 0 | 5 | 10-07-2026 |
| 8 | EIP-7906: Transaction Assertions via State Diff Opcode | 0 | 7 | 09-07-2026 |
| 9 | EIP-7723: Network Upgrade Inclusion Stages | 0 | 6 | 09-07-2026 |
| 10 | ERC-8313: Protocol Interaction Manifest | 0 | 7 | 08-07-2026 |