π 5x Hackathon Winner π¨π¦πͺπΊπΉπ· Lead DevRel Engineer π»βοΈ @BeraChain β Prev @0xPolygonLabs + @ankr π₯ @developer_dao member since 09/21
Canada / Europe
Joined November 2018
- Tweets7K
- Following1.9K
- Followers13.8K
- Likes16.3K
Manny (π§±,π) retweeted
OpenAI employees making up new words to justify Astraβs unreadable code
Manny (π§±,π) retweeted
π¨ CRITICAL ETH SECURITY UPDATE
A critical vulnerability has been discovered in the Ethereum app on Ledger hardware wallets.
The flaw could allow a malicious application to alter ETH transaction details during signing without the change being visible on your Ledger device screen.
Fixed in Ethereum app v1.22.2
If you use Ledger for ETH or Ethereum assets:
β’ Update the Ethereum app to v1.22.2+
β’ Update Ledger Live
β’ Update your Ledger firmware
β’ Avoid signing transactions until everything is updated
If you hold ethereum:native on Ledger, update ASAP.
π¨Critical security update for LEDGER hardware wallets
A critical vulnerability has been identified in the Ethereum app on Ledger hardware wallets. It could allow a malicious application to alter the details of a transaction during signing, without this being visible on the device screen.
This has been fixed in Ethereum app version 1.22.2. If you use a Ledger device, please update ASAP
While you're in there, it's also good practice to make sure Ledger Live and your device firmware are fully up to date.
Manny (π§±,π) retweeted
Just FYI. If you are switching models in a session all the time - you are doing it wrong.
Every time you switch, your entire prompt cache is invalidated on the new model you switch to, and you have to repay the full input tokens price for all of it.
Stop doing this unless those models are free.
This is not a hermes thing - this is a fundamentals of inference thing.
Manny (π§±,π) retweeted
Despite the frenzy of activity in the stablecoin space, onchain yields are still cooked
To hit 15-20% yield you've gotta be somewhere from 3-7x levered on PT or Convex loops etc
Meanwhile Liquid Royalty's senior vault is paying 30%, with Bend at 16% with instant liquidity.
Manny (π§±,π) retweeted
We've been quiet as the first ERA pilot preps to go live this quarter.
Now they've got some capital deployed (stealth), solid PoC data, an 8 fig LP pipeline, and a 0 to 1 path towards yield generation on a massive non yield bearing asset.
Excited to share more soon.
Manny (π§±,π) retweeted
1/ PoL Next is coming to @berachain Mainnet on July 7th & 8th!
PoL Next is the most significant upgrade to Berachain since mainnet launch. It's not a soft patch, it's a hard fork that rewrites the core incentive layer of the chain.
Here's everything you need to know π
ALT Berachain PoL Next is coming to Mainnet on July 7 and 8
Manny (π§±,π) retweeted
BrownFi V3
ββββββββββ 90% Complete π
In traditional market making, bid-ask spread is the top 1 tool to protect LPs against informed traders (or adverse selection). But in most AMMs, Spread = zero, where Bid and ask collapse to the same point on the bonding curve. LPs are fully exposed.
BrownFi V3 changes this.
We built a dynamic spread system that responds to real market signals:
- Oracle price discrepancy
- Volume imbalance (VPIN)
- Markout & external price events
π‘ When market is stagnant (low volatility, balanced flow):
- VPIN is low β flow is mostly uninformed
- Narrow the spread
- Maximize trade volume β LPs earn more fee.
π΄ When market crashes (strong sell pressure):
- π Widen Bid side β Bid moves further down
- Limit LP losses from one-sided selling pressure of base token.
- π Narrow Ask side β attract buyers to get base token out, rebalance pool faster.
π’ When market is in a momentum run (FOMO / one-sided buying pressure):
- Pool drains of base token as buyers pile in
- π Widen Ask side β make buying base more expensive
- Slow down informed/momentum buyers extracting value
- π Narrow Bid side β incentivize sellers to bring base back
- Pool rebalances before LPs take asymmetric inventory loss
With this design, each market regime can get a tailored response, not a one-size-fits-all fee hike like other AMMs. And this dynamic spread system can serve as a real market making desk in Defi.
BrownFi V3
ββββββββββ 70% Complete
With V3, we aim to build the most efficient AMM on EVM, starting with asymmetric liquidity concentration.
In V2, a single liquidity concentration parameter, K (kappa), is applied symmetrically to both quote and base inventories:
β¬οΈ When K decreases, both quote and base inventories contract, reducing price impact.
β¬οΈ When K increases, both inventories expand, increasing price impact.
In V3, however, liquidity concentration between Base and Quote becomes asymmetric. This allows each side to be controlled independently, providing greater flexibility for our MM strategies.
E.g. For ETH/USDC pair during a bear market, we can widen the liquidity range of the USDC (Quote) side to capture a deeper decline in ETH price (from $2,000 down to $1,500). At the same time, we keep the ETH (Base) side more concentrated (from $2,000 to $2,200) to maximize fee capture from ETH buy orders.
More on V3 coming in the next few days. Stay tuned!
Manny (π§±,π) retweeted
wow, i want to re-iterate here, the @wasabi_protocol exploit isn't really a story about a stolen key. It's a story about what happens when one EOA controls a batch of upgradeable vaults with no multisig, no timelock, and no DAO governance as @evilcos and @zachxbt both pointed out within an hour of the drain (it should have never happen)
The mechanics: deployer EOA grants ADMIN_ROLE to an attacker contract β UUPS upgrade replaces the perp vaults & LongPool with malicious logic β strategyDeposit() called on 7 vaults β drain(). 3 minutes, $5M+ across Ethereum, Base, Berachain & Blast. Largest single hit: 840.9 WETH (~$1.9M) from wWETH.
Wasabi has acknowledged the issue and asked users not to interact with contracts. @blockaid_ flagged that all Wasabi/Spicy LP-share tokens minted by these vaults should be treated as compromised the underlying assets are gone.
If you have funds anywhere in the protocol: withdraw and revoke approvals via @RoscoKalis's @RevokeCash. Big shoutout to him, the tool everyone reaches for on days like this.
34th major incident this month. April 2026: 30+ exploits, ~$630M drained. The recurring pattern keeps writing itself: privileged EOAs over upgradeable contracts, no governance friction, one phished signature away from zero.
Manny (π§±,π) retweeted
Berachain is aware of the Wasabi Protocol admin key compromise affecting multiple chains.
We have paused and blacklisted the affected Wasabi reward vaults on Berachain. No further BGT emissions will flow to the compromised contracts.
If you interacted with Wasabi on Berachain, revoke your token approvals immediately:
β revoke.cash
Contracts to revoke:
- 0xc95ab9eff8fb48760703c74416764b8f898afa1b
- 0xd948212f077e552533158becbc1882c1b19c40fe
- 0x0da575D3edd4E3ee1D904936F94Ec043c06Bb12B
- 0x3EE6C6CdAa0073DE6Da00091329dE4390B0DF1EE
BGT rewards in Berachain's native RewardVaults are safe and can still be claimed.
We are working with Blockaid and ZeroShadow on the ongoing investigation.
Manny (π§±,π) retweeted
I'm looking for my next role. DevRel / DX engineer with 5+ years shipping across web3, ai and fintech on different stacks. I'm ready to dive in and solve problems from day 1! My DMs are open π€
Manny (π§±,π) retweeted
Introducing the DefiLlama SQL Studio.
Create custom CSV exports and charts that bring together multiple DefiLlama datasets. Run SQL directly in your browser to access every major slice of DeFi data.
Now available to API plan users in our Downloads portal.
Manny (π§±,π) retweeted
Look guys, it's actually really straightforward, a bunch of people staked their ETH on the Ethereum blockchain to earn yield, except they didn't want their capital to be locked up, so they actually staked with a liquid staking protocol called Lido who provided them a liquid staking receipt token called stETH, except they decided to juice their yield further by depositing their stETH receipt tokens into a restaking protocol called Eigenlayer, except they didn't want to lock up their capital, so they actually restaked with a liquid restaking protocol called KelpDAO who provided them with a liquid restaking receipt token called rsETH, except they decided to juice their yield further by depositing their rsETH tokens into a lending protocol called Aave so that they could open a leveraged looping position that borrows ETH against the rsETH collateral and restakes the ETH into rsETH which is then deposited as collateral, except it turns out rsETH used a cross-chain bridge called LayerZero that was hacked by north koreans causing rsETH to become undercollateralized and now these looping positions are stuck and unprofitable, and everyone is pointing fingers at each other, and also DeFi is a very serious industry
Manny (π§±,π) retweeted
We are hiring at @zeropsio!
We are expanding the DevRel team and hiring for two critical roles:
- Technical DevRel Engineer
- Developer Advocate (Community Builder)
100% remote.
Full descriptions are available at the link below.
I'll go live later to talk about this
Manny (π§±,π) retweeted
we've got a few projects lining up for launch that'll be offering very attractive yields on stables (10-20%+) and BTC (5%+)
they're hoping to primarily deal with a smaller set of concentrated LPs (HNWIs, funds etc), as opposed to retail.
DMs open for interested folks π«‘
Manny (π§±,π) retweeted
Early next week, we expect to launch a claims page, allowing anyone who lost funds in the Balancer v2 / BEX exploit to reclaim their deposits from the BEX.
For anyone who deposited through a vault contract (ie. Infrared), your original address used for the deposit (into Infrared etc) will be able to claim the funds directly.
In the meantime, a CSV will be published with all wallets and their expected claimable holdings. All recovered funds will be returned to users. We believe these to be equivalent to approximately 96% of the deposited value in most pools.
For funds which remain in the BEX, we expect to perform an additional hard fork later next week to unblock the BEX contracts at the VM level, then follow a similar process to Balancer's most recent communications in terms of enabling Recovery Mode on Composable Stable v6 pools, and re-enabling the use of non-Composable Stable Pools. More info to come on this in the near future.
Thanks in advance for your support and patience as we get funds back to users in the safest manner possible.
Berachain.
Manny (π§±,π) retweeted
The Berachain validators have coordinated to purposefully halt the Berachain network as the core team performs an emergency hard fork to address Balancer V2 related exploits on the BEX.
This halt has been executed purposefully, and the network will be operational shortly upon recovering all affected funds.
Thank you in advance for your understanding, and expect more updates and a full retro soon.