Hiding identity in digital currency era

Hiding identity in digital currency era

I have a question about the security of digital currencies, however still I have find a clear answer for that. No matter what is the currency, e.g bitcoin, monero, ..., at the end of the day, I have to go to somewhere and change the digital money to physical money. Isn't that?

For example, I have 20 XMR. I need to change that to Dollar. So, I have to tell somebody (a bank or someone else) to take this 20 XMR and give me some money. At this point the identity is revealed.

Specifically, I have to first transfer the digital money to the person in the other side and then take the physical money.

Can someone explain that?

https://ift.tt/2CGy7rF

Comments

Post a Comment

Popular posts from this blog

Bitcoin Core errors with database block

Bitcoin Core errors with database block I've had the follow issue: on one machine I've launced Bitcoin Core v0.16.0 and Litecoin Core v0.16.0. Each application work in separate datadir also each application have setted callback call for event walletnotify . For now I use both application with testnets. Recently, there have been frequent cases when these applications stop sending transactions, when restarting, an error occurs: "Corrupted block database detected. Do you whant to rebuild the block database now ?". It happens on both apps Bitcoin Core and Litecoin Core, after rebuild applications continue to work, but after a while it happens again Please help me, what I doing wrong? Thank you for any advice https://ift.tt/2z6j9rL
Read more

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more