[WeExchange]WARNING!The Fall of Ukyo II: Ukyo Digs a Hole?!WARNING![WeExchange]

[azaniet]

I just don't understand how it's possible that Ukyo is 'fixing' weExchange's withdrawal system, while there is up to today still no withdrawal that will not receive error : ' could not connect to 2nd stage server' (I just made another small one today). All new withdrawals will just add to the list of manual withdrawals.

In my opinion, the most likely explanation for this fiasco is that Ukyo's bitcoin reserves are indeed running low, and that this problem is being 'resolved' by postponing the withdrawals.

[1715487583]

1715487583

[1715487583]

1715487583

[1715487583]

1715487583

[1715487583]

1715487583

[SebastianJu]

Im back to where i was before... only at the end of queue. ukyo canceled my withdraw because of my stupid request he should do it in case "he cant withdraw". Because it would have been better to have shares than bitcoins i cant use. I noticed that cancellation way too late because no email was sent about it and now the time was too short to buy the things at bitfunder i wanted. Back into queue and wait again.

ukyo... whats the date of withdraws you work on and how many withdraw requests are still open now?

[Sanqianli]

 fuck,Take my bitcoin  back to me.right now!

[Ukyo]

Of course no new withdraws are working.
I have stated over and over that bitcoind is in a constant state of non-use by the system because it either in startup/wallet loading mode, or locked up due to the latest transfer request.

Let me repeat again.
During startup, bitcoind does not respond to RPC calls.
Once it is up, I make a transfer. The moment I make the transfer, no matter what hardware is provided, it goes to 100% resources and fails to respond to any RPC requests, even after the transaction eventually makes it to the network.

-Ukyo

[SebastianJu]

Of course no new withdraws are working.
I have stated over and over that bitcoind is in a constant state of non-use by the system because it either in startup/wallet loading mode, or locked up due to the latest transfer request.

Let me repeat again.
During startup, bitcoind does not respond to RPC calls.
Once it is up, I make a transfer. The moment I make the transfer, no matter what hardware is provided, it goes to 100% resources and fails to respond to any RPC requests, even after the transaction eventually makes it to the network.

-Ukyo

But you doesnt explain with it that manual withdraws stopped working right?

[bobboooiie]

any hope/eta on fixing automatic withdrawals? I would rather you to focus more time on that then manualy doing this as it will take you till 2015 to process everything by hand

[SebastianJu]

any hope/eta on fixing automatic withdrawals? I would rather you to focus more time on that then manualy doing this as it will take you till 2015 to process everything by hand

I guess it wont be so easy since ukyo is working on this since weeks already. Manual withdraw only works every 20-30 minutes and all the other time he can work on it. On top... if it would be easy then other real bitcoind devs would have solved this already.

[Pompobit]

Revert the withdrawal requests and send the btc back to the bitfunder account would not avoid the bitcoind problems?
And lower the withdrawal's waiting list for Ukyo, too.

I'd like it, so I could buy my last shares before the closure and help who just wants his btc back to get them sooner

[lophie]

sigh, Stop posting that "over and over and over" and STOP THE WITHDRAWING FUNCTIONALITY!.

now I told you, Dump all using pywallet, install the latest electrum and connect using tor, import all addresses and move the coins to a single or a couple of addresses, import them in a wallet.dat. Headache done, this solution WILL stick for a while.

Of course you want a permenant solution, USE LIBBITCOIN.

[SebastianJu]

Revert the withdrawal requests and send the btc back to the bitfunder account would not avoid the bitcoind problems?
And lower the withdrawal's waiting list for Ukyo, too.

I'd like it, so I could buy my last shares before the closure and help who just wants his btc back to get them sooner

That probably wouldnt help since the problem seems to be that bitcoind is checking thousands of bitcoin addresses if they have bitcoins in it to do a withdraw. So it doesnt matter how many withdraws are waiting.

[Pompobit]

Revert the withdrawal requests and send the btc back to the bitfunder account would not avoid the bitcoind problems?
And lower the withdrawal's waiting list for Ukyo, too.

I'd like it, so I could buy my last shares before the closure and help who just wants his btc back to get them sooner

That probably wouldnt help since the problem seems to be that bitcoind is checking thousands of bitcoin addresses if they have bitcoins in it to do a withdraw. So it doesnt matter how many withdraws are waiting.

I'm not saying unlocking funds on bitfunder from limbo would fix bitcoind issues, but if Ukyo is processing tickets in chronological order, popping withdrawals from the waiting list will shift all the widrawals made later.
Or to revert a withdrawal request is not possible? The transfers between weexchange and bitfunder are always instantaneous, so seem like virtual passages. And hadn't Ukyo mentioned he could have canceled withdrawals to input.io?

[SebastianJu]

Revert the withdrawal requests and send the btc back to the bitfunder account would not avoid the bitcoind problems?
And lower the withdrawal's waiting list for Ukyo, too.

I'd like it, so I could buy my last shares before the closure and help who just wants his btc back to get them sooner

That probably wouldnt help since the problem seems to be that bitcoind is checking thousands of bitcoin addresses if they have bitcoins in it to do a withdraw. So it doesnt matter how many withdraws are waiting.

I'm not saying unlocking funds on bitfunder from limbo would fix bitcoind issues, but if Ukyo is processing tickets in chronological order, popping withdrawals from the waiting list will shift all the widrawals made later.
Or to revert a withdrawal request is not possible? The transfers between weexchange and bitfunder are always instantaneous, so seem like virtual passages. And hadn't Ukyo mentioned he could have canceled withdrawals to input.io?

