Penalize peers whose fetched data column sidecars fail the chain checks

Aperta
#815 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 6 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
47/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

Start with crates/net/p2p/src/beacon/column_checks.rs and the two response handlers in crates/net/p2p/src/req_resp/handlers.rs named in the issue. Trace how check verdicts reach those handlers, then read the existing peer reporting or suspicion and backoff paths. Done means a forged column from a by-root response reports its serving peer, with a test asserting that result.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

The problem. A DataColumnsByRoot or DataColumnsByRange answer goes through column_checks::check_and_forward (crates/net/p2p/src/beacon/column_checks.rs:322), which takes no PeerId. Both response handlers know the peer and drop it at the call:

  • handle_data_column_sidecars_range_response (crates/net/p2p/src/req_resp/handlers.rs:2466, call at :2505);
  • handle_data_column_sidecars_response (handlers.rs:2530, call at :2567).

A fetched sidecar can be refused on KZG proofs, inclusion proof, header signature, proposer or shape. Such a sidecar is counted in lean_data_columns_rejected_total and nothing else. The peer that served it is not scored, disconnected or deprioritized. Column lookups pick peers at random on retry, so a peer serving forged columns stays as likely to be asked again as any other.

The cost today. Each forged column costs the node CPU. lambdaclass/ethlambda#754 verifies a block's columns in KZG sub-batches of at most 16 and re-checks a failed batch column by column. One forged column per sub-batch then costs about 64 ms of CPU per 16 columns at 9 blobs, against about 51 ms for checking them one at a time as main did. Both figures are computed from measured single-thread batch timings. That is bounded, but nothing stops it repeating.

Why it is out of #754's scope. The gap predates the PR: main's per-sidecar checks did not penalize the sender either. #754 changes how the checks are paid for, not what happens to the source.

What a fix would look like.

  • Carry the source of a check_and_forward call into the group's verdicts: a peer for req/resp answers, and gossip, parked replay or this node's own for the rest.
  • On a Reject outcome from a peer's answer (not an Ignore, and not a parked replay, whose original sender is long gone), report that peer. That could mean a disconnect, or the same suspicion and backoff range sync applies to peers that serve bad data, so it is not asked again for a while.
  • A test can feed a forged column through a fake by-root answer and assert the peer is reported.

Related. lambdaclass/ethlambda#803 (open) holds a refused sidecar against its sender for the rest of that one by-root lookup, so the lookup stops asking that peer. It does not score the peer or carry over to later lookups.

Lingua principale
Rust
Stelle
86
Fork
34
Merge medio
9g 20h
PR unite (30g)
77

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di lambdaclass/ethlambda

Tutte le issue di lambdaclass/ethlambda

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.