openclaw was this year btw

We have won.

Metropolis project submissions are now live on the hackathon portal Submissions end October 13th at 11.59 PM ET $250,000 in prizes are on the line hackathon.monad.xyz hackathon.monad.xyz

“A lot easier” continues to show the ugliest sign up form I have ever seen

Gold lending has been quoted every working day for fifty years, yet is still closed to almost everyone who owns the asset. Institutional minimums, bullion bank relationships, settlement infrastructure. PAXGy changes that. Live today on @okx and onchain on @Uniswap, @XLayerOfficial, @0xProject, @ether_fi, powered by @chainlink CCIP. Gold that grows. paxgy.com/x

S&P GLOBAL ANNOUNCES AGREEMENT TO ACQUIRE OPENZEPPELIN: PRN

crypto and ai are converging on the insight that TEEs/confidential compute is endgame technology bc of verifiability and programmable privacy excited to see where this lands (and maybe read my post from 2024 on the 5 levels of secure hardware below)

We finally cracked it! We built an open-source video editor that turns every edit into code. I got tired of agents: → Losing context → Giving me outputs I couldn’t modify So we flipped it: → Code is the new database.

what it feels like using Opus 5

have you found the smoking gun to make the output less load-bearing?

Lost my phone at the office and spent 30 minutes turning the place over. Find My was disabled by MDM. Out of ideas, I asked Claude how I could find it. It suggested tracking the Bluetooth signal strength, then wrote me a meter in about a minute. I walked around watching the number climb. Found it. Apparently you can just make the tool you need now. Code: github.com/ben-z/findphone

Today we are releasing Cloudflare OS, a chatbot with connectors, just like every other tech company is doing. Except actually, it's different. This is a remake of Sandstorm[.]io, my startup from 10 years ago, except this time built on Cloudflare Workers (the platform I've spent the last 9 years building) and deeply leveraging AI. This is more or less the culmination of my secret 10-year master plan. This is a full-on personal app vibe coding platform, in which the sandbox is so secure that you can pretty much go wild -- the AI cannot introduce a significant security bug. We believe a company's security team can feel comfortable giving non-technical users permission to vibe code and then sleep soundly at night. How is that possible? It's the Sandstorm security model, revisited. A "Gadget" is the same thing as a Sandstorm "Grain": a fine-grained app instance. For example, if you have a document editor app, each document runs as a separate instance of the app, in a separate sandbox (one "Gadget"). This means two things, both of which I think are Big Deals: 1. The platform can manage all access control, by controlling who can access the Gadget at all. There is no way the Gadget can accidentally leak itself to an attacker -- even an attacker who has access to other Gadgets based on the same app. 2. Since everyone is running their own copy of the code, everyone can freely *modify* their copy of the code. Think about #2 a bit more. What if, when you wanted a new feature in the software you are using, you could just prompt your agent to add it? This doesn't work in the cloud Software-as-a-Service model, because you are not running your own copy of the app. Sandstorm tried to change that 10 years ago, but the world wasn't ready, because not enough people had the skills or patience to actually modify their software. AI has changed that. Now you just ask the agent -- the same agent that you are using to help you interact with the Gadget can also modify the code of the Gadget. And it is so fun. github.com/cloudflare/cloudf…

Build Wealth. Earn more. Simple.

Shoutout @dave2peer for casually bringing sales for actual equity on-chain. USDC -> Actual Shares in seconds (No SPVs) for US users is huge.

Finally, sudo make me a sandwich is reality.

As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes: 1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship 2. Builder: quickly turns a prototype/idea into production-grade product/infra 3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance 4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit 5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS. A healthy team needs a mix of these, depending on the product: - A product that is new and pre-PMF needs people that are strong at 1+2+3 - A product that is growing and has found PMF needs 2+3+4 and some 5 - A product that has strong PMF needs 3+4+5 and some 2 Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?

Bro 😭

You can’t be serious

1/n) is just twitter people writing 'First of all...'