3. It's probably pooled. This allows people that deposit USD to sell BTC or people who deposit BTC to buy more BTC. It wouldn't make sense for Bitcoinica to use their own funds for every hedge, because that would require insane reserves.
so someone who deposits $50K, doesn't establish a position, gets that $50K added to the pool, might in fact not be able to establish a position in a red flag event. is this fair?
If you don't like it, don't use Bitcoinica. Nobody is forcing you. And remember this pooling is always only temporary. Your funds are never "gone" or anything like that.
why does everyone say this when asked questions?
4. Not sure, you'll have to ask Zhoutong. Still, as I've said again and again, there's no reason to use market orders when you go do the same with limit orders and more. Imaging wanting to click when it's at 4$ and you're too slow to notice a spike, and you click at whatever other price is displays instead.
but a market and limit order are not the same thing. they serve different useful functions. sure a limit order is safer. but if the displayed ask @$4 keep moving up after you've clicked the button, it sounds like it won't fill and you could be stuck chasing it. a market order, will sweep up and thru any asks that are listed until its filled. when i trade stocks, the execution is instantaneous (relatively) so i'm not too exposed to a spike. but a 4 sec delay could spell death to your acct as we saw on the spike to 4.95.
you didn't answer my question about whether you had a financial link to Bitcoinica.
For #3, everything put into Bitcoinica would be part of the pool I'd imagine. If everyone puts in USD and takes a long position, then very quickly Bitcoinica would have to start buying BTC in order to cover those. Likewise, if everyone put in BTC and took a short position, Bitcoinica would have to start selling BTC in order to have enough reserve. Over time, of course, Bitcoinica has been increasing their holding of both USD and BTC because they get their 1-5% margin wherever the market goes. They've also likely lost at least a portion of that to accounts that got force liquidated at a price that left them negative. Still, I'm sure they're way ahead overall. Realistically, if Bitcoinica has something like $100K USD long and $100K USD short (probably more like $500K or even $1000K each), both sides can't be right and so when the market moves one way or the other, one side loses, the other side wins, and Bitcoinica always wins.
For #4, if you put in a market order buy at $5 a fraction of a second before or after someone on MtGox sends through a $10K buy order that moves the price up $1, yes, you'd get dinged for that extra $1 (and perhaps more as the sudden spike would likewise cause a sudden jump in leverage "just in case"). There is no such thing as "instantaneous" transactions, but of course at MtGox if you put in a sell for $5 right about the same time someone else puts in a huge sell order at $4.999, at least your sell won't ever execute. When you're trading market orders, you're always running a risk that someone, somewhere is putting in a huge sell/buy right before you -- whether it's delayed four seconds or not. In fact, if you go to MtGox and put in a sell order at $4 right now, and watch MtGoxLive, you'll see that it doesn't execute immediately, and in heavy traffic there could be many seconds of delay (though your order is at least put in the queue somewhere). Best-case, though, "instant" on the Internet still has to account for round trip time of the network traffic ("ping"), which would likely be at least half a second for your order to go to MtGox, process, and send the update out over the network API. The only place that could really execute an "instant" trade would be MtGox itself, and they would need to do something like this: pause all other trades, execute our trade at the current prices, and then resume all other trades. Then they would know for sure exactly what the price will be. All of that is more or less happening in real-time, except that they just take the top order from the queue and execute it (or if it's not an order that will actually commit right now, they put it on the order books).