There's no way we can make it to the halving without increasing blocksize/implementing segwit. Despite handling bets offchain, Primedice still accounts for a solid amount of bitcoin transactions and small blocks are becoming a major issue. There's no way anyone who is against scaling or wants to scale slowly runs any sort of high transaction website/business.
+1, yeah. It's getting ridiculous.
Yeh, just add some fees.
For PD (and other sites) withdrawals, it could be interesting to have a "high priority" checkbox. So default is 0.00015, then with checkbox for example 0.0003 (paid by user.) I am sure some bigger players would pay bigger. And I also assume some people don't care waiting a day (if you don't need the funds right away), so lower fee should be fine for them.
Yeah, I actually sponsored the development of some patches that landed in bitcoin 0.12 to support this. Assuming you put a lock on bitcoin (so you don't send in parallel), you can now go:
bitcoin-cli settxfee `bitcoin-cli estimatefee $n`
bitcoin-cli sendtoaddress $address $amount
My intention was that I'd default to $n of like 3, but users could pay extra to switch to 2 or 1. The big problem is, it's pretty easy to run out of utxo's if you're not careful.
Other idea: how much space (and therefor fees) would be saved if withdrawals are in batches? Could be optional, every x hours, for those who are not in hurry. Could give lower fee to player too. But depends if it really saves space this way and if people are interested in it.
There's also a privacy cost to this, but it does have a lot of benefits. I suspect this would work especially well for a site like PrimeDice, which could probably save a lot on its tiny withdrawals. At least my site the main cost is just sourcing the transactions, so it wouldn't help that much (but segwit would)
