More good info. Would you please answer these questions?
Instead of sending NAVcoin directly to the receiver, the wallet encrypts the receiver address and sends the transaction to one of the addresses provided by the randomly selected processing server.
What information about the originator does the processing server know about (originator IP, wallet address, amount available to spend, etc.). When this server receives this transaction, it creates a transaction of arbitrary size on the Subchain which it sends to a randomly selected outgoing server.
This Subchain transaction has the receiver address and the amount of NAVcoins to send, encrypted and attached to it. When the outgoing server receives the Subchain transaction, it decrypts the data, randomizes the transaction amounts and sends NAVcoins to their intended recipient from a preloaded pool of NAVcoins waiting on the outgoing server.
What is the potential that the decrypted data can be viewed by the server operator and/or logged by the server operator?.
After the outgoing server has sent out the randomized NAVcoins to the intended recipient, the incoming server will join together any NAVcoins that have been processed and on the next transaction cycle send it to the outgoing server to replenish the pre-loaded pool of NAVcoins for future transactions.
What is the size of the preloaded pool of NAVcoins?
Show Posts
