If a bitcoin wallet service provider terminates a users account, what happens to the funds?

If a bitcoin wallet service provider terminates a users account, what happens to the funds?

A friend of mine has/had a bitcoin wallet service provided by an online marketplace. Sounds like he had some kind of disagreement with the site administrators and they terminated his account. At that time, he still had some BTC in the wallet. Not a lot (about $50.00 USD or so), but still.

Is there any way to recover the funds, or are we all at the mercy of our wallet service providers in that respect?

Seeing as all transactions are recorded in the ledger, I figured perhaps there's some way to claim/prove/declare ownership. It seems pretty thin, but surely there's some kind of safeguard in place, otherwise wallet service providers could exploit that trust and just terminate all their customers accounts and take all their funds with impunity at any moment. Right?

https://ift.tt/2EHpzSb

Comments

Post a Comment

Popular posts from this blog

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

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more