What really happen when user moves fund between Main Account and Trading Account in HitBTC?

What really happen when user moves fund between Main Account and Trading Account in HitBTC?

I am building a crypto exchange and I wonder how HitBTC exchange (https://hitbtc.com/) is handling "Main account" and "Trading account", as the image below:

enter image description here

According to them, Main Account is like cold wallet, while Trading Account is like hot wallet. Storing your fund in Main Account (cold wallet) will be safer to your fund.

Now, let's talk about definition of cold wallet and hot wallet. Cold wallet means private key is stored offline, while hot wallet means private key is stored online.

So, am I correct that, when user store his fund in "Trading Account", what really happens is, HitBTC moves private key of that particular user's wallet to an online server? And when the user moves the fund to "Main Account", what really happens is, HitBTC remove the private key from online server and store it in online offline servers?

If yes, then how can HitBTC, when necessary, moves private key from offline server to online server, without making the offline server online?

http://bit.ly/2Ta8yo4

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