
Layer is making @WAVS_WAVS_WAVS the event-driven framework for distributed architectures. Ship fast with verifiable offchain compute.
Joined December 2023
- Tweets778
- Following261
- Followers3.3K
- Likes1.7K
LAYER retweeted
Replying to @WAVS_WAVS_WAVS
@WAVS_WAVS_WAVS is unique.
ZK, TEE, FHE, MPC... none of the hot buzzwords let you build something as basic as a decentralized event listener.
LAYER retweeted
Digital human rights in a massive industry.
This can be extremely overwhelming, because you need to keep up with so many topics, people, and initiatives.
But also, it's an invitation, my gosh, to entanglement (trendy word), or just connection between so many different organisms. In @web3privacy, we expand our spores covering areas of
- investigative journalism as in @FreedomofPress
- data workers as in @timnitGebru
- politics of gen AI as in @Info_Activism
- mesh networks like BitChat
- localism
- internet censorship mapping @OpenObservatory
- resistance AI
- feminist orgs protecting marginalised groups
- open knowledge foundations from @internetarchive to @Wikimedia
- flagship rights orgs like @accessnow
- artists working on surveillance tech mapping
- anti-authoritarian practical stack like @TutaPrivacy
- new encrypted messengers air.ms/install
- activists for various global causes x war conflicts, non-democratic regimes from Iran to Ukraine
- mercenary software mapping, advocacy like sentinelalliance.org
- whistleblower tech like @SecureDrop
- tech workers unionising against Big Tech
- free software for young adults
- multi-generational hacktivism @DyneOrg
Donna Haraway & Anna Tsing would be proud!
LAYER retweeted
keep3r network, gelato, and chainlink automation all share the same architectural weakness.
an external bot must be online, funded, and responsive at the exact moment your protocol needs execution
WAVS internal events are native, not another third party point of failure
verifiable doesn't mean slow.
decentralized doesn't mean complex.
trustless doesn't mean untrustworthy.
that's what we're proving 🌊
LAYER retweeted
Just automate it using @WAVS_WAVS_WAVS
I thought I had everything under control in the Resolv USR exploit, but the damage still exceeded my expectations.
Decided to share lessons that almost ruined my DeFi farming portfolio:
— 1. Big-name curators won't save you
Putting a larger allocation into a vault just because Gauntlet is the curator is a fatal mistake.
What happened to Gauntlet's Morpho vaults disappointed me. Their automated rebalancing bots kept supplying USDC into a broken market after the exploit was already known.
The systems designed to manage risk were actively making losses worse.
Don't trust what they project on their profiles. Verify how they actually manage capital.
— 2. Diversifying across black-box vaults is a mistake
If the vault you deposit into claims to diversify across yield strategies, depositing into another vault with a similar approach doesn't reduce risk.
It concentrates it.
wstUSR and RLP were embedded across Morpho vaults, Fluid, Venus Flux, and Euler. When the domino fell, contagion hit 15+ vaults and multiple lending markets because they were all feeding from the same well.
In this bear market, there aren't that many opportunities. The underlying positions likely overlap.
— 3. When something breaks, check everything immediately
I was one of the first to see this exploit unfold. And I just left for the gym, thinking the damage was already done.
That was wrong. There was a window where USR was trading at $0.15-$0.40 on DEXs but hadn't been paused on some platforms yet. Opportunistic borrowers exploited that gap to post depegged collateral and drain stablecoins.
Had I mapped my full exposure immediately, I could have withdrawn from Venus Flux before they paused withdrawals instead of spending the rest of the day worrying about how operators would fill the hole.
When a stablecoin depegs, don't assume the blast radius is contained. Track every integration point.
— 4. Crisis response reveals who deserves your trust
This incident exposed flaws in protocols I assumed were safe. Venus Flux, for example. I deposited three weeks ago and hadn't tracked what collateral they whitelisted since.
But Fluid's team stood out. Facing $15M+ in bad debt and $300M+ in outflows (their worst single day ever), they moved really fast by:
> Secured short-term loans to cover 100% of the bad debt
> Announced it publicly
> Committed to making every user whole
All within 24 hours.
Can't ask for much more from a team in crisis. However, whitelisting criteria for new collateral assets needs to be much tighter.
I got lucky and dodged the worst this time. But the next exploit won't send a warning. Still much more to learn to survive consistently in this market.
Banks are saying it plainly: adapt, or be replaced as "lower-value human capital."
This is what it looks like when the social contract dissolves.
The response has to be bigger than policy. Regulation alone can’t fix a logic that sees people as diminishing returns.
We need to rebuild the system – so technology serves the public, and people remain the point.
💚
crypto is still stuck in 2013 paying oracle providers.
enterprise systems figured out years ago that connecting directly to data sources beats the middleman. that why 85% of enterprise systems run on event-driven architectures
WAVS is the event-driven framework for crypto🌊
WAVS turns three vendor categories: oracles, bridges, cron jobs into three event types in one framework.
that's not a feature slapped onto a blockchain. WAVS is a completely reimagined event-driven architecture for distributed applications
chainlink only supports ~600 data feeds but the internet has over 200 million active APIs.
this isn't a data problem, it's an integration problem.
WAVS offchain events connect to any of them. no coverage list. no middleman. no permission needed 🌊
one event-driven framework for:
any data source ⚡️
any language ⚙️
any chain ✅
thats @WAVS_WAVS_WAVS 🌊













