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: ๐งต
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.
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.
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.
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.
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
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
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 protected]. Stay vigilant.