What did happen yesterday?
reply
reply
Oh wow. Wtf.
reply
Sounds worse than it is. No issues with taproot.
reply
Seems to be uncertainty over who is effected.. also, every ln node user of a specific implementation being forced to update at once is not a good thing. Its not a terrible end all event, but its something man.
reply
Agreed. Definitely not good, I do not mean to underplay the situation.
reply
So now we know you are not running a LN node :)
reply
Or no LND ;)
reply
Lmao darthcoin. Not everyone obsesses over their node and sends payments every 10 minutes. It can just sit there.
reply
I learned that Alby wont let you log into SN if your associated lndhub instance isn't running, and you cant get lndhub to restart without lnd synced to chain. So after I started trying to get things fixed, lnauth was unavailable and I couldn't post to SN my progress without going to a browser that was already logged in. This seems like an unnecessary dependency in @alby since it already has sufficient information to sign the lnauth challenge.
reply
A node operator should always keep his eyes open over his own node. Otherwise is for nothing.
reply