Evercrest Technologies, described in the initial report as associated with KelpDAO, is said to have filed a civil claim in the Supreme Court of British Columbia over the April rsETH bridge exploit that involved 116,500 rsETH. The reported defendants are LayerZero entities and co-founder Bryan Pellegrino. What is clear is the scale of the underlying incident and the security-design dispute around a reported single-DVN bridge setup. What remains unclear is the formal status of the case, because no court file number, pleading, or official party statement was retrieved.

Reported BC claim lacks a public court record

The reported British Columbia claim is notable, but its procedural details are still missing from view. The initial account says Evercrest Technologies filed against LayerZero entities and Bryan Pellegrino, alleging negligence, negligent misrepresentation, and defamation over the rsETH exploit. Those are specific claims, and they would matter materially if confirmed in a filed pleading.

For now, the gap is basic but important: no Supreme Court of British Columbia filing, case number, docket entry, or party-issued statement was retrieved to confirm the exact style of cause, filing date, or present status. That does not disprove the existence of a lawsuit. It means readers looking for firm answers on the legal process should treat the case as a reported filing rather than a documented court proceeding with published details.

Field	Current reading
Reported claimant and defendants	Evercrest Technologies versus unnamed LayerZero entities and Bryan Pellegrino
Reported forum	Supreme Court of British Columbia
Underlying exploit scope	116,500 rsETH transferred; dollar value widely cited around $292 million
Current status	Filing reported, but no court document or official party statement was retrieved

That distinction matters because the next question is not only whether a case exists, but whether the technical allegations behind it are supported by documentary evidence.

Single-DVN allegations remain a proof problem

The core dispute is whether a reported single-DVN bridge configuration created a single point of failure, and whether LayerZero had enough involvement in that setup to face responsibility claims. In plain terms, a Decentralized Verifier Network is part of the message-verification structure used in some cross-chain transfers. The initial account says LayerZero reviewed or endorsed a single-DVN design connecting KelpDAO infrastructure with Unichain, and that KelpDAO later argued this made the bridge dangerously dependent on one verification path.

That is the central accusation, but it is still only an accusation on the current record. No retrieved postmortem, bridge-configuration record, verifier-threshold document, or official LayerZero statement confirms that review, approval, or direct causal chain. A separate media summary adds another layer of uncertainty by saying LayerZero first described the event as a developer configuration error and later said it “owns” a verifier-related decision tied to a vulnerable setup. Without the underlying statement, those positions cannot be cleanly reconciled.

That is why the most important unanswered question is not simply who was blamed in public. It is who controlled the configuration, what was reviewed in writing, and whether any explicit warning about concentration or failure risk existed before the exploit.

rsETH fallout reached DeFi before legal clarity

The broader importance of the dispute comes from ecosystem spillover, not from any proven legal precedent at this stage. The same incident that produced the reported claim also appears to have triggered reactions across other protocols. Internal media records tied to the event say Curve suspended certain LayerZero infrastructure functions while assessing root cause, and Aave later liquidated the attacker’s rsETH positions as part of recovery efforts.

Those responses suggest the rsETH exploit was not an isolated bridge error with contained consequences. It touched lending markets, collateral management, and risk controls elsewhere in DeFi. That is also why the often-cited roughly $292 million figure should be handled carefully: the token amount is consistent across reports, but the timing basis for the dollar valuation is not yet resolved between “at the time” and “at current prices.”

The real turning point will come when either a court filing or a technical incident record appears with enough detail to show who configured the bridge, what security assumptions were accepted, and how much loss remains after recovery actions. Until then, the case is best understood as a high-stakes responsibility dispute built on a major exploit, with the decisive documents still missing.