4 ms·

I don't understand the "key image" cryptography, but I can't fathom how any cryptography, no matter how smart it is, could prevent the user from: 1) Creating a

I don't understand the "key image" cryptography, but I can't fathom how any cryptography, no matter how smart it is, could prevent the user from: 1) Creating a backup of their wallet on disk. 2) Sending their coins somewhere, but not broadcasting the transaction to the network, instead storing it in a file. 3) Restoring from the backup 4) Sending the coins to a different address = double spending them. 5) Broadcasting the transactions in a very close timespan to conduct the double-spend. The network needs to prevent this by storing, in an non-forge-able fashion such as PoW, which transaction happened first. How does your system guarantee that?

comex 6y ago
The client trusts a list of centralized validator servers, albeit protected by SGX, to resolve conflicts. At least according to: https://github.com/mobilecoinfoundation/mobilecoin/tree/master/consensus/service#mobilecoin-consensus-protocol https://github.com/mobilecoinfoundation/mobilecoin/tree/mast...
- crazypython 6y ago
  > The MobileCoin Consensus Protocol solves the Byzantine Agreement Problem by requiring each user to specify a set of peers that they trust, called a quorum. Quorums are based on the real-life trust relationships between individuals, businesses, and other organizations that compose the MobileCoin Network. How does this solve network splits or honest disagreements?