Bitcoin Forum
May 28, 2024, 05:15:38 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Blocking uneconomic UTXO creation  (Read 1174 times)
Peter Todd (OP)
Legendary
*
Offline Offline

Activity: 1120
Merit: 1150


View Profile
March 10, 2013, 01:59:50 AM
Last edit: March 10, 2013, 06:06:43 AM by retep
 #1

I've created a patch that blocks the creation of transaction outputs whose value is smaller than the fee per KB the transaction is paying. Basically it's blocking the creation of transaction outputs that would cost more to spend than they are worth. Because it determines this by fee, it's adaptive, and will automatically adjust as fees change. At the same time, if someone creates a really high fee transaction, like the recent 93BTC one, there is an upper limit, so you'll still collect it and profit.

Ultimately the issue is right now SatoshiDice is creating huge amounts of "you lost" transaction outputs that have a value so small they don't make sense to spend; >50% of the unspent transaction outputs are for just one satoshi. This hurts pool operators because while transaction history can be stored on slow hard-drives, and in the future pruned away, the set of all unspent transactions must be stored in fast memory so when your pool receives a new block you can validate every transaction spend, and start working on a new block. The bigger the UTXO set gets, the more RAM you need to provision for the computers your pool runs on.

If pool operators adopt this patch I expect SatoshiDice will simply change their failed bet outputs to always be > the transaction fee, and thus users will be able to spend those outputs. You'll still collect the large fees SatoshiDice is paying to miners, yet keep your costs down in the long run, and keep Bitcoin viable as a decentralized currency.

solex
Legendary
*
Offline Offline

Activity: 1078
Merit: 1002


100 satoshis -> ISO code


View Profile
March 11, 2013, 10:47:10 PM
 #2

retep, that patch sounds like great progress.

Regarding SD. the minimum bet is 0.01 BTC, so the minimum payout is 5,000 satoshi as it always returns at least 0.5%

Ok. I just checked on github and based on the latest revision dust is considered < 100,000 satoshi
However, the fx rate is 3 times higher since that was decided, so 33,000 is a reasonable comparison now. So any SatoshiDice bet above 0.07 will not leave a dust amount for a loss.
https://github.com/bitcoin/bitcoin/pull/2100

Since then I sampled a few thousand recent bets and found that 54% are 0.06 or less.

hobbes
Full Member
***
Offline Offline

Activity: 128
Merit: 107



View Profile
April 15, 2013, 12:35:45 PM
 #3

Does the patch allow 0 value tx? These don't have to be spent but can be pruned right away.

This nice timestamping service is the reason for my question:
http://vog.github.io/bitcoinproof/

It creates an address by hashing your data.

Peter Todd (OP)
Legendary
*
Offline Offline

Activity: 1120
Merit: 1150


View Profile
April 15, 2013, 01:53:49 PM
 #4

Does the patch allow 0 value tx? These don't have to be spent but can be pruned right away.

This nice timestamping service is the reason for my question:
http://vog.github.io/bitcoinproof/

It creates an address by hashing your data.

Such outputs can still be spent, so no it does not allow them. However, see my post here about prunable outputs: https://bitcointalk.org/index.php?topic=151329.msg1844144#msg1844144

I'm curious, have you tried my OpenTimestamps stuff? If so, what did you think?

hobbes
Full Member
***
Offline Offline

Activity: 128
Merit: 107



View Profile
April 15, 2013, 03:52:37 PM
 #5

Does the patch allow 0 value tx? These don't have to be spent but can be pruned right away.

This nice timestamping service is the reason for my question:
http://vog.github.io/bitcoinproof/

It creates an address by hashing your data.

Such outputs can still be spent, so no it does not allow them. However, see my post here about prunable outputs: https://bitcointalk.org/index.php?topic=151329.msg1844144#msg1844144
Interesting what you guys have going under the hood Smiley

I realized nobody would want his timestamping to be pruned so you would have to make it a spendable tx anyway.   Smiley

Quote
I'm curious, have you tried my OpenTimestamps stuff? If so, what did you think?
It looks very sophisticated. The other one is so simple it is brilliant in it's way.




Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!