₿ENOWHERE

Product Lead @Bitkey

[₿ENOWHERE @BEN0WHERE]

Seed phrases were a breakthrough for Bitcoiners. But they also handed users the hardest part of the problem: securing them.

Bitkey takes a different approach.

https://t.co/zRUJKXiCIR

[Rijndael @rot13maxi]

I built a very small language model on plebslop.
How small? Small enough to fit in a single *standard* bitcoin transaction.

There is now a plebslop generator on every Bitcoin node.

The UI includes client-side inference code. It loads the weights and does it all in-browser

[Adam O'Brien - bitcoinwell.com @adamobrien]

This is the best swag I’ve seen at a bitcoin conference and it’s not even close

[Miles 🌞 @milessuter]

We just shipped stablecoins on @CashApp.

Everything runs from your existing USD balance - no separate wallet, no managing multiple chains, no extra setup, and importantly no fees.

Send and receive USDC on SOL, ETH, POL, and ARB.

The most seamless integration in the world imo.

[Mr.Hodldamus @MrHodl]

Bitkey product lead 🤝 MrHodl. 😂

[₿ENOWHERE @BEN0WHERE]

👋

I think this ultimately comes down to the question, "why not just allow seed export for the people who want it and know what they're doing?"

I think this is very reasonable, and ethos-aligned with self custody.

We fundamentally believe hardware devices should protect the key, not just sign with it. So our hardware is designed to never export its secret; the APIs simply don’t exist.

That gives us a very powerful security posture: there is only one copy of the HW key in the world, and access to it is gated by a physical device with biometrics.

I would hesitate to erode that property. But it’s clear that some customers, like yourself, would prefer to give up that property in exchange for having a direct copy of your key.

One way to support that, without weakening Bitkey’s non-exportability posture, would be to let customers set a seed phrase into Bitkey instead of having the hardware generate its own.

That would preserve the principle that Bitkey-generated hardware keys are never exported, while still giving power users a way to use the wallet with keys they have access to outside the wallet.

Would something like that get at what you’re trying to achieve?

[₿ENOWHERE @BEN0WHERE]

From a security perspective, the safest way to leave a wallet is a transaction.

If you use seeds to migrate keys, you carry forward the history of those keys: entropy quality, backup exposure, supply-chain risk, leaked metadata, unknown wallet bugs, etc. The new wallet inherits whatever latent risks existed before.

If instead you migrate wallets by transaction, you get fresh keys and a clean security boundary.

I agree with you that seed portability does have some convenient aspects to it -- no transaction fees, no consolidation considerations, not having to update your DIY seed-based recovery and inheritance system.

But I disagree that there's a sovereignty benefit to seed-based vs transaction-based exits. And most importantly, transaction-based exits are unequivocally more secure than seed-based exits.

[₿ENOWHERE @BEN0WHERE]

The app xpriv is already exportable.

The hardware is different. We fundamentally believe hardware devices should protect the key, not just sign with it. So our hardware is designed to never export its secret; the APIs simply don’t exist.

That gives us a very powerful security posture: there is only one copy of the HW key in the world, and access to it is gated by a physical device with biometrics.

I would hesitate to erode that property. But it’s clear that some customers, like yourself, would prefer to give up that property in exchange for having a direct copy of your xpriv.

One way to support that, without weakening Bitkey’s non-exportability posture, would be to let customers set a seed phrase into Bitkey instead of having the hardware generate its own.

That would preserve the principle that Bitkey-generated hardware keys are never exported, while still giving power users a way to use the wallet with keys they have access to outside the wallet.

Would something like that get at what you’re trying to achieve?

[TFTC @TFTC21]

Block and Spiral just launched Loupe, a free AI-powered vulnerability scanner for open-source Bitcoin projects.

The tool scans Bitcoin codebases for security flaws across millions of lines of code. It is available as a free "scanning-as-a-service" tool for any open-source Bitcoin developer.

As Bitcoin secures hundreds of billions in value and the codebase grows more complex, automated security scanning is no longer optional.

Block and Spiral say it is "mission-critical" for the ecosystem, especially as open-source developers face growing pressure to secure infrastructure that most of the world's financial system is increasingly building on.

[Bitcoin at Block @BitcoinatBlock]

No more someday. ₿itcoin is now. 🟠

We brought the whole Block party to @TheBitcoinConf this year: @square, @cashapp, @bitkey, and @protomining all under one roof.

Buy. Spend. Secure. Power. See you next year.

[jack @jack]

proof of reserves https://t.co/XuFpXxfjzU

[Bitcoin at Block @BitcoinatBlock]

Bitcoin only works if people use it.

Today at @Blocks, we’re making that easier:

• New @Bitkey with 100% more screen
• 5% BTC Back with @CashApp at @Square merchants
• Turn P2P payments into bitcoin on @CashApp
• Soon, NFC tap to pay and bitcoin toggle on @Square
• Proof of Reserves you can verify

This is how bitcoin becomes everyday money.

[Bitkey @Bitkey]

Meet the new Bitkey.

No seed phrase.
Multisig by default.
Built-in inheritance.

And now, with 100% more screen.

See what's new: https://t.co/wsBnYHYu73

[Curiosity @CuriosityonX]

Artemis II Trajectory compared to Apollo 11 and Apollo 13

[mononaut @mononautical]

crazy that Bitcoin is now being used to *prevent* boating accidents

[The ₿itcoin Therapist @TheBTCTherapist]

There was $2.4 billion in spot Bitcoin ETF volume today, Morgan Stanley launched the first Bitcoin ETF product by a bank, Iran demanded Bitcoin for passage through the Strait of Hormuz and Michael Saylor raised $150 million to buy more Bitcoin.

Most bullish bear market ever

[Miles 🌞 @milessuter]

Only $120,000 left in the @BitcoinatBlock faucet.

$880k worth of bitcoin stimmy in the hands of the American people already 🫡

[TFTC @TFTC21]

Block just open-sourced mesh-llm, a peer-to-peer system that lets anyone pool spare GPU compute to run large open-source AI models without relying on any cloud provider.

If a model fits on your machine, it runs locally at full speed. If it doesn't, the system automatically splits it across multiple machines on the network. Dense models get split by layers. Mixture-of-experts models like DeepSeek and Qwen3 get split by experts. Zero configuration required.

Discovery happens over Nostr. Nodes find each other through relays, score by region and VRAM, and self-organize. No central server coordinates anything. Weights are read from local files, never sent over the network. Dead nodes get replaced in 60 seconds.

It exposes a standard OpenAI-compatible API on localhost, meaning any existing AI tool can plug in without modification.

Block is building infrastructure for AI that doesn't route through OpenAI, Google, or Anthropic. Frontier-class open models running across a mesh of commodity hardware, discovered via Nostr, with no cloud dependency. That's the direction AI needs to go.

[a16z @a16z]

Inside Block: How AI Changes Software Development

Block's Owen Jennings sat down with a16z GP David Haber to discuss how AI is changing software businesses, including the end of handwritten code, why Block reduced its workforce by 40%, how small teams are doing more with agents, and more.

00:00 Introduction
09:08 The most meaningful difference in how Block is operating
12:57 AI infrastructure build across the org
17:09 The shape of the business: Square, Cash App, Afterpay
20:00 From static UI to generative UI
23:23 Defensibility in the AI era

@owenbjennings @dhaber @blocks

[Science girl @sciencegirl]

3D-printed joystick transforms your keyboard into a full arcade controller

[Vlad @VladArtym]

Okay I think I finally found a good use for @_chenglou 's Pretext.

A resume builder that always fits on one page
with realtime rendering.