pull down to refresh
17 sats \ 0 replies \ @BTCLNAT OP 10 Aug \ parent \ on: Has anyone tested Phoenixd as a self-custodial backend for LNbits? AskSN
I really appreciate your suggestion; it will be another option we will consider. We will read all the documentation and test the solution. I reiterate my gratitude.
Thank you for your words. Truly understanding these basic aspects of the fiduciary system could help people turn to Bitcoin, although some realize they’re being robbed and still cling to fiat. Layer 0—that is, people—can be strange at times.
🇬🇧 English
I’m sharing my personal repository “Fundamentos Técnicos de Bitcoin”, where I’m publishing my study notes and articles from the Librería de Satoshi course on Bitcoin’s technical foundations.
It’s a work-in-progress aimed at learners who want to understand Bitcoin from the ground up—covering its history, cryptographic principles, and technical design.
📂 Repository: Fundamentos Técnicos de Bitcoin
You can collaborate directly through pull requests or open issues with your suggestions, corrections, or additional resources.
Feedback is always welcome—let’s make this a valuable resource for the community! ⚡
🇪🇸 Español
Comparto mi repositorio personal “Fundamentos Técnicos de Bitcoin”, donde estoy publicando mis apuntes y artículos de estudio del curso de la Librería de Satoshi sobre las bases técnicas de Bitcoin.
Es un trabajo en desarrollo, pensado para quienes quieran comprender Bitcoin desde sus fundamentos: historia, principios criptográficos y diseño técnico.
📂 Repositorio: Fundamentos Técnicos de Bitcoin
Pueden colaborar directamente mediante pull requests o crear issues con sugerencias, correcciones o recursos adicionales.
¡Todo aporte es bienvenido para que sea un recurso útil para la comunidad! ⚡
Hello. Actually, this solution exists because the tools are already built, so anyone with a bit of curiosity and need can combine them—especially now that LNbits allows for a more seamless integration with Phoenixd. In Cuba, it's a solution for those who want self-custody on ultra-slow connections and with limited resources, since with just 21.5k SAT, you can open a 2M SAT channel. But regarding this particular post, I don't know anything. I hope I can meet the author of the post, who is a doctor like me, to exchange experiences and see what they've achieved. That's all I can say.
🇬🇧 English
Thanks to everyone who commented and contributed valuable insights in this thread! Your feedback and encouragement helped us complete the first version of the guide for using LNbits with Phoenixd as a self-custodial Lightning solution.
We’ve just published a detailed step-by-step guide for implementing this setup on Linux x64, which could be especially useful for merchants or users in regions with limited connectivity or infrastructure.
🔗 Check it out here:
👉 https://github.com/Delgado74/LNbits-and-Phoenixd-on-your-Linux-x64-machine
We welcome any feedback or contributions to improve or extend this solution to other platforms!
🇪🇸 Español
¡Gracias a todos los que comentaron y compartieron ideas valiosas en esta publicación! Sus sugerencias y apoyo nos ayudaron a completar la primera versión de la guía para usar LNbits con Phoenixd como solución Lightning autocustodia.
Ya está disponible una guía detallada paso a paso para implementar esta solución en Linux x64, especialmente útil para comerciantes o usuarios en regiones con conectividad limitada o pocos recursos técnicos.
🔗 Puedes verla aquí:
👉 https://github.com/Delgado74/LNbits-and-Phoenixd-on-your-Linux-x64-machine
¡Cualquier sugerencia o contribución para mejorarla o adaptarla a otras plataformas será muy bienvenida!
Thank you very much, my friend @DarthCoin, always with your great recommendations. We all have to be very careful when using public nodes for routing. It’s always great to have your help.
Thank you for the suggestion. However, one of the key challenges we face is synchronization with Neutrinos. If Zeus alone could resolve this—given its integrated POS system—it would largely address the issue.
We did evaluate the LND + Neutrinos option, but latency constraints in our environment make it impractical. Currently, we’re operating LNbits + LND in custodial mode via the community node, though our priority now is achieving greater sovereignty: your own node, your own LNbits instance with tailored extensions (including LNDHub), and even self-hosted BTCPay Server if desired. The main obstacle, however, remains our extremely slow internet connection.
Thanks for your encouraging words!
In the Phoenixd documentation, the autoliquidity section explains the mechanism clearly: the minimum channel size is 2M sats, and the liquidity service fee charged by ACINQ is 1% — that’s 21,000 sats just for the service.
On top of that, the on-chain miner fee must also be paid, which varies depending on network conditions.
Now that you mention it, I’ll start putting together a GitHub repo documenting this setup. It’ll be public so anyone interested in using or improving this self-custodial LNbits + Phoenixd combo can access it freely.
Thanks again — I truly appreciate the support and feedback!
🇪🇸 Español
¡Gracias por tus palabras de aliento!
En la documentación de Phoenixd, el apartado de autoliquidez explica claramente el mecanismo: el tamaño mínimo del canal es de 2 millones de sats, y la tarifa por el servicio de liquidez que ofrece ACINQ es del 1%, es decir, 21,000 sats solamente por el servicio.
Aparte de eso, también se deben pagar los fees de minería on-chain, que varían según las condiciones de la red.
Ahora que lo mencionas, voy a empezar a trabajar en un repositorio en GitHub donde documente esta configuración. Será público para que cualquiera que quiera usar esta combinación de LNbits + Phoenixd en modo autocustodia pueda hacerlo o incluso colaborar.
¡Gracias de nuevo! Aprecio mucho el apoyo y el feedback.
Thank you for your feedback!
In our case, LNbits with Phoenixd as the backend is currently working very well.
As I explained in the original post, the goal is to offer an environment that enables self-custody through LNbits — mainly because of its very useful extensions — in a context where connectivity is extremely poor.
Using LND with Neutrino is an option we’ve explored, but syncing is very difficult in our conditions. We’ve already tried with both Zeus and Blixt, and the experience was far from ideal.
A cloud-based solution could work, but it requires more technical knowledge — and we also have to keep in mind that the node would be “on someone else’s computer.”
We already run a custodial LNbits instance using the CubaBitcoin community node, but we’d love to see merchants gain self-custody, at least those who want it and have the means to manage it.
Thanks again for your suggestion and support! ⚡
🇪🇸 Versión en español
¡Gracias por tu comentario!
En nuestro caso, LNbits con Phoenixd como backend está funcionando muy bien por el momento.
Como expliqué en la publicación original, el objetivo es ofrecer un entorno que permita la autocustodia, aprovechando LNbits por sus extensiones tan útiles, y en un contexto donde la conectividad es muy mala.
Usar LND con Neutrino es una opción que ya hemos explorado, pero la sincronización es muy difícil en nuestras condiciones. Ya lo intentamos con Zeus y Blixt, y la experiencia no fue buena.
Una solución en la nube podría funcionar, pero requiere más conocimientos técnicos, y no debemos olvidar que el nodo estaría “en la computadora de otro.”
Actualmente tenemos un servicio de LNbits custodiado usando el nodo de la comunidad CubaBitcoin, pero nos gustaría que los comerciantes pudieran acceder a la autocustodia, al menos quienes lo deseen y puedan manejarla.
¡Gracias de nuevo por tu sugerencia y apoyo! ⚡
— BTCLNAT
Thanks to your input, I now understand that:
- The minimum channel size for Phoenixd is 2,000,000 sats.
- The service fee to open such a channel is 1%, which means 20,000 sats, plus the miner fee.
- This fee can be paid gradually through smaller payments or all at once.
- Once the fee credit is fulfilled, Phoenixd opens the 2M sats channel.
- After that, small payments can be made and the existing fee credit can be used to cover the associated service and routing fees.
This is incredibly useful information for my use case: helping Cuban merchants run LNbits with Phoenixd as a self-custodial backend.
Appreciate the support and knowledge sharing! ⚡
🇪🇸 Versión en español (traducción)
Gracias a sus aportes, ahora entiendo que:
- El tamaño mínimo de canal en Phoenixd es de 2,000,000 sats.
- La tarifa de servicio para abrir ese canal es del 1%, es decir, 20,000 sats, más los fees de minería.
- Esta tarifa puede pagarse de forma progresiva con pagos pequeños o en un solo envío.
- Una vez cubierto ese crédito de fee, Phoenixd abre el canal de 2M sats.
- A partir de ahí, los pagos pequeños pueden realizarse utilizando el crédito de fees existente para cubrir los costos del servicio y enrutamiento.
Esta información es sumamente útil para mi objetivo: ayudar a comerciantes cubanos a utilizar LNbits con Phoenixd como backend autocustodiado.
¡Gracias por el apoyo y por compartir su conocimiento! ⚡
Thank you for your kind words—it means a lot to us. We want to do everything possible to give people the opportunity to achieve freedom through Bitcoin. This platform, and especially Agora Territory, is a great showcase for our work in the community. Sharing these posts is a powerful way to help. We hope that in the future, you can come here to spend your bitcoin at all kinds of businesses in a circular economy.