Comment by Bobanaut on 12/01/2018 at 17:10 UTC

13 upvotes, 2 direct replies (showing 2)

View submission: ⚡ Lightning Network Megathread ⚡

View parent comment

a full node allows me easy and fast access to the whole blockchain and if i ever need it to the mempool. sure i could use a custom client to just get the data, but it doesn't hurt me... and it's not using a noticeable amount of my system.

but a LN node is a completely different beast. while a BTC node only needs to validate blocks (sigcheck) every 10 minutes a LN node is a completely different monster.

Once the network scales big enough there will be a huge number of transactions going everywhere, 3 hops through onion routing, then generation of at least 4 ecdsa keypairs per update...

i just don't see it working with my current CPU being able to only generate 3000 ecdsa keypairs per second at full utilization ...

this costs energy, lots of energy... a miner gets the reward and fees... a LN node doesn't get anything

Also OSS doesn't ask you for more than your free time and much less for the power this time costs.

Replies

Comment by GibbsSamplePlatter at 12/01/2018 at 18:32 UTC

4 upvotes, 2 direct replies

LN pegging your CPU as a routing node is a champagne problem(you're apparently making plenty of fees), quickly solved by rate limiting or raising your fees.

Comment by jayAreEee at 12/01/2018 at 18:11 UTC

1 upvotes, 1 direct replies

That's actually impressive that you can create keypairs at 3000/sec. I ran some tests on ECDSA signing and I'm maxing out at 80-100/sec on a skylake 6700k CPU. That's in javascript via chrome/firefox, but still.