GuthL

So, it is slightly more complicated than a serial number. In some sense, everytime you make a transaction, you burn all the input coins and creates new coins for the same value, each assign to the respective recepient. Tracking them is not straight forward. Most OTC are not very tech savvy and I can imagine one either being criminal but stupid for bringing it to Bitfinex or simply non criminal but did not do their due diligence and KYC the seller (which is very surprising knowing the space)

Litterraly France.

Bear in mind you might not have the same way to report salaries. In France, for instance, when employees report salary, they don't include the tax the company pays for them. AFAIK, in the US, salaries are reported including them. I still have a very hard time making apple to apple comparisons. If anyone has a good methodology, please ping

This Unit is litterally 10000 people, is the largest in the Israeli army and handles the vast majority of computer security things. So still does not say much.

What Zcash did and Solana plans to use is a VDF without succinct verification. Unfortunately, I cannot verify it on a smart contract though, which brings me back to RANDAO + VDF for onchain verifiable randomness.

While you are right for most applications, it would not work for gambling or block selection in the case of proof of stake. Let say I'm flipping a coin (based on the last bit of the block hash) with you. You already locked the funds on the contract, waiting for me to commit to. I can wait until I'm the block proposer to push a block where I'm included. Even if we defined ahead of time how many rounds of hashing, I still have access to that information ahead of time and can decide to participate in the bet. Therefore, it is not secure randomness. (I won't get into commit and wait which could solve it but they are a pain in any case)

Secure randomness requires unpredictability, unstoppability and unbiasable. If you are flipping coin based on bitcoin randomness, the block proposer has an advantage over you. It is not technical secure randomness. That's why Ethereum 2.0 is planning on using a RANDAO + VDF to ensure it. More info on vdfresearch.org

Great work! I love the execution speed. Pretty amazing what we can do in the browser at this point. It sure will bring more zero Knowledge protocols to be deployed in the wild

Why could not you have both ? No one said that you need Securities transactions to be irreversible. STO can bring more liquidity to property assets and simplify dramatically otherwise complex financial operation (title emission, splitting of subsidiaries and so on). I do hate the point that talks about adoption when we are talking of a technology that has less than 5 years of age (Ethereum for that matter). I hear it a lot and I cannot stop myself to think that this is the same kind of reasoning could have been use again Amazon in 1996 (Bookstore are a small business and Internet has no adoption)

Bitcoin and ethereum are such successes! On a smaller scale but growing, 0x is doing an amazing job.

Ip used for technical reasons such as logging access are not concerned by the gdpr per se. The same goes to KYC informations. The gdpr is actually a well written piece of legislation which should worry you only if you do shady stuff. The only edge case that I know are not well addressed concerns the status of encrypted data (would be deleting private keys considered to be deleting them? This question is important on blockchain data storage)

Your personal opinion on cash is irrelevant to the subject. Cash has property you say you don't want. Some people might and do want them. Just have a look at what the relationship between Germans and cash.

Bitcoin has property similar to cash to many extend. It was not technically possible before its invention and as such as it is a real intrinsect value (dont ask me to quantify it)

Because they do not need it for the task at hand. Password security has clear best practices which are also simpler to implement than encryption. The very fact that someone can somehow read your password is a breach of privacy.