Bitcoin Forum
September 19, 2018, 05:56:29 PM *
News: ♦♦ Bitcoin Core users must update to 0.16.3 [Torrent]. More info.
 
   Home   Help Search Donate Login Register  
Pages: « 1 [2]  All
  Print  
Author Topic: SatoshiDICE hit 1,000,000 bets today  (Read 5088 times)
evoorhees
Legendary
*
Offline Offline

Activity: 994
Merit: 1000


Democracy is the original 51% attack


View Profile
August 16, 2012, 04:29:44 AM
 #21

i hope you will invest them into more bitcoin projects Smiley

That goes without saying Wink
1537379789
Hero Member
*
Offline Offline

Posts: 1537379789

View Profile Personal Message (Offline)

Ignore
1537379789
Reply with quote  #2

1537379789
Report to moderator
1537379789
Hero Member
*
Offline Offline

Posts: 1537379789

View Profile Personal Message (Offline)

Ignore
1537379789
Reply with quote  #2

1537379789
Report to moderator
Make a difference with your Ether.
Donate Ether for the greater good.
SPRING.WETRUST.IO
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
jgarzik
Legendary
*
Offline Offline

Activity: 1554
Merit: 1001


View Profile
August 16, 2012, 06:13:52 AM
 #22


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...


Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own.
Visit bloq.com / metronome.io
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
apetersson
Hero Member
*****
Offline Offline

Activity: 666
Merit: 500



View Profile
August 16, 2012, 07:34:38 AM
 #23


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
Legendary
*
Offline Offline

Activity: 1554
Merit: 1001


View Profile
August 16, 2012, 06:15:15 PM
 #24


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.


Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own.
Visit bloq.com / metronome.io
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
dree12
Legendary
*
Offline Offline

Activity: 1246
Merit: 1031



View Profile
August 16, 2012, 08:07:19 PM
 #25


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
Hero Member
*****
Offline Offline

Activity: 504
Merit: 500



View Profile
August 16, 2012, 08:15:34 PM
 #26


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

14ga8dJ6NGpiwQkNTXg7KzwozasfaXNfEU
dree12
Legendary
*
Offline Offline

Activity: 1246
Merit: 1031



View Profile
August 16, 2012, 08:21:39 PM
 #27


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
Hero Member
*****
Offline Offline

Activity: 504
Merit: 500



View Profile
August 16, 2012, 08:24:34 PM
 #28


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)

14ga8dJ6NGpiwQkNTXg7KzwozasfaXNfEU
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!