Was leaning towards my own bitcoind implementation - this confirms pretty much what I suspected. Thanks for the confirmation.
Quote
When a transaction is made it is broadcasted as an unconfirmed transaction across the network. ... So the answer is a few seconds to a minute, but the transaction may never confirm if it is double-spent or does not have enough of a transaction fee.
Great I didn't realize the unconfirmed transaction was propagated immediately.
My reasoning here is I can let a user start playing almost immediately. It's more important to to me to give a better user experience and allow instant access.
I understand the concept of a hot wallet and cold wallet - but thanks for pointing this out.
What I was interested in was more around some strategies for secure storage of private keys server side in regards to encryption/locking down bitcoind wallet.dat etc.....