From d7c3043fcb2736898fd9597743c6a821d96923af Mon Sep 17 00:00:00 2001 From: bkchr Date: Wed, 9 Apr 2025 01:11:14 +0000 Subject: [PATCH] deploy: 7f673a4f6a895090f6dfd2372e8db2222f04e00d --- print.html | 159 ++--------------------- proposed/0139-faster-erasure-coding.html | 159 ++--------------------- searchindex.js | 2 +- searchindex.json | 2 +- 4 files changed, 30 insertions(+), 292 deletions(-) diff --git a/print.html b/print.html index a1974ce..ad3cbd7 100644 --- a/print.html +++ b/print.html @@ -967,13 +967,15 @@ As the number of parachains and PoV sizes increase, optimizing the performance of the DA layer becomes increasingly critical.

RFC-47 proposed enabling systematic chunk recovery for Polkadot's DA to improve -efficiency and reduce CPU overhead. However, systematic recovery assumes -very good network connectivity to approximately one-third of validators (plus some -backup tolerance on backers) and still requires re-encoding. Therefore, -we need to ensure the system can handle load in the worst-case scenario.

+efficiency and reduce CPU overhead. However, while it helps under the assumption of +good network connectivity to a specific one-third of validators (modulo some +backup tolerance on backers), it still requires re-encoding. Therefore, +we need to ensure the system can handle load in the worst-case scenario. +The proposed change is orthogonal to RFC-47 and can be used in conjunction with it.

Since RFC-47 already requires a breaking protocol change (including changes to collator nodes), we propose bundling another performance-enhancing breaking -change that addresses the CPU bottleneck in the erasure coding process.

+change that addresses the CPU bottleneck in the erasure coding process, but using +a separate node feature (NodeFeatures part of HostConfiguration) for its activation.

Stakeholders