User:Gmaxwell/utxo spring cleaning - Revision history

Gmaxwell at 10:30, 5 September 2013

2013-09-05T10:30:08Z

← Older revision		Revision as of 10:30, 5 September 2013
Line 6:		Line 6:
	* Coin control (almost done)		* Coin control (almost done)
	* free transaction policy biasing priority in favor of txn that reduce utxo set size ([https://github.com/bitcoin/bitcoin/pull/2945 pull req])		* free transaction policy biasing priority in favor of txn that reduce utxo set size ([https://github.com/bitcoin/bitcoin/pull/2945 pull req])
	* wallet fragmentation visualization ~~tool~~		* wallet fragmentation visualization
	* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.		* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.
	** Requires making the address grouping stuff more computationally efficient.		** Requires making the address grouping stuff more computationally efficient.

Gmaxwell at 10:29, 5 September 2013

2013-09-05T10:29:21Z

← Older revision		Revision as of 10:29, 5 September 2013
Line 9:		Line 9:
	* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.		* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.
	** Requires making the address grouping stuff more computationally efficient.		** Requires making the address grouping stuff more computationally efficient.
	* Ability in the wallet to specify sending _all_ your funds (minus whatever fees are required). Right now wallets often get abandoned with tiny amounts of dust remaining. (Electrum can do this)		* Ability in the wallet to specify sending _all_ your funds (minus whatever fees are required). Right now wallets often get abandoned with tiny amounts of dust remaining after users have manually searched for a value small enough to make it through. (Electrum can do this)

	Less likely things:		Less likely things:

Gmaxwell at 10:28, 5 September 2013

2013-09-05T10:28:38Z

← Older revision		Revision as of 10:28, 5 September 2013
Line 9:		Line 9:
	* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.		* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.
	** Requires making the address grouping stuff more computationally efficient.		** Requires making the address grouping stuff more computationally efficient.
	* Ability in the wallet to specify sending _all_ your funds (minus whatever fees are required). Right now wallets often get abandoned with tiny amounts of dust remaining.		* Ability in the wallet to specify sending _all_ your funds (minus whatever fees are required). Right now wallets often get abandoned with tiny amounts of dust remaining. (Electrum can do this)

	Less likely things:		Less likely things:

Gmaxwell: sending all funds

2013-09-05T10:28:10Z

sending all funds

← Older revision		Revision as of 10:28, 5 September 2013
Line 9:		Line 9:
	* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.		* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.
	** Requires making the address grouping stuff more computationally efficient.		** Requires making the address grouping stuff more computationally efficient.
			* Ability in the wallet to specify sending _all_ your funds (minus whatever fees are required). Right now wallets often get abandoned with tiny amounts of dust remaining.

			Less likely things:

	* Functionality to aid people in automatically 'giving away' configurable very small payments, e.g. you set it so that if you receive a payment less than 0.00001 you'll author a OP_RETURN,0 output ANYONE_CAN_PAY\|NONE transaction and broadcast it. Many of these can be merged to give away this dust to miners.		* Functionality to aid people in automatically 'giving away' configurable very small payments, e.g. you set it so that if you receive a payment less than 0.00001 you'll author a OP_RETURN,0 output ANYONE_CAN_PAY\|NONE transaction and broadcast it. Many of these can be merged to give away this dust to miners.
	* Change rounding to avoid change:		* Change rounding to avoid change:

Gmaxwell: helps if I remember the external link syntax

2013-09-01T10:07:55Z

helps if I remember the external link syntax

← Older revision		Revision as of 10:07, 1 September 2013
Line 5:		Line 5:
	* OP_RETURN exclusion from UTXO set (almost done)		* OP_RETURN exclusion from UTXO set (almost done)
	* Coin control (almost done)		* Coin control (almost done)
	* free transaction policy biasing priority in favor of txn that reduce utxo set size ([~~pull req~~ https://github.com/bitcoin/bitcoin/pull/2945])		* free transaction policy biasing priority in favor of txn that reduce utxo set size ([https://github.com/bitcoin/bitcoin/pull/2945 pull req])
	* wallet fragmentation visualization tool		* wallet fragmentation visualization tool
	* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.		* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.

Gmaxwell: there is a pull on this now

2013-09-01T10:07:29Z

there is a pull on this now

← Older revision		Revision as of 10:07, 1 September 2013
Line 5:		Line 5:
	* OP_RETURN exclusion from UTXO set (almost done)		* OP_RETURN exclusion from UTXO set (almost done)
	* Coin control (almost done)		* Coin control (almost done)
	* free transaction policy biasing priority in favor of txn that reduce utxo set size		* free transaction policy biasing priority in favor of txn that reduce utxo set size ([pull req https://github.com/bitcoin/bitcoin/pull/2945])
	* wallet fragmentation visualization tool		* wallet fragmentation visualization tool
	* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.		* Adjust coin selection to attempt to spend whole privacy groups, subject to transaction size limits and some change size targeting.

Gmaxwell: utxo-bytes days destroyed.

2013-08-14T23:37:48Z

utxo-bytes days destroyed.

← Older revision		Revision as of 23:37, 14 August 2013
Line 14:		Line 14:
	** There should be an adjustable option to round down change to zero, converting it to fees. We already do this for >0.01 for free transactions to avoid mandatory fees, but it could be made more general and configurable.		** There should be an adjustable option to round down change to zero, converting it to fees. We already do this for >0.01 for free transactions to avoid mandatory fees, but it could be made more general and configurable.
	* Mining logic to merge up ANYONE_CAN_PAY\|NONE transactions		* Mining logic to merge up ANYONE_CAN_PAY\|NONE transactions
	* UTXO cleaning contest: Get money from BTC foundation (and perhaps other interested parties), every UTXO destroyed which was created before some date (perhaps Aug 1st 2013) gets entered into a lottery~~, perhaps with some weight to inverse-btc days destroyed~~. Big BTC payouts in the lottery to encourage people to dig up old and inactive wallets with dust.		* UTXO cleaning contest: Get money from BTC foundation (and perhaps other interested parties), every UTXO destroyed which was created before some date (perhaps Aug 1st 2013) gets entered into a lottery. Big BTC payouts in the lottery to encourage people to dig up old and inactive wallets with dust.
	** perhaps only those submitted via ANYONE_CAN_PAY\|NONE to some site, to avoid sending winnings to dead keys or disinterested users, perhaps don't require utxo submission but allow people to claim credit for their UTXO cleanup via some signmessage stuff.		** perhaps only those submitted via ANYONE_CAN_PAY\|NONE to some site, to avoid sending winnings to dead keys or disinterested users, perhaps don't require utxo submission but allow people to claim credit for their UTXO cleanup via some signmessage stuff.
			** perhaps with some weight to inverse-btc days destroyed or utxo-bytes days destroyed.

Gmaxwell: additions

2013-08-14T23:35:19Z

additions

← Older revision		Revision as of 23:35, 14 August 2013
Line 11:		Line 11:
	* Functionality to aid people in automatically 'giving away' configurable very small payments, e.g. you set it so that if you receive a payment less than 0.00001 you'll author a OP_RETURN,0 output ANYONE_CAN_PAY\|NONE transaction and broadcast it. Many of these can be merged to give away this dust to miners.		* Functionality to aid people in automatically 'giving away' configurable very small payments, e.g. you set it so that if you receive a payment less than 0.00001 you'll author a OP_RETURN,0 output ANYONE_CAN_PAY\|NONE transaction and broadcast it. Many of these can be merged to give away this dust to miners.
	* Change rounding to avoid change:		* Change rounding to avoid change:
	** on sending a payment there should be an option to round the payment up by up to [configurable] if doing so will eliminate change. This is useful when sending funds to persistent "accounts"		** on sending a payment there should be an option to round the payment up by up to [configurable] if doing so will eliminate change. This is useful when sending funds to persistent bank-like "accounts" owned by the same user. E.g. I want to send 10 BTC to foo-exchange, but I'd be just as happy to send 10.009123184.
	** There should be an adjustable option to round down change to zero, converting it to fees. We already do this for >0.01 for free transactions to avoid mandatory fees, but it could be made more general and configurable.		** There should be an adjustable option to round down change to zero, converting it to fees. We already do this for >0.01 for free transactions to avoid mandatory fees, but it could be made more general and configurable.
	* Mining logic to merge up ANYONE_CAN_PAY\|NONE transactions		* Mining logic to merge up ANYONE_CAN_PAY\|NONE transactions
	* UTXO cleaning contest: Get money from BTC foundation (and perhaps other interested parties), every UTXO destroyed which was created before some date (perhaps Aug 1st 2013) gets entered into a lottery, perhaps with some weight to inverse-btc days destroyed. Big BTC payouts in the lottery to encourage people to dig up old and inactive wallets with dust.		* UTXO cleaning contest: Get money from BTC foundation (and perhaps other interested parties), every UTXO destroyed which was created before some date (perhaps Aug 1st 2013) gets entered into a lottery, perhaps with some weight to inverse-btc days destroyed. Big BTC payouts in the lottery to encourage people to dig up old and inactive wallets with dust.
	** perhaps only those submitted via ANYONE_CAN_PAY\|NONE to some site, to avoid sending winnings to dead keys or disinterested users, perhaps don't require utxo submission but allow people to claim credit for their UTXO cleanup via some signmessage stuff.		** perhaps only those submitted via ANYONE_CAN_PAY\|NONE to some site, to avoid sending winnings to dead keys or disinterested users, perhaps don't require utxo submission but allow people to claim credit for their UTXO cleanup via some signmessage stuff.

Gmaxwell: change rounding

2013-08-14T23:33:10Z

change rounding

← Older revision		Revision as of 23:33, 14 August 2013
Line 10:		Line 10:
	** Requires making the address grouping stuff more computationally efficient.		** Requires making the address grouping stuff more computationally efficient.
	* Functionality to aid people in automatically 'giving away' configurable very small payments, e.g. you set it so that if you receive a payment less than 0.00001 you'll author a OP_RETURN,0 output ANYONE_CAN_PAY\|NONE transaction and broadcast it. Many of these can be merged to give away this dust to miners.		* Functionality to aid people in automatically 'giving away' configurable very small payments, e.g. you set it so that if you receive a payment less than 0.00001 you'll author a OP_RETURN,0 output ANYONE_CAN_PAY\|NONE transaction and broadcast it. Many of these can be merged to give away this dust to miners.
			* Change rounding to avoid change:
			** on sending a payment there should be an option to round the payment up by up to [configurable] if doing so will eliminate change. This is useful when sending funds to persistent "accounts"
			** There should be an adjustable option to round down change to zero, converting it to fees. We already do this for >0.01 for free transactions to avoid mandatory fees, but it could be made more general and configurable.
	* Mining logic to merge up ANYONE_CAN_PAY\|NONE transactions		* Mining logic to merge up ANYONE_CAN_PAY\|NONE transactions
	* UTXO cleaning contest: Get money from BTC foundation (and perhaps other interested parties), every UTXO destroyed which was created before some date (perhaps Aug 1st 2013) gets entered into a lottery, perhaps with some weight to inverse-btc days destroyed. Big BTC payouts in the lottery to encourage people to dig up old and inactive wallets with dust.		* UTXO cleaning contest: Get money from BTC foundation (and perhaps other interested parties), every UTXO destroyed which was created before some date (perhaps Aug 1st 2013) gets entered into a lottery, perhaps with some weight to inverse-btc days destroyed. Big BTC payouts in the lottery to encourage people to dig up old and inactive wallets with dust.
	** perhaps only those submitted via ANYONE_CAN_PAY\|NONE to some site, to avoid sending winnings to dead keys or disinterested users, perhaps don't require utxo submission but allow people to claim credit for their UTXO cleanup via some signmessage stuff.		** perhaps only those submitted via ANYONE_CAN_PAY\|NONE to some site, to avoid sending winnings to dead keys or disinterested users, perhaps don't require utxo submission but allow people to claim credit for their UTXO cleanup via some signmessage stuff.

Gmaxwell: spelling

2013-08-14T23:29:22Z

spelling

← Older revision		Revision as of 23:29, 14 August 2013
Line 2:		Line 2:
	A brief plan to improve the state of the UTXO		A brief plan to improve the state of the UTXO

	* <s>relay policy adjustments to ~~may~~ very tiny notification payments unattractive</s>		* <s>relay policy adjustments to make very tiny notification/data-storage payments unattractive</s>
	* OP_RETURN exclusion from UTXO set (almost done)		* OP_RETURN exclusion from UTXO set (almost done)
	* Coin control (almost done)		* Coin control (almost done)