Marcus_Balancer Profile Banner
Marcus | Balancer 🦇🔊 Profile
Marcus | Balancer 🦇🔊

@Marcus_Balancer

Followers
619
Following
13K
Media
45
Statuses
3K

@Balancer

Worldwide
Joined August 2018
Don't wanna be here? Send us removal request.
@Marcus_Balancer
Marcus | Balancer 🦇🔊
18 hours
Proud of the team for moving fast and doing things the right way. On-chain notice sent and recovery path open. Focus stays on users and restitution. Grateful for the teams supporting this effort.
@Balancer
Balancer
18 hours
On wednesday, we sent an on-chain message to all known addresses involved in Monday's exploit, following the best practices and offering a path for the hacker to contact us and return the funds. We understand that affected users are awaiting further updates. We will continue to
5
3
46
@therollupco
The Rollup
2 days
Cyfrin Audits Co-founder Patrick Collins talks about the recent Balancer exploit and cloud chasers posting fake hack analysis: "Be careful of KOLs who don't know what the f*ck they're talking about. Most of them don't."
3
2
10
@DefiIgnas
Ignas | DeFi
2 days
Vault products like disgraced Stream xUSD will continue to attract users. DeFi gets complicated and retail WANTS higher passive yield, so 'experts' fill that hole. Problem is opacity: You can't track where funds are in real time. DeFi already solved this issue last cycle:
@LidoFinance
Lido
2 days
Introducing stRATEGY Curated DeFi rewards centered around stETH Aave, Ethena, Uniswap & more ↓
68
18
276
@Marcus_Balancer
Marcus | Balancer 🦇🔊
24 hours
The Certora team has been a steadfast partner from the early days. As soon as the incident surfaced they spared no efforts, jumped in and worked side by side with us. Grateful to them and to everyone supporting Balancer.
@CertoraInc
Certora
2 days
Since Monday’s @Balancer v2 exploit, we’ve worked hand in hand with their team to develop the first root-cause analysis of the issue, identify all affected and potentially vulnerable pools, and determine whether v3 was susceptible to the same attack. Our analysis breaks down
0
2
42
@crypticdefense
CrypticDefense
2 days
Respect to the Balancer team for their speedy analysis and transparency. I can speak from first hand they take security very seriously. With such a fantastic developer team, the protocol will bounce back from this incident in no time. We SRs should be motivated to do our best.
1
1
10
@Marcus_Balancer
Marcus | Balancer 🦇🔊
2 days
DeFi will win!
@StaniKulechov
Stani.eth
2 days
DeFi will win.
3
2
22
@beets_fi
Beets
3 days
Balancer has published an incident update on the Balancer V2 Composable Stable exploit. As a Balancer fork, Beets’ V2 Composable Stable pools were also impacted. The issue affected only Balancer V2; V3 pools and stS remain fully functional and were not exploited. Please
8
10
75
@victorokpukpan_
𝗩𝗶𝗰𝘁𝗼𝗿_𝗧𝗵𝗲𝗢𝗿𝗮𝗰𝗹𝗲
3 days
Here’s what I have to say about the @Balancer hack. No matter how many audits a codebase passes, no code is ever 100% risk free. Balancer took security seriously, as seen in the image attached. But the blackhat was just better at seeing what the whitehats didn’t. Still,
7
9
85
@fabiomendesafc
Fábio Mendes
3 days
This post outlines some of the efforts we've been putting together with partners, security teams, and the broader community. Despite the challenges the entire ecosystem has faced recently, serious DeFi protocols will prevail.
2
5
37
@autopools
AUTOfinance (prev. Tokemak)
3 days
Update from Balancer below 👇 Reminder: only autoETH, balETH, and autoLRT had exposure to Bal v2 pools, totaling ~4% across their total TVL. Bal v2 destinations are removed. USD denominated Autopools were unaffected.
1
1
19
@monerium
Monerium
3 days
🚨 $EURe and the @Balancer V2 exploit: what you need to know A quick recap of what happened, the steps we took, and why EURe remains secure 🔐 🧵
1
2
17
@Marcus_Balancer
Marcus | Balancer 🦇🔊
3 days
"The exploit does not work on Balancer v3"
@trailofbits
Trail of Bits
3 days
Since the Balancer hack on Monday, we've been working around the clock to help the Balancer team understand the bug and its implications. We've verified the bug's cause and have independently verified that the exploit does not work on Balancer V3. Once the dust settles, we plan
4
5
61
@trailofbits
Trail of Bits
3 days
Since the Balancer hack on Monday, we've been working around the clock to help the Balancer team understand the bug and its implications. We've verified the bug's cause and have independently verified that the exploit does not work on Balancer V3. Once the dust settles, we plan
6
12
216
@Xeonusify
xeonus.eth
3 days
I was one of the first team members being made aware of the incident and initiated emergency procedures immediately with our security partners. Support from the community has been amazing. This first report shall bring some clarity. Much more work to be done!
1
1
7
@Marcus_Balancer
Marcus | Balancer 🦇🔊
3 days
This provides the first level of clarity. We continue working closely with security partners, whitehats and the ecosystem across networks. We’ll share more as soon as it’s appropriate to do so. Thank you to everyone who has been supporting the ongoing efforts.
7
11
104
@stakewise_io
StakeWise
4 days
The full account of how ~5,041 osETH and 13,495 osGNO were recovered from the Balancer V2 exploiter.
5
11
46
@QuantAMMDeFi
QuantAMM
4 days
Excited to be at smartcon in NYC, we will be announcing our CRE integrations on stage tomorrow.
@chainlink
Chainlink
4 days
A wide variety of use cases in onchain finance are being built and deployed on CRE today: • Cross-chain DvP transactions across public & private chains • Tokenized fund workflows using ISO 20022 messaging • Tokenized fund subscriptions and redemptions • Hybrid smart
2
7
109
@rezervemoney
Rezerve Money
4 days
We’ve worked closely with both @Balancer and @beets_fi What happened is devastating. But knowing these teams, they’ll fix, recover, and rebuild stronger. Exploits can hit code. They can’t kill conviction. We got you. DeFi will come back. It always does 💪
4
2
12
@TreehouseFi
Treehouse
4 days
An Update on the Balancer & Stream Incident TLDR: All tAssets (tETH & tAVAX) are unaffected and secured. All funds are SAFU. Following our earlier post on the Balancer security incident, Treehouse’s engineering and risk teams have completed a full assessment of all tAsset
@TreehouseFi
Treehouse
5 days
We are aware of the ongoing security incident affecting the Balancer protocol. All Treehouse products and vaults are unaffected and funds are SAFU. On 3 November 2025, 07:50 UTC, Treehouse’s on-chain monitoring systems detected irregular activity involving Balancer’s
38
121
173