You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Overall I like this design, but it could be better if Padded Uniform Random Blobs were used instead of PGP-like messages for additional metadata protection. Additionally, this tool could be built using the Open Quantum Safe libs, or the OpenSSL Post-Quantum Fork. Until NIST decides, none of the post quantum algos are finalized, but they should be soon. So there's no reason not to get ready for it right now.
Also it might be useful to have a truly open public network for any use if the intent is to grow it, banning non-commercial use may affect even free lancers from being able to safely communicate over it.
The text was updated successfully, but these errors were encountered:
Ok, good point. I didnt dig into post-Q yet, but will certainly do. Leaving this open for reminder.
Would be good to have more drops node anyways.
The non-commercial is only for the "mainnet". You are not allowed to use drops CA
commercially, but you may create your own CA and keys and run your own private network
with it, commercially or not.
This is to make it impossible for tech giants to hop on a potentially already existing good running p2p network, making revenue. But they can start and maintain their own.
The idea is to have many of these nets anyway.
Overall I like this design, but it could be better if Padded Uniform Random Blobs were used instead of PGP-like messages for additional metadata protection. Additionally, this tool could be built using the Open Quantum Safe libs, or the OpenSSL Post-Quantum Fork. Until NIST decides, none of the post quantum algos are finalized, but they should be soon. So there's no reason not to get ready for it right now.
Also it might be useful to have a truly open public network for any use if the intent is to grow it, banning non-commercial use may affect even free lancers from being able to safely communicate over it.
The text was updated successfully, but these errors were encountered: