Bridge Exploit Update Work on bridge remediation progresses. Over the past few days, the team has been focused on reviewing, testing, and hardening the updated bridge infrastructure. We are currently finalizing our internal review and preparing for an additional external security review before relaunching the bridge. In parallel, we are reviewing the broader bridge architecture and identifying additional improvements. Our intention is to further strengthen the system beyond the specific vulnerability involved in this incident. As of today, relaunching the bridge remains our preferred recovery path for affected users. We currently believe this is the fastest and most straightforward way to allow legitimate wrapped ALPH (wALPH) holders to redeem their assets, while also supporting the broader recovery process. This approach remains subject to the outcome of the ongoing reviews. On the investigation side, following coordination with legal counsel, a criminal complaint has now been formally filed with the competent prosecutor's office in Switzerland. We also continue to cooperate with security and investigation partners regarding asset tracing and recovery efforts. We will continue sharing updates during this process.

March to Mainnet 12/06 🏃 This week, our Core Contributors have been pushing Powfi closer toward mainnet, maintaining key Alephium infrastructure, and continuing Bridge audit and remediation work in parallel. We are working to relaunch an improved Bridge as soon as possible, once all relevant measures are complete. Here’s your weekly dev update: <Powfi> 💥 Continuing internal smart contract audit work 💥 Finalising the referral system design proposal 💥 Completed Powfi and Crowdin integration 💥 Fixed Powfi SDK npm homepage GitHub URLs <Backend> ⚙️ Upgrading all Alephium dependencies ⚙️ Running a full audit of the entire codebase ⚙️ Reducing Explorer Backend database size ⚙️ Improving node WebSocket support <Wallets> ✅ Hardened in-app browser security ✅ Team sync on Explorer Backend data validity ✅ Improved transaction sending speed across both wallets ✅ Submitted mobile wallet v2.5.1 to both app stores, including: 1️⃣ Improved cold start performance 2️⃣ Improved perceived transaction confirmation speed 3️⃣ Fixed spinner animation position on data refresh <Misc> 📸 Took snapshots of all wALPH holder addresses and LP providers on Uniswap and PancakeSwap 📚 Researched referral program designs, contract requirements, key considerations, and integration needs for channel partners (see the Powfi update from earlier this week) 🔎 Reviewed current grant applications ⬆️ Upgraded Alphland nodes 🔒 Researched improvements to security monitoring for the Alphland Alert System 🙅 Removed /admin path from production website Our conviction and resilience are rock solid. Alephium’s core contributors have continued to deliver through all of it, and that has not gone unnoticed by the community. Your continued support is priceless 👏 Keep an eye out for upcoming Bridge and Powfi updates. More to come.

🏆⚽️ World Cup 2026 is here and we're celebrating with @Tangem! Up for grabs: - 3x Limited Tangem "Soccer Edition" hardware wallets - A share of $200 in USDT rewards To enter: → Follow @Alephium & @Tangem here on X → Describe the team you're rooting for at the WC26 - no country names, just vibes (e.g. 🇨🇭🧀🏔️) → Tag @Alephium & @Tangem 2 friends → Fill out the form at forms.gle/37SaGHifZnaebuS88 Final whistle: June 20th. Good luck!

Bridge Update Today, we continued work across multiple recovery and investigation tracks. ▪️As part of the bridge incident remediation, the bridge guardians, with support from our security partners, executed an authorized recovery procedure to invalidate the unbacked wrapped ALPH held in the attacker's wallet. This action applied exclusively to unauthorized wrapped ALPH created through the exploit and held by the attacker. It did not affect native ALPH, legitimately backed wrapped ALPH held by users, or addresses that unknowingly acquired unbacked wrapped ALPH through trading activity following the exploit. It also did not affect the Alephium L1 consensus rules. Removing these exploit-created assets from the attacker's control is an important step in the ongoing recovery and remediation process. ▪️ We are advancing the recovery path for legitimate wrapped ALPH holders and have identified all eligible holders via snapshot. ▪️We are confirming the addresses of liquidity providers affected by the exploit, including LPs currently providing liquidity on Uniswap and PancakeSwap, as well as addresses that unknowingly traded against the attacker's transactions. ▪️We have submitted an incident report to Switzerland's National Cyber Security Centre (NCSC) and are coordinating with the relevant law enforcement authorities. ▪️We continue to work closely with @Blockaid_, @SEAL_911, and other investigation partners to trace assets and assess possible recovery opportunities. ▪️In parallel, work continues on the bridge recovery plan, technical remediation, legal and criminal investigation efforts, and the preparation of the full postmortem. ▪️Below, we have published a comprehensive on-chain analysis covering the exploit timeline, affected transactions, fund movements, and the current location of the drained assets. Read the on-chain report here: alephium.org/news/post/the-a… We will share further updates as the situation develops.

Powfi Update 💥 Following very positive discussions with several partners, the Powfi codebase has been upgraded to support direct integrations with our $ALPH Staking Layer through a referral-based framework. How it works: Traditional B2C Workflow ▪️ A user holds ALPH ▪️ Connects their wallet to Powfi ▪️ Stakes their ALPH ▪️ User starts earning rewards New B2B2C Partner Workflow ▪️ An integration partner offers ALPH staking to its users ▪️ The yield offered is the same as staking natively on Powfi ▪️ Staking is attributed to the partner via an on-chain referral tag ▪️ ALPH is staked via the Powfi Staking Layer ▪️ The partner earns a commission One example from our recent discussions is a mining pool offering ALPH Staking to its users. Other potential integration partners include: wallets, centralized exchanges, and of course dApps. This is how the Powfi staking layer scales and maximizes locked circulating supply, strengthening $ALPH and the broader ecosystem. We'll share more updates as these conversations progress and integrations begin to materialize.

