Datachain - ELC for Bridge - Ethereum

QuantstampRepository at commit 7a40e6a

Quantstamp reviewed Datachain (Datachain - ELC for Bridge - Ethereum) on 8 Jan 2025: 2 findings, 0 critical; all marked fixed.

No open critical findings
Open the reportOpen Datachain’s security record

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings4

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low002

Marked Informational by the firm. Not counted as findings.

InformationalMissing Validation for Finalized Header in Light ClientAcknowledged

The function `is_valid_light_client_finalized_header()` is missing essential validation checks for finalized headers introduced in the Deneb (EIP-4844) and Capella upgrades. These checks ensure that: - For epochs earlier than `DENEB_FORK_EPOCH`, `execution.blob_gas_used` and `execution.excess_blob_gas` are both `0`. - For epochs earlier than `CAPELLA_FORK_EPOCH`, `execution` is an empty `ExecutionPayloadHeader`, and `execution_branch` is an empty `ExecutionBranch`. These validations are specified in the [Deneb upgrade to the Sync Protocol](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/light-client/sync-protocol.md#modified-is_valid_light_client_header). Without these validations, the function may incorrectly validate headers that are non-compliant with the protocol rules for these upgrades.

InformationalNot Taking Update's Next Sync CommitteeFixed

The function `apply_updates()` is designed to mirror the function of the spec named `apply_light_client_update()`. In the latter function, when the stored consensus state lacks a next sync committee, it is checked that the update's finalized header's sync committee period is equal to the stored consensus state's sync committee period, and the update's next sync committee is added to the stored consensus state. However, this assignment does not take place at any point in `apply_updates()`. However, this appears not to be a problematic issue as it appears that the stored consensus state will never be lacking a next sync committee. This is despite the fact that when the new consensus state is validated in `ConsensusState::validate()`, it is not checked whether there is a next sync committee.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Repository and files the report names (4)

  • https://github.com/datachainlab/ethereum-elc/src/errors.rs at commit 7a40e6a73b1fc08874aa33b7fa4c07daad9141af
  • https://github.com/datachainlab/ethereum-elc/src/lib.rs at commit 7a40e6a73b1fc08874aa33b7fa4c07daad9141af
  • https://github.com/datachainlab/ethereum-elc/src/client.rs at commit 7a40e6a73b1fc08874aa33b7fa4c07daad9141af
  • https://github.com/datachainlab/ethereum-elc/src/state.rs at commit 7a40e6a73b1fc08874aa33b7fa4c07daad9141af

Part of Datachain’s security record

Datachain
Audits7 audits by 1 firmLast audit Jul 2025, by Quantstamp.
Critical findingsNo open critical findingsAcross 7 reports.
Open Datachain’s security record

Security firm

Quantstamp

240 projects reviewed · 338 reports · latest Nov 2026

See Quantstamp’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us