remove LossyDAS naming from spec

While the technique was introduced as LossyDAS, we don't need the name
in the specification itself.

Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
This commit is contained in:
Csaba Kiraly 2024-05-29 11:08:52 +02:00
parent a04cd87c38
commit 5f3beca871
No known key found for this signature in database
GPG Key ID: 0FE274EE8C95166E

View File

@ -245,7 +245,7 @@ To custody a particular column, a node joins the respective gossip subnet. Verif
At each slot, a node SHOULD select at least `SAMPLES_PER_SLOT` column IDs for sampling. It is recommended to use uniform random selection without replacement based on local randomness. Sampling is considered successful if the node manages to retrieve all selected columns.
Alternatively, a node MAY use LossyDAS selecting more than `SAMPLES_PER_SLOT` columns while allowing some missing, respecting the same target false positive threshold (the probability of successful sampling of an unavailable block) as dictated by `SAMPLES_PER_SLOT`. The table below shows the number of samples and the number of allowed missing columns for this threshold.
Alternatively, a node MAY use a method that selects more than `SAMPLES_PER_SLOT` columns while allowing some missing, respecting the same target false positive threshold (the probability of successful sampling of an unavailable block) as dictated by `SAMPLES_PER_SLOT`. The table below shows the number of samples and the number of allowed missing columns for this threshold.
| Allowed missing (L) | 0| 1| 2| 3| 4| 5| 6| 7| 8|
|----------------------------------------|--|--|--|--|--|--|--|--|--|