Timeout opening a channel when in blocksonly mode on bitcoind

[vincecate]

My Pebble wallet is connected to BTCPayserver. My bitcoind is runnin in "blocksonly" mode. This reduces the bandwidth needed by nearly a factor of 10. But it means we only see on blockchain stuff from others after it is inside a block. So setting up a channel there is a timeout that produces the attached error message in Pebble. The channel is opened ok and works. It is just the error message that is the problem.

Note that blocksonly mode does not slow down normal off-blockchain Lightning Network stuff, so it seems a great thing for reducing the cost of running a node. I believe as Lightning takes over that blocksonly will become the default setting.

[mandelmonkey]

Thanks good to know
im not sure its possible for pebble to know if your btcpay is using blocks only mode, it uses grpc to communicate to btcpays lnd, which is proxied by btcpay, so I think maybe its more of a btcpayserver issue
I could add a patch to detect this error and assume its btcpay in blocksonly and hence return a better message

[vincecate]

On Tue, Apr 16, 2019 at 11:47 AM Christian Moss ***@***.***> wrote: Thanks good to know im not sure its possible for pebble to know if your btcpay is using blocks only mode, it uses grpc to communicate to btcpays lnd, which is proxied by btcpay, so I think maybe its more of a btcpayserver issue I could add a patch to detect this error and assume its btcpay in blocksonly and hence return a better message

I asked Andrew Camilleri <[email protected]> if btcpayserver could fix this message and he said for sure it was a pebble issue. :-) But at least a better message. Maybe "Channel setup has not finished yet. If you are in blocksonly mode then nothing to worry about. Check channels later. " Thanks,

…

-- Vince

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[vincecate]

I have attached a screenshot of an error message I have received several times now. It seems like things are working though. Vince

…

On Tue, Apr 16, 2019, 11:47 AM Christian Moss ***@***.***> wrote: Thanks good to know im not sure its possible for pebble to know if your btcpay is using blocks only mode, it uses grpc to communicate to btcpays lnd, which is proxied by btcpay, so I think maybe its more of a btcpayserver issue I could add a patch to detect this error and assume its btcpay in blocksonly and hence return a better message — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AjxlnkJIS8TWhUlu2BfFuDmrU-JIzk72ks5vhfCFgaJpZM4cyLO-> .