I did a reinstall of Win7 2 days ago,my wallet just finshed DL'ing the blockchain,so 2 days is about right.I am not defending or supporting,just stating a fact.

Of course I have no need for speed myself,but I do have 2 "spare/backup" wallets on other PC's that are always "caught up" just in case.All I do is swap my dat & I'm in my main wallet.

Hope you guys get your BTC/money back soon  

Just so everyone knows I am ignoring all hostility and lies. I will not respond to them.

Can we rename this thread to "Guy tries to prove his superiority on the internet and casually propose pet theories while trolls troll and others waste time responding"

BitFloor does not charge any fees for cash deposits. All fees are charged by LocalTill, which is a third party processor. There are no hidden fees. I will update the notice for clarity. Thank you for the feedback.

Now, that I think about it, maybe the solution is to write an optional donation into the default client. If each transaction had a small donation to the development team, then they could potentially fund a larger operation, hire QC, etc.

Hey, I am only 140 IQ.

The BDB limit is the default set_lk_max_locks (max locks) setting of 10000. It is easily fixed by including a DB_CONFIG file in the 0.7 bitcoin application directory with a higher max locks setting.

That DB_CONFIG file should allow 0.7 clients to accept blocks up to the 1MB hard/protocol limit without choking, as the developers were expecting when they released 0.8 and asked pools to raise their target block sizes to the 1MB limit.

If you wanted to make a sustainable attack of 1000 transactions per 10 minutes (which current network could probably handle), you would need at least 0.01*144*1000*100 = 144000 btc (making 0.01 btc payments for 144 blocks in a day, 1000 transactions per block, and each 0.01 btc input has a 100 day "cooldown period"). Does this look accurate?

This is your post from august 2012. And you're telling us bitcoin has serious flaws? Yeah.

Why do you call MP they? Because of his multiple personality disorder? Because you think PR is hot? There is no "they" here.  How many people you hiding up there MP?

Well, in my opinion there are several steps that would be key improvements:

- Create a chained trust system, this would allow a transaction to be verified by a logarithmically smaller number of clients; the key observation here is that to prevent double spending you do not need a majority of machines to vote, you only need a quorum of trusted machines; to understand this note that there are the so-called "5 degrees of separation" meaning that you "know" everybody in the world friend of a friend of a friend, etc. If each client has a "reputation" with its neighboring clients, you can create a web of trust such that a transaction can be verified with only a hundred or so votes, instead of the thousands (or millions?) now necessary. Also, these votes will tend to happen on the fastest machines, thus further speeding the process.

- Generate new bitcoins proportionally to the volume of transactions and distribute the new coins proportionately to existing holders of bitcoins; the whole mining thing is pointless and destabilizing.

- Base transaction priority on reputation, not age/size the way it is now. This will speed transactions being done by the largest, most trusted players and push out DOS transactions in a way far more effective and secure than the current system which can be gamed in all sorts of ways.

I would note that a web of trust is also critical to protecting the network against a motivated minority from taking over the system. In the current system, its one machine, one vote. This ill-conceived design has the result that a small group of professionals using large botnets could outvote the network or a big enough sub-network such that they could seize or create coins. As the value of bitcoins grows the feasibility of this kind of attack is increasing. In a reputation system, not all machines have the same vote, but more trusted machines have greater weight, this prevents the possibility of a zombie attack.

The "manual tweak" is exactly two lines. Anyone can apply it, because the recompilation is not necessary. All it takes is to create a short text file and restart the bitcoin client.

https://bitcointalk.org/index.php?topic=152208.0

The limitation is not related to block size, but rather number of transactions accessed/updated by a block.

In general, the default for 0.8 (250k) is fine.  Raising that to 500k is likely just as fine.

But it is not very simple to answer the question, because this 0.7 BDB lock issue becomes more complicated with larger BDB transactions.

Tom, what keeps you from posting a list of order number with a refund status and maintain that list in public?

I am sorry if I left this out, I have purchased a couple hundred BTC and have some more on the way - As soon as my block chain downloads
34700 left to download now I will begin todays refunds. If anyone emails me I will reply today.
Everyone will be refunded starting in 3400 or so blocks - people will post confirmations today. I hope this is enough information for you
Im not going to bicker with anyone Im just going to refund them, I dont care about the scammer tag anymore have a nice day.

All software projects have bugs.  Salaries are for work not perfection. 

I'm sorry your angry. I fucked up. I poorly managed this business. I completely fucked it up and its my fault but I did not do it with the intention of scamming anyone.


I will admit that although my FPGA business was going well until they became obsolete, I was way out of my league when it came to making an ASIC - I fucked it up, I ruined my business and if it makes you feel any better I feel like a piece of shit every day.


I should have a couple hundred BTC by the end of the day - the entirety of that will go to refunds.

There's nothing I can do other than pay people back and believe me or not I will continue to do so util everyone is paid.

I am sorry about my attitude, I did not mean to come off like that - please everyone can you find it in your heart to forgive me for my poor attitude. This is a very humbling experience for me.

When I feel like  I am being attacked - I tend to act immaturely and fight back and I am truly sorry.

Your right its no ones fault but my own that this happened but you can ask the people I was working with I never once had the intentions of scamming anyone. There's no point in it for me, I made nothing from this and I am spending my own money to pay it back.

I don't want you to feel sorry for me I dont want pity I just want you to work with me.

thanks to those who can feel at least some empathy towards me. My wallet has 36920  blocks left to download and then the refunds will begin.

As a professional software developer this may be an opportune time to point out that the bitcoin code is an amateur production.

I have the greatest respect for Gavin and others that have donated untold hours to make bitcoin into a reality and I know from experience how tough self-funded development is.

Nevertheless, make no mistakes, the current incarnation of Bitcoin has a lot of ill-conceived design points and implementation weaknesses (as we have seen from the events of the last 24 hours).

Aside from the blunder that just resulted in a blockchain fork, there is a much larger, related issue looming on the horizon, which is the inability of the design to process large numbers of transactions. It is ludicrous we have people whining about "Satoshi Dice" creating numerous transactions. I could sit down and write a software component that could easily generate billions of transactions without breaking a sweat once it is deployed to a few thousand boxes, if I so chose, and yet you are concerned about Satoishi Dice generating a few million transactions. The problem of high-volume transaction handling needs to be answered at a new level which is, unfortunately, way above the paygrade of the current development team.

You have no evidence that he didn't.