Hey ETFbitcoin,
Thank you for taking the time to post.
Release your whitepaper and make sure someone do peer review on your paper. Release it on it's own testnet or release the source code also helps.
I am going to do exactly that. I have the proof of concept stress tested. Will be publishing the white paper within a month and releasing the test network within 2 months and main network within 3 months.
It would be great if you can do a peer review too and point to the issues I have so that I can improve upon thigs. Of course this system also comes with a Turing complete VM and I am planning to run the entire project as a smart contract with tokens issued in a DAO style to anyone who adds value. Will share the business plan and other stuff at a later stage after the white paper is ready.
You mention LN's disadvantage, not why it only works on theory since LN already used on both testnet and mainnet.
Yes, thanks for correcting me. What I meant was that it works only in theory for "unlimited scaling".
Assuming current block size is 1MB (which isn't because we use block weight limit with 4 kWu limit) or AFAIK 1.000.000 bytes in reality, then that means 1 transaction only have size about 1 byte and i can't see how would you fit transaction (input, output and signature). But i've no idea about GoLang.
ETFbitcoin, It has nothing to do with GoLang. Data is data everywhere. My solution algorithm reaches sharding consensus with infinitesimally low failure rate and extremely high fault tolerance.