New answers tagged

2

The first line is normal behaviour: UNUSUAL plugin-bcli: Could not connect to 'lightning-rpc': Connection refused Your lightningd cannot start if the underlying bitcoind is not up-to-date: 2020-07-20T02:59:44.730Z UNUSUAL lightningd: Waiting for initial block download (this can take a while!) 2020-07-20T02:59:44.732Z UNUSUAL lightningd: Unable to estimate ...


3

c-lightning doesn't store old versions of the commitment transaction, exactly in order to avoid accidentally cheating. If you compiled with DEVELOPER=1 you can however call lightning-cli dev-sign-last-tx {peer-id} and it'll spit out the fully signed commitment transaction (that's why dev-* commands are dangerous and should not be used if you don't know ...


2

In order for you to see these scripts you'll have to force the channel on-chain, along with the HTLC. Only then will the HTLC be swept using the script, otherwise you'll only see the P2WSH output for the HTLC being added and then removed if the payment succeeds or fails. Under normal operation you wouldn't therefore see the HTLC. When testing c-lightning we ...


Top 50 recent answers are included