This is new! It seems there is a new way to run wallets on mobile, perhaps a similar approach to what @justin_shocknet is doing with Shockwallet and Lightning.pub, but totally different infrastructure.Thoughts?
- Node always online on a server
- The web app simply plugs into it.
- Plug to any LSP
- Make your node an LSP
An on-chain and pure-Lightning bitcoin wallet that runs anywhere. No account. No middleman. No one watching. Your key, your money.
Five reasons this is a fresh start
Pure Lightning, real bitcoin
On-chain bitcoin and Lightning. No Spark, no Ark, no custodian you can’t audit.Anyone with a node can be your LSP
LiJ is built on the open LIJOX standard: if you run a Lightning node, you can serve LiJ wallets and put your bitcoin to work supporting the network — full control, no gatekeepers, designed for LSPs to compete for your business.Your bitcoin key is your Lightning key
The same 12 words work in any ordinary bitcoin wallet. Done with LiJ? Take your key and walk away, any day.Always-on is the LSP’s job. Control is yours
The standard splits the work: the LSP stays online; your wallet has the keys, the privacy and the decisions.Wallet independence. Offline recovery
A WebAssembly app written in Rust — no app store, no account, no gate. Provider goes dark, you still have control.
Operators: the network is open
LIJOX is the open, permissionless standard LiJ speaks. Register your node, run the adapter, and serve wallets on your terms — your liquidity, your fees, your rules.
Read the standardGet the adapter
Open a channel to LiJ-Node
Bring liquidity to the wallet’s LSP. Fund a channel to LiJ-Node from your node: on Tor, dial the URI below. Not on Tor? Send your node URI through the LIJOX repo and LiJ-Node will dial you — then open from your side.
Screenshots
Code
Wallet repo: https://github.com/dav1dpgit/lightninginajar
LIJOX repo: https://github.com/dav1dpgit/LIJOX
LIJOX adapter for node runners: https://github.com/dav1dpgit/lijox-lnd-adapter
The architecture (mobile LDK keys + always-online LSP) is the proven Greenlight/Breez-SDK shape, so the interesting claim isn't the split, it's LIJOX as a permissionless-LSP standard. Fair test for any new wallet standard: can two independent implementations interoperate without the reference adapter? History says new standards fragment first (see the LNURL vs offers split) and unify much later.
On the actual interop gap for pay-per-call: static BOLT-11 is the bottleneck. Single-use, no reusable price offer, no refund path, no machine-readable terms, so every metered-API integration bolts on a side channel (LNURL-pay callbacks work today but drag in an HTTPS-server trust model). BOLT-12 offers are the standards-track answer: reusable offers with amount, expiry and quantity metadata, plus blinded paths so the endpoint doesn't leak its node. That's what makes metered calls composable instead of bespoke per vendor.
So judge LiJ less on "another wallet" and more on whether its standard speaks offers natively. Permissionless LSP competition lives or dies on liquidity depth, not protocol docs, but a wallet standard with BOLT-12 request negotiation baked in would genuinely unblock pay-per-call.
I like the separation of responsibilities here. The user keeps the keys while the infrastructure handles the always-online part. If the LSP layer stays open and competitive, that could make Lightning wallets a lot less dependent on a single provider.
Will have a look closer at some point, but at a glance this still seems to be running a mobile node (LDK) and the middleware is an LSP.
Decentralizing LSP's good, but more mobile nodes bad.
... but at least it's not another fake L2 wallet.