Some really neat send payment UX going into @Christoph Ono Arké wallet, based on some patterns established in @Bitcoin Design. By integrating with Bark, a wide range of payment formats are available immediately across Lightning, Ark, and on-chain. Video demo of Arké's send page dynamically reacting to what's held in the clipboard—fewer clicks and less to think about for the user:

Why Rust? Memory safety isn't optional when you're handling people's bitcoin. Type safety catches bugs at compile-time that would be runtime disasters in other languages. Performance matters too when you're processing hundreds of signatures per round.

Self custody is going to get a lot easier.

X (formerly Twitter)

Alby 🐝 (@getAlby) on X

An innovative wallet architecture for users of bitcoin apps 🚀 With @spark, Ark by @secondhq / @ArkLabsHQ, and @nwc_dev, it’s now possible to ...

The LSP business model has issues—high capital requirements, unpredictable revenue, complex liquidity management. Ark servers are simpler to operate and more capital efficient for similar use cases. We expect competition between the two models will drive better services for users.

Open source means anyone can fork our code and improve. We want that. If someone builds improvements on our Ark implementation, the ecosystem wins. Competition between implementations drives quality up for everyone.

Our goal isn't replacing Lightning. It's ensuring every bitcoin user can access Lightning without needing to become a node operator. Ark is the gateway—you hold a self-custodial balance, pay Lightning invoices when needed, no channel management required.

During a round, the Ark server + users construct a tx tree. Each leaf of the tree is controlled by a single user. The root of the tree is broadcast on-chain (the round tx). Once confirmed, each user has verifiable assurance they can unilaterally retrieve their bitcoin on-chain.

Kept you waiting, huh? (We're finally on Nostr)