--- Log opened Fri Apr 18 00:00:18 2025
04:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
04:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
04:17 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 245 seconds]
04:19 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
04:25 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 248 seconds]
04:33 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
04:40 -!- jonatack [~jonatack@user/jonatack] has quit [Remote host closed the connection]
04:48 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
05:37 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 272 seconds]
06:11 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
08:41 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 276 seconds]
08:42 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
08:57 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 264 seconds]
09:02 -!- jon_atack [~jonatack@user/jonatack] has joined #c-lightning
09:03 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 265 seconds]
10:01 -!- jon_atack [~jonatack@user/jonatack] has quit [Quit: WeeChat 4.6.1]
10:19 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
12:11 -!- jespada [~jespada@r179-25-58-5.dialup.adsl.anteldata.net.uy] has joined #c-lightning
12:12 -!- jespada [~jespada@r179-25-58-5.dialup.adsl.anteldata.net.uy] has quit [Client Quit]
12:16 -!- jespada [~jespada@r179-25-58-5.dialup.adsl.anteldata.net.uy] has joined #c-lightning
12:17 -!- jespada [~jespada@r179-25-58-5.dialup.adsl.anteldata.net.uy] has quit [Client Quit]
12:25 -!- zeshbtc [~zeshbtc@116.71.176.244] has joined #c-lightning
12:26 < zeshbtc> Core Lightning (previously c-lightning) is a lightweight, highly customizable and standard compliant implementation of the Lightning Network protocol.
12:26 < zeshbtc> Getting Started
12:26 < zeshbtc> Installation
12:26 < zeshbtc> Starting lightningd
12:26 < zeshbtc> Using the JSON-RPC Interface
12:26 < zeshbtc> Care And Feeding Of Your New Lightning Node
12:26 < zeshbtc> Opening A Channel
12:26 < zeshbtc> Sending and Receiving Payments
12:26 < zeshbtc> Configuration File
12:26 < zeshbtc> Further Information
12:26 < zeshbtc> FAQ
12:26 < zeshbtc> Pruning
12:26 < zeshbtc> HD wallet encryption
12:26 < zeshbtc> Developers
12:26 < zeshbtc> Documentation
12:26 < zeshbtc> Project Status
12:26 < zeshbtc> Continuous Integration Pull Requests Welcome Documentation Status BoL2 Telegram Discord Irc
12:26 < zeshbtc> This implementation has been in production use on the Bitcoin mainnet since early 2018, with the launch of the Blockstream Store. We recommend getting started by experimenting on testnet (testnet4 or regtest), but the implementation is considered stable and can be safely used on mainnet.
12:27 < zeshbtc> Using The JSON-RPC Interface
12:27 < zeshbtc> Core Lightning exposes a JSON-RPC 2.0 interface over a Unix Domain socket; the lightning-cli tool can be used to access it, or there is a python client library.
12:27 < zeshbtc> You can use lightning-cli help to print a table of RPC methods; lightning-cli help <command> will offer specific information on that command.
12:27 < zeshbtc> Useful commands:
12:27 < zeshbtc> newaddr: get a bitcoin address to deposit funds into your lightning node.
12:27 < zeshbtc> listfunds: see where your funds are.
12:27 < zeshbtc> connect: connect to another lightning node.
12:27 < zeshbtc> fundchannel: create a channel to another connected node.
12:27 < zeshbtc> invoice: create an invoice to get paid by another node.
12:27 < zeshbtc> pay: pay someone else's invoice.
12:27 < zeshbtc> plugin: commands to control extensions.
12:27 < zeshbtc> Care And Feeding Of Your New Lightning Node
12:27 < zeshbtc> Once you've started for the first time, there's a script called contrib/bootstrap-node.sh which will connect you to other nodes on the lightning network.
12:27 < zeshbtc> There are also numerous plugins available for Core Lightning which add capabilities: in particular there's a collection at: https://github.com/lightningd/plugins
12:27 < zeshbtc> Including helpme which guides you through setting up your first channels and customizing your node.
12:27 < zeshbtc> For a less reckless experience, you can encrypt the HD wallet seed: see HD wallet encryption.
12:27 < zeshbtc> You can also chat to other users at Discord core-lightning; we are always happy to help you get started!
12:27 < zeshbtc> Opening A Channel
12:27 < zeshbtc> Configuration File
12:27 < zeshbtc> lightningd can be configured either by passing options via the command line, or via a configuration file. Command line options will always override the values in the configuration file.
12:27 < zeshbtc> To use a configuration file, create a file named config within your top-level lightning directory or network subdirectory (eg. ~/.lightning/config or ~/.lightning/bitcoin/config). See man -l doc/lightningd-config.5.
12:27 < zeshbtc> A sample configuration file is available at contrib/config-example.
12:27 < zeshbtc> Further information
12:27 < zeshbtc> Pruning
12:27 < zeshbtc> Core Lightning requires JSON-RPC access to a fully synchronized bitcoind in order to synchronize with the Bitcoin network. Access to ZeroMQ is not required and bitcoind does not need to be run with txindex like other implementations. The lightning daemon will poll bitcoind for new blocks that it hasn't processed yet, thus synchronizing itself with
12:27 < zeshbtc> bitcoind. If bitcoind prunes a block that Core Lightning has not processed yet, e.g., Core Lightning was not running for a prolonged period, then bitcoind will not be able to serve the missing blocks, hence Core Lightning will not be able to synchronize anymore and will be stuck. In order to avoid this situation you should be monitoring the gap
12:27 < zeshbtc> between Core Lightning's blockheight using lightning-cli getinfo and bitcoind's blockheight using bitcoin-cli getblockchaininfo. If the two blockheights drift apart it might be necessary to intervene.
12:27 < zeshbtc> HD wallet encryption
12:27 < zeshbtc> You can encrypt the hsm_secret content (which is used to derive the HD wallet's master key) by passing the --encrypted-hsm startup argument, or by using the hsmtool (which you can find in the tool/ directory at the root of this repo) with the encrypt method. You can unencrypt an encrypted hsm_secret using the hsmtool with the decrypt method.
12:27 < zeshbtc> If you encrypt your hsm_secret, you will have to pass the --encrypted-hsm startup option to lightningd. Once your hsm_secret is encrypted, you will not be able to access your funds without your password, so please beware with your password management. Also, beware of not feeling too safe with an encrypted hsm_secret: unlike for bitcoind where the
12:27 < zeshbtc> wallet encryption can restrict the usage of some RPC command, lightningd always needs to access keys from the wallet which is thus not locked (yet), even with an encrypted BIP32 master seed.
12:27 < zeshbtc> Developers
12:27 < zeshbtc> Developers wishing to contribute should start with the developer guide here.
12:30 -!- zeshbtc [~zeshbtc@116.71.176.244] has quit [Quit: Client closed]
12:40 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
13:01 -!- colinsane [~colinunin@97-113-94-68.tukw.qwest.net] has quit [Quit: bye]
17:21 -!- zeshbtc [~zeshbtc@2407:d000:405:db:8de6:56ed:d389:6139] has joined #c-lightning
17:34 -!- zeshbtc [~zeshbtc@2407:d000:405:db:8de6:56ed:d389:6139] has quit [Quit: Client closed]
18:27 -!- opsec_x122 [~opsec_x12@44.25.143.46] has quit [Ping timeout: 248 seconds]
19:18 -!- colinsane [~colinunin@97-113-94-68.tukw.qwest.net] has joined #c-lightning
21:37 -!- opsec_x12 [~opsec_x12@50.54.217.67] has joined #c-lightning
--- Log closed Sat Apr 19 00:00:28 2025