A full technical breakdown of how the burn was executed was published walking through the technical process behind how the attacker's wALPH was burned, including the guardian coordination process. x.com/alephium/status/206253…

Powfi is getting a codebase upgrade introducing the B2B2C partner integration framework built on the ALPH Staking Layer, enabling integration partners to offer ALPH staking to their users and earn a commission through an on-chain referral system. x.com/alephium/status/206217…

Weekly Summary 🗓️ A lot happened this week. Here is a recap. 🧵

On Decentralization and immutability Governance actions and decentralization are often discussed as though they are incompatible concepts, when in reality, decentralization and immutability are distinct properties. A decentralized system can still change state when the relevant participants reach the required level of consensus. The defining question is not whether a change is possible, but who is authorized to approve that change and what consensus threshold must be met. Bitcoin, Ethereum, Alephium, and other decentralized networks have all coordinated protocol changes throughout their histories. Network upgrades, hard forks, and governance actions are all examples of decentralized participants collectively agreeing to modify a system’s state or rules. The Ethereum DAO fork is perhaps the most widely known example of a highly decentralized network coordinating a state change in response to an exploit. The Ethereum community reached consensus around a protocol change that effectively invalidated the outcome of the attack and restored the affected funds. The same principle applies here. The action was not the result of a unilateral administrative decision. The Bridge Guardians collectively approved a temporary upgrade that enabled the unbacked wALPH remaining in the attacker’s wallet to be burned. Approval from the full Guardian set was required. The bridge governance model differs from that of a Layer 1 blockchain and relies on a substantially smaller guardian set. This governance structure is similar to that used by many cross-chain bridge systems, where upgrades require approval from the designated guardians or validators responsible for securing the bridge.

🧵How the Attacker's wALPH Was Burned “As part of the bridge incident remediation, the bridge guardians, with support from our security partners, executed an authorized recovery procedure to invalidate the unbacked wrapped ALPH held in the attacker's wallet.” The Bridge Guardians coordinated through the bridge’s multi-signature governance mechanism to temporarily upgrade the bridge’s wrapped asset contract implementation. This temporary implementation introduced functionality that allowed the attacker-controlled unbacked wALPH to be permanently burned. Immediately after execution of the burn, the contract was reverted to its original implementation. This action required approval from the full Guardian set, which is why the process took several days to organize and execute. Note that the guardians are separate and independent from each other. Alephium’s bridge wrapped asset contracts, like those used by many cross-chain bridge systems, are deployed behind upgradeable proxy contracts. This architecture allows contract implementations to be modified through Guardian-approved governance actions when required. It is important to note that the burn capability used in this remediation did not exist in the bridge’s normal operating implementation. It was introduced through a temporary governance-approved upgrade specifically to remediate the unbacked supply created by the exploit and was rolled back once the action was completed. This approach has precedent in previous DeFi security incidents. Following the pxETH exploit involving Yearn Finance, unbacked tokens were invalidated by the token issuer directly from the attacker's wallet. After the Echo Protocol incident, attacker-controlled eBTC was burned once administrative control had been recovered. The tokens burned in our case were exclusively the unbacked wALPH that remained in the attacker’s wallet at the time of the action. Any wALPH that had already left the attacker’s wallet prior to the burn was not affected. The recovery action was intentionally limited to assets that remained under the attacker’s direct control and did not affect third-party holders who acquired wALPH through ordinary market activity without involvement in the exploit. The action had no effect on assets held by legitimate users and did not affect any assets on the Alephium Layer 1 blockchain. The bridge itself remains disabled while remediation, review, and security assessment work continue.

Teams that innovate, deliver, push boundaries -- in the long run, they are the ones worth paying attention to.

Alephium. Soon. All thanks to @Factorcx.

RWAs on _________?

The community's already here. Come find them: alephium.org/discord/

Want to stay closer to everything happening across the @alephium ecosystem? There's a new opt-in role on Discord: >> Marketing/Ecosystem Ping Spaces, ecosystem launches, community updates, and more... basically, all the things we can't justify hitting @-everyone for. Discord fam >> subscribe in #role-assignment if you want in 🔔

What if there were a better way? Hmmmm...

there's no reason to still have infinite approvals for ERC20 tokens

Some of 2026's nastiest exploits had nothing to do with smart contracts. The contracts were absolutely fine. Several attacks were traced back to the off-chain infrastructure that nobody thinks to audit, like: ▶️ RPC nodes ▶️ Relayers ▶️ Indexers These are all in scope for an attacker, but none of them are in scope for your audit firm. That's a problem. Fortunately, @RaduC22 built @linx_labs on @alephium specifically to reduce this surface. Now, he shares exactly why it matters. 🔗 alephium.org/news/post/the-w…

Stop scrolling, scrolling, scrolling... 🎶

While you're scrolling, your $USDT could be earning 8.73% APY on Linx. Don't let idle stables sit. Put them to work → app.linxlabs.org