 Show Posts
|
|
Pages: [1]
|
For me that does not function of all, and is running out of patience. Whereas the support tells me that the withdrawal is moving!!!!!!!
What seems to be the problem? After checking the logs, all withdrawals have been processed. |
|
|
|
I appreciate the explanation, would have been nice if it was a day sooner. I gave you exchange a chance because of the reasonable asking price compared to others. If you can overcome your communication issues in the future, i would probably use your site again.
Same here. I also appreciate the detailed explanation and i apologize for maybe exaggerating a little bit with criticism. Either way the exchanges are there for us, users, and they profit from us. No need to apologize, I cant agree more. We might have problems with the system itself in the future, but we strive to handle it with highest priority. But the most important is the customer support, as every minute not knowing what is going on, do no good, to us or the client. |
|
|
|
deposit doesn't work!
After your post, i have rechecked the system. And i found out, that with some users, LISK deposit address could not be generated. This has now been fixed. Thank you. |
|
|
|
deposit doesn't work!
Please PM me with more details. |
|
|
|
It is now working, slow but working. In regards to being scammed at the time it was a very easy conclusion to make expecially when customer support stopped responding for 12 hrs. Then you add past comments on this forum and you can see where I was coming from.
X2! How else could you explain the very clicking inside the >withdraw address< and >amount< throws an error at you? Not to mention the price was ridiculously low comparing to all other markets, i bet it scare forced few users to sell their LISK for insane low price (i can blind guess who's bids was there) just for sake of saving their BTC. If it wasn't deliberate, it was amateurish. Put yourself together Bloombit, there's a competition out there. I already explained why the errors where coming. GET /api/accounts?address=address was returning “{"success":false,"error":"Account not found”}” (while the node was out of sync), and the fronted did not handle the request and return an detailed error message, but printed “Something went wrong. Please contact support” as default error message instead. Non of this ever happened on testnet. There is no internal trading that i can guarantee. It wasn’t deliberate and neither “amateurish”, as we were not getting any response from the lisk support (as they were fixing their problems i guess…), and we were walking in the dark for quite some time. We were working for 20h/day for the last 2 days now, so i guess that caused some minor mistakes, which lead to user problems, and misunderstanding - which is again our customer supports fault. Thank you again |
|
|
|
It is now working, slow but working. In regards to being scammed at the time it was a very easy conclusion to make expecially when customer support stopped responding for 12 hrs. Then you add past comments on this forum and you can see where I was coming from.
You have to know, that we are a small team, and we have been focused on the system for the past 2 days. Customer support did not have any answer from us, as we were still investigating what is going wrong - the tests we were running on testnet, newer showed any similar problems. No offence taken for those acquisitions, as we understand how is it to be in the dark. That was the reason i registered and started posting updates. Certain security measures, can slow the process for withdraws, but can not take longer than 20min - if the daemons are ok. Lisk deposit checks are being made every minute, for other coins, they are instantly shown in the deposit section of the page. |
|
|
|
thnx guys!
btwn. other ones who are always negative, please be patient and stop acting childish with those "we're scammed" posts.
We all know Lisk is having troubles with their own network so it's pretty clear that bloombit is having those same problem because of Lisk network.
It will all be fine, just be patient.
Thank you metropolit and others for your understanding. UPDATE: backup node is sync-ed. We are now developing a script for block height checking, so in case of any problems with the primary node, the system can route to the backup node. We have found that, in case node is not synced it can lead to many other problems, such as not broadcasting transactions to network. That happened to the users that managed to place a withdraw request after 01:00am server time, and they could see the transaction id (txid), which did not exists in the mainnet. Those transactions have been now processed as requested, and are already confirmed. |
|
|
|
|
UPDATE: Withdrawals and Deposits are working.
|
|
|
|
|
UPDATE: Node is now fully synced. We are in a process of seting up a backup node.
|
|
|
|
|
First of all let me apologise for the trouble we have may caused you. We are experiencing problems with the LISK local node, which is failing to completely sync. After rebuilding the node, the blocks sync to about 80%, then is slows down.
Testnet was running for more than a month, and we have not experienced any major problems during the tests.
The problem you have been experiencing is "Account not found" message, when trying to submit a withdrawal request. If the node is not fully synced, it returns that response when validating the address. Even the transactions are not broadcasted.
This is Bloombit’s hot wallet address:https://explorer.lisk.io/address/6548789768638451324L
60% of the ICO bought funds were moved to that address, the rest is still on a different address till the problem is solved, so it can be sent to cold (+ the extra from the hot).
Some of the withdrawal request went through, then the node stopped syncing again.
Other coins, are working ok.
I will keep you updated.
|
|
|
|
|
