Quote from: Rothgar on May 10, 2012, 03:22:29 AM

Does anyone else have an answer to these type of questions?

Someone else may have a stock storefront they can point you to, but I can tell you how I'd implement it...

You have the game running on server X. You have litecoind (preferably stripped down to only accept the two RPC commands mentioned below) running on server Y (And although X could equal Y, that just begs to get hacked).

When someone goes to make a payment, you invoke the getnewaddress RPC call (remote this however you like - I'd probably go for a simple webservice wrapper rather than expose "real" RPC to the network), and tell the customer to send however many LTC to that address.

Once a minute or so, you invoke listtransactions (you could hook this in a cleaner way and thus avoid polling, but seriously, not a lot of overhead here on the wallet-side) with only a tiny change to the litecoind source, but I'll presume from the nature of the question that you want to minimize custom coding here) and compare it against your list of outstanding payments. If you have a match, credit the customer for their purchase. Note that you can do almost all of that on Y and send a message (via Email for all it matters) to X on receipt, rather than having X and Y chattering constantly for no reason.

And as a matter of good practice, you really shouldn't keep more LTC on Y than you could stand to lose; Manually send its balance to a "real" account, preferably on a normally-offline machine, on a reasonably frequent basis (daily?).

Quote from: localhost on May 10, 2012, 11:06:34 AM

Also, hashrate has dropped quite a bit despite the release of a GPU miner.

I would say instead that it dropped because of the GPU miner, which stripped it of at least part of its raison d'etre as a GPU-hostile alternative to BitCoin. That said, you still don't have quite the disparity between CPU and GPU mining as you do with BitCoin, so I for one continue to have a lot of hope for LTC (or at least, only slightly less than I do for BitCoin, which too sadly seems to have jumped the shark already).

/ Sorry if this posts more than once, it gave an error on my first try...