CLN is an advanced Lightning implementation that usually requires you to figure things out yourself. Like a race car vs automatic: race guys love the control; others get frustrated fast by the complexity. Even as a long-term contributor for more than 5 years, CLN feels like a Pandora's box these days. Not saying @ocean_mining's LN setup is easy; just choose the right tool for your experience level with Lightning and that stack. There are solutions like @lexeapp out there that make stuff easy to receive, and if you want to experiment a bit, you can check nitter.siddz.com/PalazzoVincenzo/status…

Landfall, built by @PalazzoVincenzo, is a huge improvement in the onboarding experience for OCEAN miners. We've just added it to our showcase here: docs.lexe.tech/showcase/#lan…

What happens when you give an agent its own Lightning wallet? @MaxAWebster walks through his experiment with @lexeapp, where an agent set up its own wallet, built a Nostr Wallet Connect bridge, and started buying domains and email addresses ↓

LexeConnect is a great feature that every wallet should consider implementing. If you maintain a wallet take a look at the protocol spec: github.com/lexe-app/lexe-con…

Congrats @lexeapp, @MaxFangX and @phlip9 on shipping LexeConnect. Connecting Zaptrain to Lexe is now one tap. Tap Connect Lexe, approve in the Lexe app, done. No keys to copy. We only ask for receive-only access. Money comes in, none can leave.

Introducing LexeConnect: a new protocol to connect a Lexe wallet to your app in one tap. Your app requests the scopes it needs. The user taps Approve in Lexe. Your app receives a scoped, revocable credential and can now receive, pay, or read from the user's wallet. Full video 👇

Hashing/Heating season just kicked off in Wyoming. I used @lexeapp last year to get payouts from OCEAN. And this year that got even better with this app called Landfall that @PalazzoVincenzo built!! github.com/vincenzopalazzo/l…

Shoutout to @jonhbit, who rebuilt the @mitDCI vending machine to accept Lightning payments, using Lexe as the receiving wallet! - Accepts payments to a static payment address: ₿mitdci@lexe.app, payable as a Lightning Address or Human Bitcoin Address (BIP 353) - Vending machine holds only a view-only client credential to its Lexe wallet, root seed held on a separate device - Infinite inbound liquidity provided by Lexe - Historically sold only Soylent, the pinnacle of human cuisine

Lexe's project showcase was just updated! It shows off the myriad ways in which people use Lexe. docs.lexe.tech/showcase/ Read to learn how: - Miners with OCEAN (@ocean_mining) use Lexe to receive Lightning payouts - @ZapriteApp adds a social layer so it is easy to request Bitcoin payments from friends and family - @getzaptrain built an entire self-custodial e-commerce stack on Lexe, under a revenue sharing model - @SatoshisPlace, @1phash, and @lightningrouter use Lexe to accept payments 24/7, without worrying about liquidity And more!

A new kind of Bitcoin payment gateway just dropped. Zaptrain is now live! @getzaptrain: • Helps you accept Lightning payments • Hosts checkout flows and payment links for you • Doesn't have any control of your funds • No KYC or bank details required Repeat: You can now accept Lightning payments while running 0 infrastructure yourself, without giving anyone control over your funds! How does Zaptrain work? Using Lexe's new credential scopes feature, you can now create a revocable credential with receive-only access to your Lexe wallet, and give it to Zaptrain. Zaptrain can create invoices and check on payment status on your behalf - and nothing more. Zaptrain hosts payment links, a checkout flow, a payment tracking web portal, and a REST API for you. Powered by the Lexe SDK and Lexe's self-custodial Bitcoin infrastructure. Video below 👇

Someone created an agent-to-agent board where agents create their own Lexe wallet via the Lexe CLI, then register onto the board using their Lightning Address. And there are small bounties for agent-friendly businesses 👀 postswarm.dev/

Lexe is possibly the first Lightning wallet to support BOLT 12 payer proofs! You can try it out now in our CLI and SDKs via the `create_payer_proof` method. 👇 docs.lexe.tech/cli/#create-p…

Big fan of @lexeapp, I use it personally and it works great with our P2P app. Our P2P app is not a competitor to wallets. It depends on them & delivers compounded value on top of a wallet's core function for a specific payments use case, increasing the value of the wallet.