Dev

Building @getaxal

[Ben Zhang @un1c0rnioz]

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: https://t.co/fmnISzHfZ2

[Kenton Varda @KentonVarda]

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.

https://t.co/qzwdrAQhtK

[Dev @dev1_sh]

Build Wealth. Earn more. Simple.

[Axal @getaxal]

Proud to work with @DinariGlobal to be the first consumer fintech offering tokenized US securities to Americans 🇺🇸

Our mission is to the best wealth app on Earth, and having the best version of publicly traded assets is essential.

[Dev @dev1_sh]

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

[Dinari @DinariGlobal]

Today, Dinari becomes the first to bring regulated tokenized US securities to investors and businesses in the United States 🇺🇸

The entire S&P 500, live as dShares™. Onchain and accessible 24/7 for the very first time in the US.

Do more with your stocks.

[Paul Graham @paulg]

Finally, sudo make me a sandwich is reality.

[Dev @dev1_sh]

https://t.co/FtB21N1XiF

[Cuy Sheffield @cuysheffield]

1/ Today, we announced Visa is joining Open Standard alongside Stripe, Coinbase, Mastercard, American Express, Blackrock, US Bank, BBVA, Standard Chartered and 100+ initial partners with the mission of issuing Open USD, a shared stablecoin designed for the global financial system.

[Boris Cherny @bcherny]

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?

[Dev @dev1_sh]

Bro 😭

[OpenAI @OpenAI]

Introducing a limited preview of GPT-5.6 Sol, our next generation frontier model, as well as GPT-5.6 Terra, a balanced model for efficient, everyday work, and GPT-5.6 Luna, a fast and affordable model for high-volume work.

https://t.co/OoM83SyISN

[Lily Liu @calilyliu]

You can’t be serious

[Dev @dev1_sh]

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

[Stacy Muur @stacy_muur]

Read the new Morpho paper so you don't have to!

Quick context: @Morpho is one of the biggest lending protocols on Ethereum, with billions in deposits. Their core product, Morpho Blue, lets anyone spin up isolated lending markets with custom collateral and risk settings. Most of DeFi credit gets built on top of it now.

They just released the Midnight whitepaper, a new lending protocol where rates are fixed and loans have a set end date, instead of the floating-rate pools everyone's used to.

Think Aave or Compound: you deposit, your rate moves with utilization, you withdraw whenever. Midnight is the opposite. You lock in a rate and a date upfront, like a CD at a bank.

The pool model worked when liquidity was thin and gas was expensive. With $25B+ in onchain loans now, floating rates and forced pooling are real bottlenecks. A treasury that needs predictable costs can't use a pool that swings 20% overnight.

How it works:

Lenders and borrowers trade "units" that act like IOUs with a fixed payout at a future date. Each market has a loan asset, end date, and collateral. Buy units = lend. Sell units = borrow. The rate is just the discount you trade at: pay $0.95 today, get $1 in six months.

All markets with the same end date pool together, no matter when you entered. So liquidity builds up instead of splitting across a thousand separate loans.

The interesting parts:

• No orderbook. Lenders post signed offers without locking capital. Borrowers find them off-protocol (Telegram, frontend, router) and submit. The protocol just settles.

• Capital stays productive. A lender can keep funds earning on Morpho Blue and quote fixed-rate offers on Midnight at the same time. When someone takes the offer, funds get pulled and the trade settles in one tx. The "idle capital waiting to be matched" problem that broke prior fixed-rate DeFi is gone.

• One pool, many markets. One signature can back offers across dozens of markets at once, like a market maker quoting 30 stocks with $10M total instead of locking $10M into each. Total risk stays capped at actual balance.

• Fairer liquidations. A 1% breach can't nuke your whole position, liquidators only repay enough to fix it. Bad debt is realized instantly. Miss repayment by a few minutes? 15-minute grace ramp instead of instant drain.

• Fee caps locked forever. Settlement fee maxes at 50 bps/yr, lender fee at 1%/yr. Can't be raised.

Morpho's bet: onchain credit should look like fixed income, not money markets. If serious makers can quote across many markets with one pool of capital, fixed-rate lending might finally work at scale.

[Dev @dev1_sh]

@Mawuko @sui414 @CloberDEX So down to attend this

[Axal @getaxal]

Axal is grateful for the whole @monad team - tremendous support across the board! Fast execution, emerging yield sources, and a great community.

[Dev @dev1_sh]

🕰️...

[Axal @getaxal]

To celebrate @Bitcoin coming to Axal, we're hosting a launch party in the world famous Bitcoin bar, @PubKey NYC.

Exclusive to Axal users and alpha group members.

Want in? DM us!

[Dev @dev1_sh]

How it feels hearing the terms 'Deploy', 'Launch', 'Release', 'Test Flight' and 'Microsoft Outlook' being used for the Moon mission:

[Dev @dev1_sh]

CCTP for cirBTC would be v welcome and much needed. But the broader issue is 1:1 BTC to cirBTC bridging - which, with KYC requirements, will remain a problem. MTL businesses with AML/KYC compliances can definitely use this with Circle Mint to achieve this though.

[Circle @circle]

Circle Wrapped Bitcoin is coming.

Backed 1:1 by BTC and readily verifiable onchain, cirBTC is being built to work seamlessly with Circle infrastructure and the broader DeFi ecosystem.

Learn more: https://t.co/wWzVBZdIz1

[chloe 🐇 @SapphoSys]

world's first enterprise solution to reach zero nines uptime

[Axal @getaxal]

Axal has no exposure to Drift Protocol.

No underlying vault strategies have allocations deployed through Drift.

As always, allocations can be verified independently in your Axal account.

[Ash Ahmed @ashlan_ahmed]

A universal wealth app is smart, intuitive, and multi-asset.

@getaxal intends to be humanity's wealth app.

Humanity cares about dollars, gold, bitcoin, land, real estate, collectibles.

Own something. Earn on it.

Dollars and Bitcoin - just the beginning.