News

On December 14, according to the official announcement, Berachain's liquid staking protocol Infrared has announced details of the IR token airdrop. The airdrop targets early community members, Boyco pre-deposit event participants, and users who have participated in community activities. Users can claim the airdrop in advance through the centralized exchange pre-deposit process. The pre-deposit period is from December 13, 12:00 UTC to December 15, 17:00 UTC. Users need to start the process on the official Infrared website, select an exchange, and submit their user ID. The IR token has three main functions: staking to obtain sIR for governance voting rights; profit sharing through a buyback mechanism, with a portion of protocol fees flowing into the "Red Fund" for IR token buybacks; and token issuance to optimize protocol efficiency and revenue. Key milestones: IR token will be listed at 8:00 UTC on December 17, and all claims will be permanently closed at 00:00 UTC on January 12, 2026. Non-exchange claims will open on the day of the token generation event. Previously, it was reported that Infrared, the first liquid staking protocol in the Berachain ecosystem, completed a $14 million Series A funding round led by Framework Ventures.

ChainCatcher news, the Ethereum consensus layer client Prysm team has released a post-mortem analysis report on the Fusaka mainnet incident. During the event, almost all Prysm nodes experienced resource exhaustion when processing specific attestations, resulting in their inability to respond to validator requests in a timely manner. The impact range was from epoch 411439 to 411480, with 248 blocks lost over 42 epochs, a missing rate of 18.5%. The network participation rate dropped to a minimum of 75%, and validators lost approximately 382 ETH in attestation rewards. The root cause of the failure was that Prysm beacon nodes received attestations possibly sent by unsynchronized nodes, which referenced block roots from previous rounds. To verify these attestations, Prysm attempted to reconstruct compatible states, leading to repeated processing of past round blocks and costly round transition recalculations. The team temporarily resolved the issue by guiding users to use the --disable-last-epoch-target parameter, and subsequent versions v7.1 and v7.1.0 include long-term fixes.