lightning/ subdirectory in your home directory: see man -l doc/lightningd.8 (or ) for more runtime options. Lightningd -network=bitcoin -log-level=debug Compiling the source code yourself as described in the installation documentation.įor the impatient here's the gist of it for Ubuntu:.Using one of the provided docker images on the Docker Hub.Installation of a pre-compiled binary from the release page on GitHub.There are 4 supported installation options: Pruning ( prune=n option in nf) is partially supported, see here for more details. Getting StartedĬore Lightning only works on Linux and macOS, and requires a locally (or remotely) running bitcoind (version 0.16 or above) that is fully caught up with the network you're running on, and relays transactions (ie with blocksonly=0). We recommend getting started by experimenting on testnet (or regtest), but the implementation is considered stable and can be safely used on mainnet.Īny help testing the implementation, reporting bugs, or helping with outstanding issues is very welcome.ĭon't hesitate to reach out to us on IRC at #lightning-dev libera.chat, #c-lightning libera.chat, or on the implementation-specific mailing list or on the Lightning Network-wide mailing list or on Discord core-lightning, or on Telegram Core Lightning. This implementation has been in production use on the Bitcoin mainnet since early 2018, with the launch of the Blockstream Store. Care And Feeding Of Your New Lightning Node.StopĬhangelog-Fixed: Fix incompatibility with LND which prevented us opening private channelsĬore Lightning (CLN): A specification compliant Lightning Network implementation in CĬore Lightning (previously c-lightning) is a lightweight, highly customizable and standard compliant implementation of the Lightning Network protocol. OPT_SCID_ALIAS if it intuited it, even if it wasn't offered. Realized that v23.05 violated the spec and send accept_channel with In addition, while looking at the previous backwards-compat code, I Did both peers announce support for scid aliases? So, if we don't negotiate anchors (we don't!), we don't set thisĬhannel_type bit even if we want it, and *intuit* it, based on:Ĥ. That has nasty privacy implications (you can probe the real channel id). We could simply drop this channel_type until we merge anchors, *but*
LND has a limited set of features they allow, and this isn't allowed without Prior to 23.05 we didn't allow it to be set at all, andĢ. When it was introduced, instead relying on the presence of the featureīit with the peer. Unfortunately, we didn't set this bit in the channel_type in v12.0 It only makes sense (and is only permitted!) on unannounced channels. Routing via the real short channel id, and MUST use the alias. option_scid_alias inside a channel_type allows for more privateĬhannels: in particular, it tells the peer that it MUST NOT allow Openingd: work harder to intuit OPT_SCID_ALIAS.
0 kommentar(er)
