pull down to refresh
221 sats \ 7 replies \ @justin_shocknet 8 Mar \ parent \ on: LND w. Neutrino Backend // Privacy & Security lightning
To add to this, neutrino is specifically a privacy focused solution for outsourcing block validation... it does this by getting compressed versions of entire blocks rather than asking a server for info about specific outputs, which could be used to deanonymize or otherwise attack you
The security profile is that you're not validating blocks yourself as you would with a full Bitcoin core node
For an edge node with a channel or three for use by you / small business / eCommerce its perfectly fine.
It's not recommended if you plan on running a routing node with lots of random peers.
Thanks a lot guys! Very appreciated! Do I understand that correctly, that in Neutrino mode, the lightning node connects to multiple neutrino nodes (unless you point it to a specific one) and compares their results (i.e. does not trust the answer of a single node)?
reply
Yes, you could add multiple neutrino peers for your connection. usually is taking first the one with the best ping. So I suggest to test their ping before you make your list, to be under 150ms.
reply
Okay, so its not automatic. Will add a couple then! Thanks a lot!
Another quick question a bit off topic, I was always under the impression that two addresses of an m-of-n native segwit multisig cannot be connected to each other when looking at the blockchain. That made sense to me since every address has a different derivation path. Now, someone claimed that after transacting with one address, your public keys are revealed and another address of the same wallet can be connected by chain analysis crap.
Is this true. Sounds like bs to me but maybe there is something in the multisig script I do not understand.
reply
It was a post about this on SN but can't find it right now. Search on SN is kind of crap showing results only for zaprank instead of recent/older.
Maybe @bitcoin_devs could give a better answer on this.
Check on their history too https://stacker.news/bitcoin_devs/posts
reply
Thanks, will have a look!
reply
there's not two addresses in a multisig, there is one address, signed for with multiple keys
when that multisig output is spent those keys are revealed, but thats not the same as your extended pubkey... the derivation path is how basically you have infinite uncorrelated public keys from one true signing key
reply
I really meant two distinct addresses in a HD wallet (each of which needs multiple signatures of course based on the required quorum)
reply