smickles: mircea_popescu: well, i was exaggerating about 'k's, i would, of course, cater to large clients

smickles: if only I had enough btc in my pocket to not care about floating users a few k coin here and there when I know there's 6 confirms on the tx

smickles: we're talking about a program here. all i'd have to do is a line that summs what I expect user accounts balances to be and compares it to the stat

smickles: mircea_popescu: the more i think about it. the 'watching mpex addy and keeping track of stuff internally' method isn't as complicated as i made it out to be

smickles: heh, i thought of situations like that :)

smickles: I was planning on haveing that be a manual process

smickles: i believe I'm doing everything else more than reasonably securely, but the deposit method, i'm unsure of

smickles: yes, i can prevent the exploit which I originally brought up thru careful monitoring, but who's to say there's one I have't thought of

smickles: yeah, (if i have teh btc in the mpex account as well)

smickles: meanwhile, i'll continue to occasionally bitch and moan about various things

smickles: i expect nothing less

smickles: heh, so your saying i'll need to update some regexes?

smickles: and i'm pretty sure, less complicated correlates with less exploitable

smickles: alright, after some thought, I think watching the mpex address and my mpex accout balance (while accounting for debits and credits from purchases, sales, surety, and outstanding orders) would work

smickles: or, i suppose the format would be more like :On Sat, 26 May 12 00:30:47 from 1BtCaddY~~ the sum of 0.34524457 BTC

smickles: I would only be charged for use of the margin if i exceeded the amount of btc which I had in the mpex account, right?

smickles: oh, i forgot you offered that

smickles: I'm working on it :P

smickles: hmm, if i wait to credit their account until I see the tx on the mpex addy, plus wait to see that amount hit my mpex funds, would that be enought to thwart a malicious user?

smickles: i just want to figure out an 'ironclad' way of doing this

smickles: and if I just wait for that specific amout to show up in my mpex account, i'm sure a clever scammer could engineer a way to fool my system and basically get a duplicate deposit

smickles: mircea_popescu: but say my mpex acout has 10 btc in it, the user deposits 100 btc (to my wallet), i have to confirm that, forward it to mpex and wait for the funds to show up in the CxBTC before they can do anything over 10BTC

smickles: mircea_popescu: if i had some confirmation of funds being available in a STAT, i could safely have the user send a deposit directly

smickles: darn, i was hoping to avoid making the deposit process longer

smickles: mircea_popescu: i would need to know when the funds became available in the account. is that not done manually?

smickles: i'm just going to have to do a bunch of addition and subtraction to verify actualization of deposits in order to have mpex sub-accounts, arn't i

smickles: ug, mircea_popescu, what am i missing here. Is there a way to see that a deposit has made it into an mpex accout other than seeing that the account balance is higher?

smickles: ok, i should call this thing "smickles' MPEX" or "SMEx" for short

smickles: mircea_popescu: well, i'm making db tables of my own to hold data for mpex sub-accounts

smickles: mircea_popescu: i wonder if i'm replicating your database tables, just with different names

smickles: i think that's against the business model

smickles: or am i just not thinking of this correctly