SatoshiDICE hit 1,000,000 bets today

[evoorhees]

i hope you will invest them into more bitcoin projects

That goes without saying

[1714855889]

1714855889

[1714855889]

1714855889

[1714855889]

1714855889

[jgarzik]

Can you fix the SatoshiDICE software to stop generating a ton of tiny outputs, in the event of a loss?  One of the long term drains on resources is tracking unspent coins -- and SD creates 0.00000001 outputs for losing bets.  We have to individually track each one of those outputs until it is spent.  Of course, it is difficult for users to find ways to spend 0.00000001 BTC, so the obvious database bloat for each bitcoin user results...

[apetersson]

Can you fix the SatoshiDICE software to stop generating a ton of tiny outputs, in the event of a loss?  One of the long term drains on resources is tracking unspent coins -- and SD creates 0.00000001 outputs for losing bets.  We have to individually track each one of those outputs until it is spent.  Of course, it is difficult for users to find ways to spend 0.00000001 BTC, so the obvious database bloat for each bitcoin user results...

it is a little bit offtopic, but may i suggest that if that becomes a concern - the bitcoin client just merges the output with a regular transaction just for defragmenting reasons? as a coin selection algorithm it could always pick the smallest outputs first for example. obviously there could be multiple (configurable) coin selectors, with different focus. privacy, output minimisation, transaction size/fee minimisation..

[jgarzik]

Can you fix the SatoshiDICE software to stop generating a ton of tiny outputs, in the event of a loss?  One of the long term drains on resources is tracking unspent coins -- and SD creates 0.00000001 outputs for losing bets.  We have to individually track each one of those outputs until it is spent.  Of course, it is difficult for users to find ways to spend 0.00000001 BTC, so the obvious database bloat for each bitcoin user results...

it is a little bit offtopic, but may i suggest that if that becomes a concern - the bitcoin client just merges the output with a regular transaction just for defragmenting reasons? as a coin selection algorithm it could always pick the smallest outputs first for example. obviously there could be multiple (configurable) coin selectors, with different focus. privacy, output minimisation, transaction size/fee minimisation..

gmaxwell already made a basic patch, but it wasn't good for privacy, so it's not ready yet.

Regardless, that does not fix all the implementations in the field now, nor does it fix non-Satoshi clients such as MtGox etc.

Because the network must always track every unspent coin, creating tons of difficult-to-spend coins is network unfriendly.

[dree12]

Can you fix the SatoshiDICE software to stop generating a ton of tiny outputs, in the event of a loss?  One of the long term drains on resources is tracking unspent coins -- and SD creates 0.00000001 outputs for losing bets.  We have to individually track each one of those outputs until it is spent.  Of course, it is difficult for users to find ways to spend 0.00000001 BTC, so the obvious database bloat for each bitcoin user results...

I'm not educated on this. Is there a reason why they cannot simply not pay BTC during a loss?

[drakahn]

Can you fix the SatoshiDICE software to stop generating a ton of tiny outputs, in the event of a loss?  One of the long term drains on resources is tracking unspent coins -- and SD creates 0.00000001 outputs for losing bets.  We have to individually track each one of those outputs until it is spent.  Of course, it is difficult for users to find ways to spend 0.00000001 BTC, so the obvious database bloat for each bitcoin user results...

I'm not educated on this. Is there a reason why they cannot simply not pay BTC during a loss?

Sending a loss would mean people know the difference between losing and dice lag at least

[dree12]

Can you fix the SatoshiDICE software to stop generating a ton of tiny outputs, in the event of a loss?  One of the long term drains on resources is tracking unspent coins -- and SD creates 0.00000001 outputs for losing bets.  We have to individually track each one of those outputs until it is spent.  Of course, it is difficult for users to find ways to spend 0.00000001 BTC, so the obvious database bloat for each bitcoin user results...

I'm not educated on this. Is there a reason why they cannot simply not pay BTC during a loss?

Sending a loss would mean people know the difference between losing and dice lag at least

Why can't they publish the losses on their website?

[drakahn]

Can you fix the SatoshiDICE software to stop generating a ton of tiny outputs, in the event of a loss?  One of the long term drains on resources is tracking unspent coins -- and SD creates 0.00000001 outputs for losing bets.  We have to individually track each one of those outputs until it is spent.  Of course, it is difficult for users to find ways to spend 0.00000001 BTC, so the obvious database bloat for each bitcoin user results...

I'm not educated on this. Is there a reason why they cannot simply not pay BTC during a loss?

Sending a loss would mean people know the difference between losing and dice lag at least

Why can't they publish the losses on their website?

They do, but, i think a lot of the popularity is in the instant response and the bot-ability of it, my bot was a constant adrenaline generator lol (of course it lost in the end, i was expecting it too, interesting to see how many losses in a row will eventually come with enough monkey's on typewriters)