pull down to refresh

100 sats \ 3 replies \ @BITC0IN 6 Sep \ parent \ on: Where does the filtering stop? bitcoin
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
write
preview
21 sats \ 2 replies \ @optimism 6 Sep
there's some edge cases with lightning nodes
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.
put me in the release notes! ;D
lol!
reply
100 sats \ 1 reply \ @BITC0IN 6 Sep
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!
reply
21 sats \ 0 replies \ @optimism 6 Sep
go make a PR and claim credit!
I'd literally have to do it under this nym to maintain at least some semblance of nymity - it's throwaway so there won't be real credit. Which is great.
reply