Preventing MITM [combined summary]



Individual post summaries: Click here to read the original discussion on the lightning-dev mailing list

Published on: 2015-10-20T23:15:26+00:00


Summary:

The discussions also address concerns about the scalability of the Lightning network. One proposed solution is to create a cost for running or registering a node/channel to discourage spamming and prevent an arms race in nodes-per-person. This would help alleviate potential scaling problems.Another topic of discussion is the malleability issue in anchor transactions. It is important to avoid key reuse and find a solution to this problem before utilizing the blockchain. Schnorr signatures are considered as a possible solution, but there are concerns about their implementation.The size of the map needed for the Lightning network is also discussed. Rusty Russell suggests that this concern can be ignored until there are over 10k nodes. The possibility of pruning distant parts of the map is also considered.Rusty Russell brings up the idea of Lightning channels through IOUs, which raises concerns about fake edges in the routing graph. However, it is suggested that the concern about the size of the map can be addressed once there are a significant number of nodes.To verify the genuineness of the Lightning network, users can perform tests by making small payments to merchants or friends. Forwarding a transaction costs about 2.4e-8 dollars or 0.0091 satoshi, providing a way to measure the authenticity of the network.Overall, the discussions highlight concerns about network security, malleability, scalability, and the genuineness of the Lightning network. Various solutions and ideas are proposed to mitigate these issues, including utilizing the blockchain for tamper-proof records, implementing cost measures to discourage spamming, and finding solutions to the malleability issue.


Updated on: 2023-07-31T18:23:44.278833+00:00