[dead]
> the client is constrained to send you true information Yeah ok bud. You wouldn’t last a week.
> Alice sends out It relies on trusting that Alice’s request is valid. If Alice sends another proof, she will have a different balance. Alice decides what to send. The server blindly accepts it. You actually don’t want…
Only because zcash trusts the sending node - whoever is hosting that ledger. If they had no clue who it was, like the typical http web, they could not allow a sender to be a prover, since they would not be able to…
It has a use case in peer-to-peer or anywhere that you want the server to trust the connections. Sometimes you want clients to be authoritative (although rare).
Not one mention that ZKP depends on servers trusting clients. The single reason ZKP is not viable for most security is that it relies on you trusting the client to send you true information about data. With conventional…
[dead]
> the client is constrained to send you true information Yeah ok bud. You wouldn’t last a week.
> Alice sends out It relies on trusting that Alice’s request is valid. If Alice sends another proof, she will have a different balance. Alice decides what to send. The server blindly accepts it. You actually don’t want…
Only because zcash trusts the sending node - whoever is hosting that ledger. If they had no clue who it was, like the typical http web, they could not allow a sender to be a prover, since they would not be able to…
It has a use case in peer-to-peer or anywhere that you want the server to trust the connections. Sometimes you want clients to be authoritative (although rare).
Not one mention that ZKP depends on servers trusting clients. The single reason ZKP is not viable for most security is that it relies on you trusting the client to send you true information about data. With conventional…