Ok, so this thread is seriously unjustified at this point. Ukyo is clearly having difficulties delivering. But it does not justify a scam accusation so long as he appears to be working on the issue.
1. Speaking as a software engineer with a lot of experience dealing with software(and software failures) at scale, it is *very reasonable* that everything Ukyo is describing about the wallet difficulties could be true*. It is also very reasonable that there are few if any good solutions to this problem. This is compounded because A. Bitcoin is a new technology and has not yet hit/fixed these scaling limits, B. Bitcoin is a distributed computing problem, which introduces a lot more complexity, C. Bitcoin is an open source project, meaning few if any single team/individuals are accountable for these types of issues, and D. many of the teams working with Bitcoin, like Ukyo, both don't have the background/experience necessary to pre-emptively prevent these types of failures, they ALSO don't have the resources to call on to fix the issues quickly. This isn't some team at Microsoft that can just call up the developers on the phone who made the software for a bugfix.
Unless some other experienced software engineer(please state your background) wants to come in here and put his balls on the line claiming that Ukyo is full of shit and there's no way Bitcoind could fail like he has described, all claims that Ukyo is lying about the problem need to stop *RIGHT FUCKING NOW.* That would include Bitcoin developers like Luke-jr or Gavin, or anyone else who can prove what they are claiming.
My background is software engineering for Amazon before I jumped to be the technical director for Dave @ Mega Big Power(100TH mine), and a gaming industry programmer before that. Right this moment we are seeing difficulties of Bitcoind scaling internally- Getworks overwhelming out bitcoind clients, getinfo and gettransactions requests taking an excessive amount of time, and a huge drop in getwork throughput every time we receive a new block notification. Speaking from my experience, there is no doubt in my mind that Ukyo is telling the truth about the difficulties he is encountering. And unless someone else with the relevant experience wants to step up and put his balls on the line claiming Ukyo is lying(and explain why), that claim needs to stop right now.
To give even more backing to the idea of how the Bitcoin community handles 'scale' so far, when mining you are supposed to have one worker per device for clear tracking. I have asked two different pool operators if I could create just shy of a thousand workers for mining projects I am involved with. Both balked and said that would likely break their backend systems. Note that we aren't talking millions of items(like most websites must handle including this forum) or billions(like Amazon.com / Google / Facebook must handle), we're talking one thousand. Mostly these are database entries. The Bitcoin communities' software simply doesn't handle scale well.
* I am not claiming that Ukyo has handled this perfectly or made optimal decisions. He is human, after all. Mistakes or decisions made non-optimally does not warrant a scammer accusation.
2. Ukyo has been responding about this issue the whole time. He has not vanished with anyone's money. People have been getting payments for days now- Not perfectly consistently or constantly, but people have been getting payments, and Ukyo is under no obligation to do things the way you want.
3. Libbitcoin/Electrum -
First of all, Ukyo is not under any obligation to do things your way. Not doing so does not warrant a scammer tag, that isn't how scammer tags work. It sounds like his wallets may have thousands to tens of thousands of addresses/private keys, which might well break Electrum the same way. Even simply exporting all of these addresses would be a difficult proposition, and exporting/importing is necessary for libbitcoin as well.
Second, libbitcoin is going to be an unfamiliar software to Ukyo. Switching from something that is working(however badly) to something unknown is not an easy decision to make, and there are definitely costs with switching midstream. Furthermore, a bug or faillure of the system(which is not backed & tested by the full Bitcoin open source team, nor has it been used by many different people in large-scale applications) could cause irretrievable losses for Ukyo. And THEN you'd give him a scammer tag unless he could somehow prove to your hearts content that the coins were truly lost(Hint: You'd never be convinced anyway).
4. Demands and ETA -
Ukyo is not dealing with a simple physical labor problem. Software problems are complex and unpredictable. He can't give an ETA for how long it would take to solve the problem because he can't possibly know. Again, anyone who is an experienced software developer can step in here and tell me I am wrong, but they won't. The entire software industry is habitually late delivering despite best efforts(and crunch time) to avoid it. Software problem fixes are generally not predictable for ETA's. So he could make up some number far in the future and it is going to sound ridiculous to you and everyone else, which would piss you off more. Or he can make a reasonable guess, but with a significant chance he might miss that date. It is better for him simply to not give an ETA but rather give updates, and then those who know how these problems go and truly understand the issues can make their own predictions, and people like you who don't understand the problem can continue to rage.
Moreover, every time Ukyo tries something new to solve the problem, you can expect a several day delay. Working with software and existing other people's systems requires a bit of stumbling and learning every time you switch gears.
5. Fractional reserve claim -
This claim is completely unsubstantiated. The "word going around" does not represent reality nor is it a fact, and therefore it is not something you can make a demand. If you're going to make that accusation, you need proof. The burden of proof is on you buddy, not him.
And the fact that your demand is for a signed message from an address with the coin shows that you clearly have no grasp of this problem, and are in no position to be making a scam accusation. He can't sign from an address with the coin because no single address has the coin. If a single address did have the coin, bitcoind wouldn't be choking. Bitcoin is choking because the coin has been fractioned out over thousands(or tens of thousands) of addresses. Sure, if you want, I'm sure he could spend a week generating the 10,000 signatures necessary to account for all the coin. And you could spend a week verifying all of those. But I think everyone else here would rather he just continue working on the problem at hand.
6. Disabling withdraw from Weexchange
While this isn't a bad idea, it doesn't really solve anything. They can't withdraw now but they at least have a process to get a slow withdrawal started. Under your way they still couldn't withdraw, but now have no process to get one started. Doesn't seem to gain much.
And lastly, Lophie you are in no position personally to be making scam accusations. Firstly, you clearly don't have a grasp on the technical problems Ukyo has described, else you would not have demanded a signed message and made yourself look stupid. Secondly, I've caught you lying publically at least twice, so you should have left this scam accusation to someone with a clean record. Someone not approaching problems the way YOU demand does not make them a scammer.
Disclaimer: I have about ~20 BTC held up in Bitfunder/Weexchange that needs to be withdrawn.
