CraysLN Node
LN Node is not a normal wallet app. It is a managed path into a user's own Lightning node, with Nostr-signed actions, LN Link URLs, Taproot Assets support and an NWC-compatible interface for apps.
A node product, not a pocket wallet
LN Node sits in the wallet shelf because it can act as a wallet backend for apps, but it should not be described like a simple mobile wallet. Lnfi Network presents it as a self-custodial, open-source Lightning node that lets users manage Bitcoin, Taproot Assets and RGB assets through LightningFi. The earlier NostrAssets docs called the same idea MicroNode: a service for creating and managing a Lightning node without requiring technical proficiency.
That difference changes everything. A normal wallet hides node operations. LN Node exposes them in a guided product: enable nodes, manage Taproot and RGB nodes, create channels, provide liquidity, generate LN Link/NWC-style connections and interact with Nostr apps. The user is not only sending and receiving. The user is operating a node-like financial surface.
For readers, the main question is whether they actually want a node workflow. LN Node may be useful for people who want app-connectable Lightning infrastructure, Taproot Asset experimentation and channel-liquidity rewards. It is probably overkill for someone who only wants a basic zap wallet. The power is real, and so is the operational weight.
From MicroNode to LN Node
The Awesome NWC list still points to the older MicroNode early-access documentation under the NostrAssets domain. That page describes MicroNode as an early-access service that installs and uses lnd, tapd and TAHub to simplify Lightning node management. The current Lnfi documentation now names the product LN Node and places it inside the wider Lnfi Network product line.
The name change is more than branding. The current documentation connects LN Node to LN Link, Channel Mining, Taproot Assets node management, RGB node management and Zapper accounts. The terms page was last updated on February 15, 2025, while the wider Lnfi terms were updated July 12, 2025. The old docs remain useful for the origin story, but the current docs are the better guide to what a reader should evaluate today.
This matters because the ecosystem map can make LN Node look like just another NWC wallet. It is not. LN Node is a product family around a managed self-custodial node, with Nostr and NWC-compatible control paths. A good article has to preserve that shape instead of flattening it into a generic Lightning wallet.
The technical stack is lnd, tapd and TAHub
LN Node's documentation names three core components. Lightning Network Daemon, or lnd, is the Lightning node software used for routing and Lightning transactions. Taproot Assets Daemon, or tapd, implements the Taproot Assets protocol and supports asset issuance and transfer. TAHub acts as the intermediary that lets lnd, tapd and Nostr clients or apps exchange information.
That stack explains why LN Node is more ambitious than a Bitcoin payment wallet. It wants to connect Bitcoin Lightning, Taproot Assets, Nostr identity and app payments into one user-facing node product. The old MicroNode page describes payments in Bitcoin and Taproot Assets, liquidity provision and interoperability with Nostr apps. The current LN Node page adds RGB assets to the set of supported asset-management surfaces.
The reader should keep those layers separate. lnd handles Lightning node behavior. tapd handles Taproot Assets. RGB has its own asset model. Nostr handles identity and message transport. LN Link and NWC-style events are the app-facing control layer. When something works, several layers are cooperating. When something breaks, several layers may need debugging.
Self-custody means the seed is the user's problem
The LN Node GitHub README states the core custody claim plainly: users exclusively hold the LND seed, and only they control their funds. The old MicroNode disclaimer says NostrAssets does not retain backups or copies of user passwords, seed phrases or access materials. It also says the team cannot help if a seed phrase or password is lost.
That is real self-custody in the most unforgiving sense. A user can gain control, but control includes the ability to lose access permanently. A managed interface can make node creation easier, but it cannot make seed handling casual. If the seed or password is lost, leaked or stored badly, the money risk belongs to the user.
Before using LN Node with meaningful funds, write down the recovery process, test what can be recovered, understand what cannot be recovered, and avoid mixing experimental app connections with savings. Self-custody is a promise and a burden. LN Node gives the user more direct control than a custodial wallet, but it does not remove the need for disciplined backups.
Nostr is the authorization and app layer
LN Node uses Nostr for more than branding. The GitHub README says user actions are signed and authenticated with the Nostr private key, ensuring genuine user authorization. The earlier MicroNode docs describe an interoperable sovereign Nostr identity and communication between Nostr clients, lnd and tapd through TAHub.
That design fits the wider Nostr wallet pattern. Instead of asking every app to hold node credentials or every node to expose a traditional web API, the user can authorize actions through Nostr-based messages. This lets apps request payment or node actions while the wallet or node service retains a constrained control boundary.
The privacy and security tradeoffs are worth naming. Nostr keys can become authorization keys. Relays can become infrastructure dependencies. App connections can create metadata about payments and node behavior. LN Node's approach is powerful because it makes node control portable, but readers should treat Nostr identity and wallet-control identity as sensitive, not decorative.
LN Link is the NWC-compatible bridge
LN Link is the part of LN Node that most directly explains its appearance in the NWC ecosystem. The current docs say LN Link builds on Nostr Wallet Connect. The GitHub LNLink README says it is built on Nostr and compatible with NWC. It describes a standardized way for clients to access a remote LN Node.
The documented event support follows NIP-47: info events use kind 13194, requests use kind 23194 and responses use kind 23195. The current supported NWC methods are get_info, get_balance, pay_invoice, make_invoice, list_transactions and lookup_invoice. That is enough for many wallet-connected apps to check capabilities, create invoices, pay invoices and reconcile history.
The limitations matter. The README says amount is not supported for amountless invoices in pay_invoice, and that the PAYMENT_FAILED error code is not supported. A developer or power user should not assume perfect drop-in compatibility with every NWC client. Test the exact client, exact invoice type and exact error path before using it in production.
LN Link goes beyond base NWC
LN Link is not only a copy of NIP-47. The API documentation adds an asset_id field to payment requests, marked as an LNLink feature. That makes sense in the Lnfi context because LN Node is meant to work not only with BTC invoices, but also with Taproot Assets and eventually broader asset flows.
This is where readers need to slow down. NWC is already a wallet-control protocol. Extending it toward Taproot Assets and node liquidity makes the integration more expressive, but also more specialized. An app that understands normal Lightning invoices may not understand asset-specific payment semantics. A wallet connection that looks familiar may carry extra assumptions.
For app builders, the safe route is to treat LN Link as NWC-compatible plus Lnfi-specific extensions. Use the base methods when you only need normal wallet behavior. Use the extra fields only when both sides explicitly support them. A failed asset payment should not be allowed to masquerade as a normal Lightning failure.
Connecting to Alby shows the practical flow
The LN Link documentation gives a concrete example with Alby. It says Alby Wallet was one of the first to support NWC, and that users can import their LN Node and manage assets in Alby by generating an NWC string from LN Node, copying it, opening the Alby Chrome Extension and connecting a wallet.
That flow explains how LN Node becomes usable outside the Lnfi interface. The node is the wallet service. The app or extension is the client. The NWC string carries the relay and secret information needed for the client to talk to the node. Once connected, the app can request supported actions.
This is also where caution belongs. An NWC string is a credential. It should be scoped, stored carefully and revoked when no longer needed. If an extension, website or app asks for the connection, the user should know exactly what the connection can do and what budgets or restrictions apply. A node connection deserves the same care as a wallet connection.
Channel Mining is not a passive wallet feature
Lnfi's current docs describe Channel Mining as a way for LN Node users to earn rewards by providing liquidity and facilitating transactions on the Lightning Network. The page says rewards are limited to one channel per LN Node, lists a minimum channel capacity of 1,000,000 sats and a maximum of 10,000,000 sats in the current phase, and discusses reward tokens such as TRICK and TREAT.
That is not the same as receiving a Lightning payment. Channel Mining means capital is placed into a channel so it can provide network liquidity. The docs say this is secured by the Lightning Network and held under user self-custody on Bitcoin mainnet, but readers should still evaluate liquidity, channel closure, fees, reward terms, token risk and terms-of-service changes.
A phrase like yield can make a technical feature sound passive. In reality, Lightning channels are operational objects. They need capacity, fees, counterparties and monitoring. LN Node may make that easier, but the user still needs to know what is locked, where the rewards come from and what happens if the channel is closed.
Taproot Assets and RGB widen the risk surface
The current user guide includes pages for Taproot Assets node management and RGB node management. The Taproot Assets page describes mainnet deposit, channel creation, channel deposit and withdrawal, and notes that BTC is needed to cover channel fees. The RGB page describes creating UTXOs, RGB channels, channel deposit and withdrawal, and invoice prefixes.
That breadth is impressive, but it turns LN Node into a multi-asset node interface. A reader who only understands ordinary Lightning invoices should not assume they understand Taproot Asset or RGB channel behavior. Asset-specific payment requests, channel setup, counterparty node information and fee requirements can all introduce new ways to make mistakes.
For now, the strongest advice is to test one layer at a time. Learn the BTC Lightning path first. Then learn Taproot Assets or RGB with tiny amounts or test environments. Do not combine a new asset type, a new Nostr app connection, a new channel and meaningful capital on the same first day.
Zapper accounts add another delegation layer
The Zapper Accounts documentation describes creating an account from the Dapp-Zapper page, assigning an EVM address as the recipient, setting a budget and sharing a QR code or account URL. The recipient can then connect the corresponding EVM wallet to manage and spend the assigned budget.
This is a different shape from a normal Lightning wallet. The user is creating delegated spendable access with a budget and an account URL. That can be useful for campaigns, rewards, zaps or controlled app spending, but it also adds a second identity layer beyond Nostr and Lightning. The presence of an EVM address should make Bitcoin-only readers pause and understand exactly what is being authorized.
The correct way to use delegated accounts is conservative. Keep budgets small, give each account a clear purpose, rotate or delete accounts when the purpose ends, and do not use the same setup for treasury funds. Delegation is useful only when the boundary is clear.
Terms and disclaimers are not decorative
LN Node's terms say the service includes AI-integrated management, channel mining and other advanced features. They also say information may not be complete, accurate or current and that users assume responsibility for relying on it. The broader Lnfi terms define LN Node as one of the products covered by the agreement.
The old MicroNode disclaimer is even more direct. It says real assets are involved, emerging technology can have unforeseen risks, the platform can be modified or discontinued, and self-custodial users are responsible for seeds, credentials and node configuration. Those warnings belong in the reader's mental model because LN Node is still a complex product in a fast-moving stack.
A user should not rely on interface polish to measure risk. If a feature involves real channels, Taproot Assets, RGB assets, zaps or delegated budgets, read the terms, test tiny amounts and keep recovery materials safe. LN Node can lower technical friction, but it cannot make emerging LightningFi infrastructure risk-free.
What to verify before using LN Node
Start with product access and documentation age. Some old MicroNode pages were early-access and whitelist-focused, while the current docs now use the LN Node name and include updated sections. Make sure the interface you are using matches the current docs, and do not rely on screenshots or instructions from a different generation of the product.
Then verify the custody setup. Create the node, record the seed and password, understand whether recovery has been tested, and learn what the team can and cannot recover. If the product says the user exclusively holds the LND seed, then the user must behave like a node operator, even if the interface feels managed.
Finally verify the app connection. Generate an LN Link or NWC string, connect it to a known client, run tiny invoices, test unsupported amountless invoice behavior, check list and lookup responses, revoke the connection, and confirm that revocation works. A wallet-control protocol should be tested before it is trusted.
Where LN Node fits in the wallet map
LN Node belongs near wallets because it can serve wallet functions to apps. It belongs near developer and Lightning infrastructure because it exposes node, channel and asset behavior. It belongs near Nostr because Nostr keys and relays carry authorization and connection messages. That hybrid nature is exactly why it is interesting.
It should not be compared only with simple mobile wallets. A fairer comparison is Alby Hub, LNbits, Electrum with NWC, and hosted node products. LN Node's distinctive angle is the combination of self-custodial node seed, LN Link, Taproot Assets, RGB, channel mining and Nostr-signed app control.
The result is powerful but narrow. If a reader wants quick zaps, LN Node may be too much. If a reader wants to experiment with Nostr-controlled Lightning infrastructure and asset channels, LN Node is one of the more ambitious projects in the NWC neighborhood.
The bottom line
LN Node is a serious infrastructure entry in the Nostr wallet ecosystem. It takes the NWC pattern and pushes it toward a broader node product: lnd for Lightning, tapd for Taproot Assets, RGB management, Nostr-based authorization, LN Link connection strings and liquidity workflows.
That ambition is also the reason to be careful. There are more moving parts than in a normal wallet, and some documented features are early, specialized or tied to reward systems. Users should start small, read the terms, protect seeds, and test every app connection before letting it move real funds.
For the right reader, LN Node is worth opening because it shows where Nostr Wallet Connect can go when the wallet is not just an account but a programmable node. For everyone else, it is a reminder that app-controlled money should become easier without becoming casual.
Sources worth opening
Open the current LN Node product docs, LN Link docs, terms, GitHub README, LNLink API file, old MicroNode early-access docs, NIP-47, lnd and Taproot Assets references before deciding whether LN Node fits your wallet or app workflow.
- Lnfi LN Node product page
- Lnfi LN Node user guide
- Lnfi enable nodes guide
- Lnfi Taproot Assets node management
- Lnfi RGB node management
- Lnfi Zapper Accounts
- Lnfi Channel Mining
- Lnfi LN Link documentation
- LN Node terms of service
- Lnfi general terms
- Lnfi brand kit
- LN Node GitHub repository
- LN Node GitHub README
- LN Node MIT license
- LNLink README
- LNLink API documentation
- Old MicroNode early-access page
- Old MicroNode user guide
- Old MicroNode Connect page
- Old MicroNode disclaimer
- NostrAssets general disclaimer
- NIP-47: Nostr Wallet Connect
- Nostr Wallet Connect official site
- NWC documentation
- Lightning Labs lnd
- Lightning Labs Taproot Assets
- Taproot Assets documentation
- RGB protocol project
- Awesome NWC wallet list
