A small open-source project called Landfall aims to make an awkward task easier for Bitcoin miners: configuring OCEAN pool rewards to arrive over the Lightning Network. The experimental wallet combines a mining payout address, reusable Lightning BOLT12 offer and proof-of-ownership signature under one recovery phrase. Bitcoin Optech highlighted Landfall on October 23, 2026. Its developer explicitly calls the code a demonstration rather than a production-safe wallet.
Video context: An independent 2026 walkthrough shows a Lexe wallet receiving OCEAN mining rewards over Lightning. It explains the underlying payout workflow; it is not a demonstration or security audit of Landfall. Watch directly on YouTube if the player is unavailable.
Why pool payouts require three separate pieces
OCEAN can send eligible mining rewards over Lightning instead of paying each small miner in an on-chain transaction. To configure the path, a miner provides a conventional Bitcoin receiving address, a BOLT12 offer describing where Lightning funds should arrive, and a BIP322 message signature proving control of the registered payout address. Each component serves a separate purpose: identify the mining account, specify the payment destination and prevent unauthorized redirection.
Ordinary wallets do not always expose compatible message-signing tools or reusable Lightning offers. Misreading a copied address, signing a different message or configuring the wrong node can interrupt payment setup. Landfall connects the steps with one guided process rather than requiring miners to assemble independent tools.
How one backup creates the necessary credentials
The project derives a BIP84 Bitcoin address using the path m/84’/0’/0’/0/0 from a 24-word seed. The same seed serves as the root for a Lexe Lightning wallet that can create the BOLT12 offer. Landfall asks the miner to paste the exact verification message supplied by OCEAN, signs it with the derived address key and shows the signed text so the recipient can verify it. The signature attests to the requested destination; it does not itself transfer a coin.
Developer documentation describes a browser wizard, a Tauri desktop shell and a Rust command-line interface. Under the hood, shared components handle address derivation, BIP322 signing and Lexe integration. A read-only MCP interface for inspecting state is included. Those documented architectural components do not establish that the application has passed an independent security review or works for every wallet configuration.
Proof of concept comes with a serious security warning
Landfall currently saves its recovery phrase as plaintext in a local file with owner-only permissions, mode 0600. Restricting file permissions is useful but is not equivalent to hardware-backed secret storage, malware protection or a formal audit. The project README warns against depositing a large balance or importing a wallet seed already used for meaningful funds. Its mainnet-only behavior further raises the cost of experimenting with real assets.
Compare the design with our coverage of Lightning wallet infrastructure and recent Lightning Dev Kit security fixes. Both illustrate why user experience should be evaluated alongside recovery guarantees and software vulnerabilities.
Why small miners may care
High on-chain transaction fees can make frequent small payout transactions disproportionately expensive. A workable Lightning route can change the withdrawal experience for smaller hashrate operators, although availability, routing liquidity, pool conditions and channel-exit costs still matter. Landfall does not add new Bitcoin consensus rules or guarantee cheaper payments in every case.
Our ArkPool micro-payout article explores another attempt to serve small miners; the decentralized payout risk report describes challenges that wallet ergonomics alone cannot solve. Landfall’s measurable contribution is reducing the number of independent credentials and manual steps in an existing workflow, not proving a new mining protocol.
Primary documentation: Landfall source code and security warnings and Bitcoin Optech Newsletter #428. Functionality is described from source documentation; a mainnet payout and mobile player playback were not independently exercised for publication.
We volunteer daily to ensure the credibility of the information on this platform is Verifiably True. If you would like to support to help further secure the integrity of our research initiative, please scan the QR code below.


Leave a Reply