Quote from: davout on July 18, 2012, 04:18:27 PM

Quote from: Herodes on July 18, 2012, 04:10:33 PM

Quote from: phantomcircuit on July 17, 2012, 11:23:54 PM

The size of the receive wallet has outgrown the server it was operating on.

Would not a security expert anticipate this in advance ?

I deal with the Instawallet shared wallet, which is probably an order of magnitude larger than Intersango's, and yes, it takes a little while to boot up, but when it's done it runs fine and smooth.

Now that I think about it, it might be that they're using the 'accounts' feature of bitcoind, which scales terribly. So guys, protip, use a monitortx patch and let bitcoind notify your backend, just poll the client to update confirmation counts once it notifies you of an incoming block.

I seriously doubt that.

The wallet for intersango is probably larger than any other wallet except gox (who dont use bitcoind).

We've had people running arbitrage bots 24/7 for essentially a year at this point.

That's a LOT of transactions to record.

And no we dont use accounts, I was probably the first person to vocally tell people to not use that particular "feature".

Anyways this was triggered by someone spamming the wallet with a very larger number of small transactions, of course I've always known this could be an issue but dealing with it is mostly a matter of money I didn't do anything about it.