pull down to refresh
If LND now supports blocksonly then that's an awesome improvement that I didn't know worked. I remember needing a mempool for it to work in the past.
no I don't think it does work, which is what I found out the hard way with some stuck channel opens.
Might be worth it for LND to disable that argument actually, now that I think about. it's a foot gun that I used well to clean the toes of my node.
go make a PR and claim credit!
iirc I only had one consistent peer when being blocksonly=1 when trying to sync to the chaintip. once at the chaintip I think i got more peers, but still very few.
Thanks for looking into this, me and the one other user in the world who used this feature appreciate it.
oh also, there's some edge cases with lightning nodes who switch blocksonly=1 on too. terrible cases of channel opens being stuck in some instances (just me lol) that required LND updates to flush out.
also,
put me in the release notes! ;D
I mean that depends. part of the problem is peoples ignorance surrounding this issue.
disclosure seems prudent to me.
fyi: despite that blocksonly code you reference being in place, it does not functionally work when I tested sending bitcoin in the field with my own node. there may be other factors at work though, i did not test this extensively.
another draw back of being blocksonly=1 is that my peers (i'd say most) start to disconnect from me, since they think I'm a bad peer.
I'd rather continue to speak-relay-gossip known monetary only transactions, while not speaking-relaying-gossiping known arbitrary data blobs.
I also can't broadcast a transaction from my node with blocksonly=1
That feature needs to be turned off if you want to send Bitcoin.