And now the world has Powfi 💥 powfi.alephium.org 👈

GM to the weekenders! Interesting project launched (beta) by an OG Alephium community member! ⛏️ Check out: karmalph.com

Powfi is now LIVE! 💥 The first two foundational layers of $ALPH DeFi are now available: ▪️ Concentrated liquidity ▪️ ALPH liquid staking That also means: ▪️ ALPH x USDT liquidity can now be provided through the CLMM. ▪️ ALPH can now be staked for xALPH. ▪️ Other markets can also be added to the CLMM. More details below 🧵

Alph Scoundrel has proven to be one of the most popular games on Alephium in recent times. What's your high score? Trust the 🐸👇

New Article 📰 @BigPepGhost explores what PoS staking participation rates suggest about community conviction. He explains why he believes the upcoming launch of Powfi positions Alephium to close a long-standing gap for PoW. Read it here: 🔗 alephium.org/news/post/why-t…

Bitcoin proved that PoW is the most trusted consensus mechanism ever built. Alephium then showed that you can build programmable DeFi right on top of it. The two ideas have always been compatible 🤝 it just took the right architecture to do it.

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.

Alephium has secured a path to provide the assets required to cover the USDT, USDC, wBTC, wETH and wBNB drained during the bridge exploit. As previously announced, the ALPH needed to back the approximately 500,000 unbacked wrapped ALPH acquired by users in the aftermath of the exploit will also be covered. The internal review of the updated bridge codebase has been completed, and the codebase has been handed over for independent third-party review. On this basis, relaunching the bridge remains the preferred path forward, subject to successful completion of the external review and resolution of any findings it raises. Given that all users affected assets (both drained and unbacked) will be covered, bridge operations would be able to resume under normal conditions. Legal and criminal proceedings related to the incident continue in parallel. Further updates will be shared as work progresses. We would like to thank our community and all affected users for their patience, understanding, and continued support as we work towards restoring normal bridge operations and resolving the impact of this incident.

Bridge Update Over the past 48 hours, the team has been working around the clock on recovery, remediation, investigation, and the future of the bridge. With regards to legitimate wALPH and corresponding native ALPH: the exact technical implementation for recovery of funds is still being evaluated and depends on several factors. Regardless of the implementation chosen, the objective remains the same: legitimate holders will be able to recover their ALPH, while assets illegitimately created through the exploit will not benefit from the recovery process. We continue to work with security and investigation partners to trace the drained assets and assess possible recovery opportunities and we are grateful for their ongoing support. At the same time, we are initiating coordination with legal counsel, relevant authorities, and law enforcement regarding the incident. Further updates will be shared throughout the week as work progresses.

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

March to Mainnet 15/05 🏃 As you may remember from last week’s report, Powfi’s frontend is now considered "feature complete" and thus the frontend devs are taking some well-earned rest after months of serious building. This week, it is Alphland that has made the most notable progress. Here is your weekly dev report: 🔍 Powfi’s smart contracts continue to undergo a thorough internal review process. 🔍 The first of three internal auditors has completed and approved the contracts. 🔍 The second stage of smart contract review is already underway and progressing positively. 🌐 Added a verification reminder banner on the Sponsor Dashboard for new sponsors pending admin approval. 🌐 Added a red warning banner for banned sponsors and disabled the “New Listing” button for both banned and unverified sponsors. 🌐 Refactored sponsor terminology from “company” to “organization” across the UI (CreateSponsor / EditSponsor). 🌐 Fixed a bug where Create Bounty was returning a 500 error. 🌐 Fixed issues related to Submission Notes. 🌐 Improved transaction hash error handling by adding a dedicated txError state for on-chain verification failures. 🌐 Fixed a bounty status bug where a bounty still showed as “Open” after a sponsor approved a submission and closed it. 🌐 Improved the Republish Bounty flow by replacing a simple date pop-up with a full, pre-filled bounty creation form. 🌐 Added a 404 page with “Go Home” and “Explore” buttons. 🌐 Removed the forced validation requiring users to change system-generated usernames. 🌐 Changed onboarding step one from “Complete username” to “Connect wallet address”. 🌐 Implemented the full Sponsor revision request flow, including revision_requested status and inline editing on the user side. 🌐 Improved UI by replacing browser alert pop-ups with toast notifications. That’s all for this week! It goes without saying, but your patience means everything to us as we build the FUTURE of SECURE DEFI ON PoW. The finish line is in sight 🏁

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…