Scan to download
BTC $79,069.42 -2.77%
ETH $2,223.80 -3.08%
BNB $671.87 -1.04%
XRP $1.43 -4.14%
SOL $89.24 -3.55%
TRX $0.3519 -0.43%
DOGE $0.1133 -2.11%
ADA $0.2612 -4.06%
BCH $426.25 -2.34%
LINK $10.07 -4.41%
HYPE $44.21 -0.49%
AAVE $92.80 -6.15%
SUI $1.09 -8.08%
XLM $0.1544 -5.14%
ZEC $517.22 -8.03%
BTC $79,069.42 -2.77%
ETH $2,223.80 -3.08%
BNB $671.87 -1.04%
XRP $1.43 -4.14%
SOL $89.24 -3.55%
TRX $0.3519 -0.43%
DOGE $0.1133 -2.11%
ADA $0.2612 -4.06%
BCH $426.25 -2.34%
LINK $10.07 -4.41%
HYPE $44.21 -0.49%
AAVE $92.80 -6.15%
SUI $1.09 -8.08%
XLM $0.1544 -5.14%
ZEC $517.22 -8.03%
first_img

LayerZero CEO counters KelpDAO: rsETH initially used the default configuration, then manually switched to the not recommended 1/1 configuration

2026-05-06 14:34:22
Collection

In response to KelpDAO's accusations against LayerZero regarding the rsETH security incident, LayerZero CEO Bryan Pellegrino tweeted a detailed response, stating that much of the content is completely false.

Bryan pointed out that KelpDAO initially used LayerZero's default MultiDVN or DeadDVN configuration and later manually migrated to the 1/1 configuration; under the 1/1 configuration, almost 100% of the transaction volume came from rsETH; LayerZero's documentation repeatedly states that the 1/1 configuration is not recommended for production environments and provides specific transaction records and document screenshots as evidence.

app_icon
ChainCatcher Building the Web3 world with innovations.