He can cancel withdraws instantly.

The bitcoins at bitfunder arent at bitfunder. Weexchange keeps them all the time. They arent moved really.

The waiting list shouldnt be nothing really problematic. Its only 200 or so requests. Thats nothing for a database. It makes practically no difference to take a withdraw out because it was done manually.

[Ukyo]

sigh, Stop posting that "over and over and over" and STOP THE WITHDRAWING FUNCTIONALITY!.

now I told you, Dump all using pywallet, install the latest electrum and connect using tor, import all addresses and move the coins to a single or a couple of addresses, import them in a wallet.dat. Headache done, this solution WILL stick for a while.

Of course you want a permenant solution, USE LIBBITCOIN.

This would be a great solution except that I am not looking to shut down the site.
The system must stay in sync with the backend for tracking and audit purposes.
We can not have divergence.

I do not want to disable the withdraw functionality because requests need to be able to be made.

Please also keep in mind, I am verifying all the transactions to make sure there are no double sends.
Just because there was an rpc time out during the withdraw process does not necessarily mean that bitcoind did not eventually process the withdraw. I am sure no one wants to get told later "oops, the system sent X bitcoins to many people more than once because of making haste so there are not enough bitcoins remaining for you"

I am currently talking with a couple people about real solutions and depending on their time and its effectiveness I am hoping to have at least one option tested and possibly running by this weekend.

There are more than 200 withdraws. Lot's of people seem to think if X withdraw does not work, let's try Y.. then Z... etc.
This has only caused even more delays.

Withdraws can be canceled.

-Ukyo

[kmtan]

sigh, Stop posting that "over and over and over" and STOP THE WITHDRAWING FUNCTIONALITY!.

now I told you, Dump all using pywallet, install the latest electrum and connect using tor, import all addresses and move the coins to a single or a couple of addresses, import them in a wallet.dat. Headache done, this solution WILL stick for a while.

Of course you want a permenant solution, USE LIBBITCOIN.

This would be a great solution except that I am not looking to shut down the site.
The system must stay in sync with the backend for tracking and audit purposes.
We can not have divergence.

I do not want to disable the withdraw functionality because requests need to be able to be made.

Please also keep in mind, I am verifying all the transactions to make sure there are no double sends.
Just because there was an rpc time out during the withdraw process does not necessarily mean that bitcoind did not eventually process the withdraw. I am sure no one wants to get told later "oops, the system sent X bitcoins to many people more than once because of making haste so there are not enough bitcoins remaining for you"

I am currently talking with a couple people about real solutions and depending on their time and its effectiveness I am hoping to have at least one option tested and possibly running by this weekend.

There are more than 200 withdraws. Lot's of people seem to think if X withdraw does not work, let's try Y.. then Z... etc.
This has only caused even more delays.

Withdraws can be canceled.

-Ukyo

Let plan it well, having a clear picture to everyone...if not the situation getting bad.

[thecoinjournal]

So Ukyo, if I want to make a withdraw, which method would you suggest among these three:

1. Withdraw and wait without submitting a ticket;
2. Withdraw and submit a support ticket;
3. Don't withdraw and wait for the problem to be solved.

If choose not to withdraw currently can help, I can wait for a few days.

Thanks!

[lophie]

More importantly, ETA?

[stonehoo]

More importantly, ETA?

no nothing,,,,, just time to delay more......

[carnivale]

Well, I'm still waiting for my October 23 withdrawal..

Over the course of the last few weeks, I've tried everything:
1)opened multiple support tickets on weexchange
2)opened a support ticket on bitfunder
3)sent emails
4)found the secret hotline number, called it every other day
5)opened an account on bitcointalk just to send ukyo a pm

 and this is the feedback I received:
1)No reply
2)"Please contact weexchange" 
3)No reply
4)"Ukyo is at a meeting"
5)No reply

It's only 19.1BTC, but these are all the bitcoins that I have. And if getting them back requires legal action, then I will do so. I'm too tired of this.

[azaniet]

Well, I'm still waiting for my October 23 withdrawal..

Over the course of the last few weeks, I've tried everything:
1)opened multiple support tickets on weexchange
2)opened a support ticket on bitfunder
3)sent emails
4)found the secret hotline number, called it every other day
5)opened an account on bitcointalk just to send ukyo a pm

 and this is the feedback I received:
1)No reply
2)"Please contact weexchange" 
3)No reply
4)"Ukyo is at a meeting"
5)No reply

It's only 19.1BTC, but these are all the bitcoins that I have. And if getting them back requires legal action, then I will do so. I'm too tired of this.

Exactly the same here..

[Sanqianli]

Well, I'm still waiting for my October 23 withdrawal..

Over the course of the last few weeks, I've tried everything:
1)opened multiple support tickets on weexchange
2)opened a support ticket on bitfunder
3)sent emails
4)found the secret hotline number, called it every other day
5)opened an account on bitcointalk just to send ukyo a pm

 and this is the feedback I received:
1)No reply
2)"Please contact weexchange" 
3)No reply
4)"Ukyo is at a meeting"
5)No reply

It's only 19.1BTC, but these are all the bitcoins that I have. And if getting them back requires legal action, then I will do so. I'm too tired of this.

Exactly the same here..

+1