Lightning network not yet.

Hi Guys,

I listen various comment about the project Lightling network, many optimists, others not so much;
but I did not read any approach to project status.
so I'll post that on this post

0) the projet Lightling network ( LN )not about bitcoin core, or your forks but according to the use cases:

  • Instant Transactions;
  • Exchange Arbitrage;
  • Micropayments;
  • Financial Smart Contracts and Escrow.
  • Cross-Chain Payments.

fonte: https://lightning.network/lightning-network-paper.pdf ( page 56 )

LN1.png

many of these applications are not even included in the specifications.

fonte: https://github.com/lightningnetwork/lightning-rfc

example: Financial Smart Contracts and Escrow.
it is neither clear nor specified which part of the 11 will do this.

1º) the documentation for development it's very confusing:

in some places there is testnet support for LTC,
this information is included in the official project website:

font: http://lightning.community/release/software/lnd/lightning/2017/05/03/litening/

but in the test files there is nothing Litecoin:

https://github.com/lightningnetwork/lnd/blob/master/test_utils.go
or
https://github.com/lightningnetwork/lnd/blob/master/lnd_test.go

or testnet support, then do you expect tests in the mainnet?

font: http://dev.lightning.community/

2º) the project is still in beta version:

LN2.png

font: https://github.com/lightningnetwork/lnd/milestones

I understand the great of many, but the project is still very new.
I follow the project for some time, and in my view due to the number of bugs does not have any reason to leave the alpha version.

3º) the LN is intended to support bitcoin, but in no time deals with security in a professional way:
the labels of developers do not address information Common Vulnerabilities and Exposures (CVE) or Common Weakness Enumeration (CWE):

https://github.com/lightningnetwork/lnd/labels/security

a very superficial way compared to what core bitcoin already does

LN3.png

font: https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures

4º) the directory lightning-onion,

this part of the project does not have versioning
but also does not inform if it is following the RFC specifications of the "TOR protocol"
or even which TOR specification is being used

font: https://github.com/lightningnetwork/lightning-onion

and recommended

https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt

5º) sometimes the design forgets the most basic:
see this improvement:
"Establish license of use #5"
font: https://github.com/lightningnetwork/paper/issues/5

I am aware that this project has several external references, but github is not a world
so it would be interesting if each repository had its own license to use, or
or even some external reference of which license the repository has.
I'll ignore that this can be done in the first few steps when creating a repository.
if it is something so simple, and a good practice because it was not done in the repository:

font: https://github.com/lightningnetwork/paper

CONCLUSION

the LN project has great intentions but still has many structural problems, I see that my criticism can be useful to the project.

thank you for reading this text, if you can share with people idealize the project but never even saw the source code.

Coin Marketplace

STEEM 0.19
TRX 0.15
JST 0.029
BTC 63178.17
ETH 2581.50
USDT 1.00
SBD 2.71