pull down to refresh
We include an .aab with each of our releases - hand it over to your agent and it should be able to convert it into an APK for you. Here's our latest release: https://github.com/lexe-app/lexe-public/releases/tag/app-v0.10.9%2B65
Noted on Obtainium; with a little bit of work we should be able to include .apks with all of our mobile app releases as well.
Hey! Lexe co-founder here. Yes, please give us a try! We've done what we can to mitigate vulnerabilities in SGX, and have written extensively about it here:
https://github.com/lexe-app/lexe-public/blob/master/SECURITY.md
We are also big believers in defense-in-depth, which is why we've taken such extreme pains (TLS-in-TLS reverse proxy) to ensure that user nodes aren't exposed to the public internet. We're also one of the very few companies out there with a bit-for-bit reproducible enclave build. I still wouldn't want you to put in any more than you're comfortable with however :)
It would be possible, but there's a balance we have to make here: if a spec is too complicated, most wallets will only implement a subset of it, and the end result is that the spec leads to more fragmentation in the ecosystem, rather than less. We already see this somewhat, with NWC defining lots of methods that only a minority of wallets support such as hold invoices or keysend payments. So there is an argument for keeping NWC simple, so that when a wallet says “we support NWC” everyone has a common understanding of what that means.
LexeConnect is designed to work with Lexe wallets and Lexe client credentials, which is why we didn’t name it something more generic. We certainly don’t intend for this to compete with NWC. I think the typical integration order for an app or service is: (1) support NWC including NWC-08. (2) If you have a more direct integration with Lexe, or want to make use of Lexe’s more advanced features with the subset of your users that are Lexe users, then integrate LexeConnect and Lexe’s SDK.
Btw, we published LexeConnect as CC-BY 4.0, so that other wallets are welcome to reuse and set their own parameters for our protocol if they need a simple and secure way to share a credential. I just don’t expect them to use this flow for NWC connections, since NWC already has a blessed way to offer this kind of UX with NWC-08.
The Paygate and BillSplit examples are fictional, intended to show what the flow looks like. But there are two apps which have already integrated LexeConnect for real:
- Zaptrain: https://zaptrain.com - a payment gateway where merchants hand over receive-only credentials to their Lexe wallet. Indeed, this is easier than BTCPay Server because merchants don't have to host their own checkout pages - Zaptrain does it for them. cc @zaptrain
- Zaprite P2P: https://zapritep2p.com/ - a peer-to-peer payments app where users can request payments from contacts, and connect their Lexe wallet in one tap. @zaprite
I agree the BillSplit example is a bit contrived, but one thing I've very excited about is subscriptions and pay-as-you-go. Once we have budgets built, you'll be able to share your credentials to a website similar to OpenRouter, which has a spending limit of say $10 a month, and have it draw from your Lexe balance as you consume inference tokens. Basically, any form of pull payment is possible with LexeConnect. You can think of Lexe's client credentials like a credit card with a spending limit attached.
Good question. LexeConnect and Lexe's client credentials are intended to make full use of Lexe's capabilities, some of which don't exist in the NWC spec, for example: on-chain payments, BOLT 12 payer proofs, partner fees, private payment notes, cancelling payments, syncing payments to disk, tailing the payments list, sending payments idempotently, etc.
We are fans of NWC and plan to integrate it, along with NWC-08 which offers a UX very similar to LexeConnect!
Lexe with NWC would be a really interesting wallet option. I see NWC is still on their roadmap. Hope they get to that sooner than later.
Yes, NWC has been consistently one of our top feature requests. We're working on it!
Cool. Was this built by the lexe team?
We didn't build it ourselves! It was built by some friends of ours who are fans of Lexe and excited about agents sending and receiving Bitcoin without humans in the loop.
Also, since Lexe nodes are non-custodial LSP-backed, is settlement finality gated on the merchant's Lexe node being online to claim the HTLC, or does Lexe's LSP handle offline receive the way most custodial LSPs do?
Lexe co-founder here. Since your node runs inside a secure enclave inside our infrastructure (which we cannot read inside), we can guarantee that your node is always online to receive a payment. So payments can finalize immediately, even when your phone is offline.
Self-custody means only you hold the keys and no one else can spend your money, which is exactly what Lexe provides.
If you want to make payments from your Lexe wallet without using any of Lexe's hardware, then you can run a LDK node on your own machine using your Lexe seedphrase and channel state and make payments that way.
You can continue to waste everyone's time keyboard warrioring for your own revisionist definition of "self-custody" while also completely failing to understand how Lexe works, but that doesn't change what everyone else understands "self-custody" to mean.
If our server or domain goes away, users recover their funds from their channel state backed up in their Google Drive. What's the problem here? You still haven't named a single thing that could go wrong with our architecture.
False. We don't have control either, and can't read the user's secrets - that's the point of running the node in a TEE. All node code is open-source, auditable, and bit-for-bit reproducible, and clients verify the enclave's remote attestation before connecting.
Educate yourself.
You should definitely try out Lexe! We've been working with Ocean for a long time now, and a lot of our users come from Ocean. Lexe's mobile app is one of the easiest ways to get a Lightning node online 24/7, with free node hosting. And we're self-custodial, unlike Coinos. We're also fans of Phoenix but with Phoenix you'll have problems receiving whenever your phone is offline.
Lexe is has a lot of liquidity and is trying to monetize it, or ordinary LSPs providing liquidity?
We provide the liquidity ourselves but we're not really trying to make money off of it. Liquidity is currently free, but in the future we'll charge for it at a rate of about 212 sats per 100k sats of liquidity per week to cover our costs.
Update: I've uploaded our canonical .apk to the link above. No AAB munging needed.