banana
Joined November 2010
- Tweets6.3K
- Following569
- Followers3.1K
- Likes7.5K
Pinned Tweet
I'm turning 55 this year.
I spent my early years as a piece of shit human. Drinking, smoking, drugs, and wasting my life.
17 life lessons at 55 I wish I knew at 25: 🧵
Automating an inefficient process just scales the inefficiency.
AI made that mistake much easier to make.
And it shows.
will button retweeted
hey folks 👋 I’m open to new challenges - backend/protocol eng, tech lead or EM. into web3, AI, or web2, whatever’s genuinely interesting.
11 yrs building things, 6 deep in web3 - distributed systems, consensus, cross-chain infra, some open source, and lately exploring AI/agent infrastructure too.
go/rust/python person. DMs open 🙌
will button retweeted
Katana's stake page, redesigned.
Cleaner layout, clearer numbers, same productive KAT.
Don't let you $KAT sit idle.
app.katana.network/stake
I didn't think Jira could disappoint me any further, but they really went out of their way to prove me wrong with the Jira MCP server.
When I die, I want the Jira team to carry my casket so they can let me down one last time.
will button retweeted
Agglayer's pessimistic proof enforces security through one simple rule: a chain can only withdraw what's been deposited. Verified by onchain ZK proofs.
That's how the Open Money Stack's crosschain infra kept @Katana liquid during the rsETH exploit.
DeFi needs to recognize that Finance runs on trust, not software. Liquidity is a posture, not a number. Katana was among the most liquid venues during the crunch created from the rsETH exploit.
Wrote about this and more here: beincrypto.com/polygon-aggla…
will button retweeted
Katana Perps site will be offline: April 27 at 14:00 UTC, estimated ~1 hour downtime.
Open positions will auto-close at upgrade time if you don't close your position beforehand.
No need to withdraw, funds stay put.
Just reopen your positions once the site is back online.
Katana Perps will be offline for a scheduled upgrade
April 27 at 14:00 UTC ~1 hour downtime.
Users do not need to migrate funds. Any open positions will be auto-closed and need to be re-opened after the upgrade is complete.
Join Discord for updates: discord.gg/katananetwork
will button retweeted
Our team has been actively monitoring the rsETH exploit: Polygon Chain, Agglayer, and the broader ecosystem, including Katana & Vaultbridge, remain unaffected by the incident.
Polygon has safely moved over $2T to date and we will continue to stay vigilant as this event unfolds.
will button retweeted
Out of an abundance of caution, the OFT path on Vaultbridge (secured by a 2/3 DVN) has been temporarily paused.
Bridging vbAssets to and from Katana remains fully available via Agglayer.
Agglayer verifies with ZK proofs, not Proof of Authority. Math, not multisigs
will button retweeted
Fun fact. Before doing dev work, I ran an IT security business for years. While nothing is 100%, I found that human error was the number one cause of hacks.
Layers of security helps a lot.
Isolating critical items from day to day tasks.
Two computer gang 🤙
Running multiple agents in parallel isn't the hard problem.
Knowing how to break the work down so agents can execute it is.
This is a leadership problem.
Agents opening PRs to merge code isn't the hard problem.
Knowing the code they wrote is the right code for the problem is.
This is a technical problem.
Solve one without the other and you've got nothing.
Watching big companies blame AI for layoffs this year has been something.
I spend my days shipping with AI agents. Here's what I see: AI isn't replacing engineers. It's letting the engineers you already have finally tackle the backlog that's been growing for years.
Every team I know has a list of "we'd do this if we had the capacity." AI is the capacity.
If your response to that is "great, now we need fewer engineers" — you're managing the wrong problem.
Asked a buddy to offer feedback on a new site
Sends back a 5 minute audio file...
Dropped the audio file in NotebookLM -> had it convert each issue raised into a task with issue, steps to reproduce, and expected behavior
Gave it to claude code -> all fixed in < 1 hour
will button retweeted
Security Notice: Email Impersonation
A bad actor is impersonating Katana team members using domain we do NOT own, email@katana[.]foundation
All official comms from our team are from email@katana.network. Stay vigilant.
I ran an entire engineering project through AI agents. Let me tell you about the parts that sucked.
1/3
1. The PRD interview should’ve been a specialized skill. Raw conversation worked for a simple project but would’ve failed to gather requirements for anything more complex.
2. Agentic Amnesia As A Service. Every agent needs a profile and task description that stands on its own. Without this you have a team with great work ethic that doesn’t know shit.
3. 20 parallel agents sounds great until they edit the same file. Coordination is the hard problem, same as human teams. Except humans eventually learn to check Slack first.
4. One-shot solutions don’t exist. Iterate.
2/3
Tweets that pair well together: xitter.cf/feross/status/20388072…
