doing smart stuff @Token_Logic prev @summerfinance_ | @oasisdotapp | @aptiv
51st state.
Joined February 2018
- Tweets1.9K
- Following1K
- Followers3.6K
- Likes2.2K
halaprix retweeted
Aave Labs has acquired the team and technology behind @avon_xyz, one of the leading companies working on fixed-rate lending onchain.
The Avon team brings deep protocol engineering and market-structure expertise to Aave Labs as it expands onchain lending for a mainstream audience.
halaprix retweeted
hindsight is 20/20, and binance hires the best. but if their statement is right, no key leaked: a devops laptop got into a service container, and the signer signed.
so the question is not the key. it's why the signer said yes.
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
binance.com/en/support/annou…
halaprix retweeted
tomorrow
Supersmooth is coming super soon 👀
Be Super...
with the best protocols:
@sparkfinance @Morpho @Compound_xyz @aave @SkyEcosystem
and the best curators:
@kpk_io @SteakhouseFi @gauntlet_xyz @ClearstarLabs
data and self custody powered by @vaultsfyi and @SafeLabs_
halaprix retweeted
All @aave V3 and V4 markets are now unfrozen.
The freeze was a precaution after the Binance incident. Aave contracts were never affected and positions stayed fully collateralized.
Glad to have supported the war room alongside the other Aave service providers.
Update following the Binance incident:
All markets are now unfrozen across Aave V3 and V4.
They were frozen as a precaution after initial reports, which paused new deposits and borrows while withdrawals and repayments continued as normal.
Aave contracts were unaffected by the incident and positions remained fully collateralized.
halaprix retweeted
Aave markets are now re-enabled for new positions.
Withdrawals and repayments remained available throughout the incident.
Aave was unaffected, and all positions remain overcollateralized with no bad debt.
Update following the Binance incident:
All markets are now unfrozen across Aave V3 and V4.
They were frozen as a precaution after initial reports, which paused new deposits and borrows while withdrawals and repayments continued as normal.
Aave contracts were unaffected by the incident and positions remained fully collateralized.
halaprix retweeted
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
binance.com/en/support/annou…
halaprix retweeted
LokalBot 0.10.1 is out. Most of the speedup since 0.9.2 came from removing Astra/Sol induced code complexity with Opus 5.5
ALT LokalBot 0.10.1: what got faster since 0.9.2. A table of six measurements, before and now. Autocomplete at the end of a long draft: 257 ms before, 60 ms now (model time per suggestion, M4 Max). Idle main thread: about 5% busy before, 99.5% idle now (30 s sample at 10 ms). Notes for a 20-minute meeting: 4 model requests before, 1 or 2 now (hosted models such as Qwen 3.8 27B). Overnight review: 80 to 480 s before, 26 s now (one review of a day, measured live). Launch cleanup: 566 ms before, 196 ms now (180-day library pruned to 14 days). Transcription with Qwen3-ASR 0.6B: 27 times real time before, 116 times now (benchmark harness, M4 Max). lokalbot.com, free and open source, private work memory for your Mac. Sources: merged pull requests 129, 141, 152, 163 and 200 on github.com/stevyhacker/lokalbot.
I gave my agents a memory of all my meetings and work.
Five open-weight AI models, 6.8 GB total, all running locally on my MacBook. They transcribe my meetings, read my screen, and find anything I said or saw on it.
LokalBot 0.9.2 is out today. I've been quietly iterating on this for a while, rebuilding it for my needs, and it looks much better now thanks to Claude Opus 5.5's excellent design skills.
Meet my all-star AI team:
Nemotron 3 → who's talking
Qwen3-ASR 1.7B → transcribes
LFM2.5 1.2B → finishes my sentences
Harrier 0.6B → search by meaning
Qwen3.5 4B → writes the recap
Claude Code and Codex can pull context from my meetings over LokalBot MCP or CLI.
Free and open source. No subscriptions necessary.
Huge thanks to @NVIDIAAIDev , @Alibaba_Qwen and @liquidai for the open weights and @huggingface for hosting them!
Links below:
ALT Infographic: "The little AI team inside your Mac." A robot next to a MacBook running LokalBot app using LLMs, with six AI model cards: Nemotron 3 (Core ML, 0.2 GB), Qwen3-ASR 1.7B (MLX 8-bit, 2.47 GB), LFM2.5 1.2B (GGUF Q4_K_M, 0.73 GB), Harrier 0.6B (GGUF Q8_0, 0.64 GB), Qwen3.5 4B (GGUF Q4_K_M, 2.74 GB) and Apple Vision (built into macOS). 6.8 GB, all local.
halaprix retweeted
60+ teams built at Orbio Build Week
Roberto took 2nd
We didn't build a demo. We built an agent people actually use, running on Orbio
Thank you @orbiodotso. .
GG @errandboard @foundryxyz @LudiArena
Orbio Build Week.
Over 60 builders, >$5000 in credit stipends, and ten winners.
Meet the top four:
1) @errandboard
2) @RobertoAgentApp
3) @foundryxyz
4) @LudiArena
More results, honorable mentions, and what comes next:
halaprix retweeted
I gave my agents a memory of all my meetings and work.
Five open-weight AI models, 6.8 GB total, all running locally on my MacBook. They transcribe my meetings, read my screen, and find anything I said or saw on it.
LokalBot 0.9.2 is out today. I've been quietly iterating on this for a while, rebuilding it for my needs, and it looks much better now thanks to Claude Opus 5.5's excellent design skills.
Meet my all-star AI team:
Nemotron 3 → who's talking
Qwen3-ASR 1.7B → transcribes
LFM2.5 1.2B → finishes my sentences
Harrier 0.6B → search by meaning
Qwen3.5 4B → writes the recap
Claude Code and Codex can pull context from my meetings over LokalBot MCP or CLI.
Free and open source. No subscriptions necessary.
Huge thanks to @NVIDIAAIDev , @Alibaba_Qwen and @liquidai for the open weights and @huggingface for hosting them!
Links below:
ALT Infographic: "The little AI team inside your Mac." A robot next to a MacBook running LokalBot app using LLMs, with six AI model cards: Nemotron 3 (Core ML, 0.2 GB), Qwen3-ASR 1.7B (MLX 8-bit, 2.47 GB), LFM2.5 1.2B (GGUF Q4_K_M, 0.73 GB), Harrier 0.6B (GGUF Q8_0, 0.64 GB), Qwen3.5 4B (GGUF Q4_K_M, 2.74 GB) and Apple Vision (built into macOS). 6.8 GB, all local.
halaprix retweeted
Aave V4 crossed $1B in user deposits.
That's more than double where it was a month ago.
halaprix retweeted
TokenLogic is aggressively working to increase Aave DAO's revenue and I love to see it.
Another Aave governance proposal by @Token_Logic is raising the GHO Borrow Rate and Aave Savings Rate.
Many of these proposals build on each other and most people don't realize it.
This will:
> Generate more revenue for GHO and @Aave DAO
> Make GHO more attractive to hold
This will be especially true once GHO becomes a spend currency on @ether_fi, and I believe TokenLogic is aligning everything for it.
Another very interesting thing is that ~69% of circulating GHO currently comes from debt, while ~31% comes from GSMs. So:
> Higher rates therefore increase revenue from the dominant issuance channel
> If the GSM share grows, Aave will hold more stablecoin backing earning supply yield on Aave (which TokenLogic is also proposing to increase)
Regardless of how GHO issuance evolves between debt and GSMs, Aave is increasing its revenue while making GHO more attractive to hold.
halaprix retweeted
Pour one out for these guys.
Originally spun out of the Maker Foundation back when the effort was to create a permissionless currency (DAI) rather than an underperforming multi-strategy credit fund (USDS).
Summer changed its name from Oasis after UK courts in 2023 forced them to exploit a previously unknown vulnerability in their own smart contracts in order to recover $140m in funds stolen from the Wormhole Bridge. The funds had been used as collateral in a Maker/Sky vault. Summer immediately patched the vulnerability, restoring their contracts to their intended permissionless nature.
Interestingly, that collateral could have been seized without an exploit by the courts going to Maker/Sky, although the Summer team was likely more reachable by the UK enforcement apparatus, given their domicile.
Summer is one of the original vault automation and aggregation services that long pre-date curators, when the emphasis of DeFi was on self-custody and trusting no one.
DeFi Saver and Oasis/Summer are always the two I think of for self management in that era, with Yearn being slightly adjacent.
So this is an old project, spun out of an even older project (MakerDAO) back when it had to build the full stack because nothing existed yet.
This quoted post is unavailable.
halaprix retweeted
💬 Onchain Message:
Information related to the exploit of the USDC Vault on the Lazy Summer Protocol Jul-6-2026 05:17 UTC.
This is the Summer deployer address. Can we discuss over Blockscan Chat.
etherscan.io/tx/0x25fa0e9b30…
halaprix retweeted
ICYMI, $SUMR is coming soon.
Full disclosure report ahead of launch👇
halaprix retweeted
Introducing: Autark 🔏
Hacked together at @ETHRome with @magentoooo ❤️🔥
🥇 1st Place in Privacy Track
🏆 2nd Place for Best Use of @ensdomains
Check out our repo 👇
github.com/jen-sei/autark-ET…
halaprix retweeted
Today’s my last working day at as an active contributor to the Lido DAO, as I head towards a (imo well deserved) break. I intend it to be at least 3 months long but colleagues are already betting against me sitting still and doing nothing. So, what did I learn working for Lido?
1. Lido secops and due diligence is second to none. These guys are very very careful about security, and are very very involved folks when it comes to Ethereum protocol level discussions. This sets them apart from any other liquid staking middleware or a service provider; sure you’ll do your opaque deals with some random centralised entity, but then these entities have no idea how to run a node, or how Ethereum works, or even share the values Lido has on topics like decentralisation.
2. Culture. The technical heart of Lido is borne out of a lived experience under an autocracy and ideals like decentralisation are woven into every conversation, every discussion, and are a common underlying theme. This is something absolutely nobody else can boast, save maybe rocketpool.
3. Lido’s going to be growing up, maturing beyond just staking. My job at Lido, I felt, was to show them possibilities. Over many months I bombarded them with ideas, some good some bad, and some may even become big beautiful protocols… and may our paths one day cross yet again.
4. I learnt a lot at Lido. I think as a technically savvy person with a deeply technical background, it was a great opportunity to hone my skills of topics _around_ technology. These are life lessons I’ll carry with me proudly.
Now, my decision to take a break comes from the fact that I do actually need a break. I moved countries, finished a very technical masters, an emotionally challenging phd, worked a regular job in a totally different field, went into crypto, built protocols, survived hacks, covid, new defi base layer lego protocol, etc.
Man. I need a break to catch my breath. I’ll be spending the time studying wtf Strategy means, working on my own product, and finally getting back to the growing backlog of books that have been staring at me for years.
Secondly, I felt that at my current capacity, I gave it my all. It is now up to other contributors to take carry my torch and instil fresher ideas.
Now with all that said, I’m incredibly proud to have had the opportunity to see, what I consider to be “the most important defi protocol in existence”, how it works internally. From my vantage point, i learnt an immense amount of details and that’s a gift that keeps on giving.