public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* Re: [Bitcoin-development] Dust recycling
       [not found] ` <3dfcdc$g3rb2n@ironport9.mayo.edu>
@ 2014-03-29 19:59   ` Justus Ranvier
  2014-03-29 20:05     ` Gregory Maxwell
  0 siblings, 1 reply; 4+ messages in thread
From: Justus Ranvier @ 2014-03-29 19:59 UTC (permalink / raw)
  To: Bitcoin Dev; +Cc: Goss, Brian C., M.D.


[-- Attachment #1.1: Type: text/plain, Size: 715 bytes --]

On 03/29/2014 07:55 PM, Goss, Brian C., M.D. wrote:
> Could you collect the dust into a transaction with no outputs (thus making it all tx fees) or putting in to an anyone can spend tx?
> 
> The large number of signatures (for large n) would make the tx size large...but, if enough dust were out there, it might be worth propagating to a pools hash power. 

What would make it easier is if there was a standard output type for
sending the entire transaction to miner fees, that would make even large
transactions propagate that would normally be dropped by fee/kB rules.

-- 
Support online privacy by using email encryption whenever possible.
Learn how here: http://www.youtube.com/watch?v=bakOKJFtB-k

[-- Attachment #1.2: 0x1B438BF4.asc --]
[-- Type: application/pgp-keys, Size: 21521 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bitcoin-development] Dust recycling
  2014-03-29 19:59   ` [Bitcoin-development] Dust recycling Justus Ranvier
@ 2014-03-29 20:05     ` Gregory Maxwell
  2014-03-29 20:20       ` Justus Ranvier
  0 siblings, 1 reply; 4+ messages in thread
From: Gregory Maxwell @ 2014-03-29 20:05 UTC (permalink / raw)
  To: Justus Ranvier; +Cc: Bitcoin Dev, Goss, Brian C., M.D.

On Sat, Mar 29, 2014 at 12:59 PM, Justus Ranvier
<justusranvier@gmail•com> wrote:
> What would make it easier is if there was a standard output type for
> sending the entire transaction to miner fees,

Hm. maybe it could be called a "return operator" or something like that? :)

> that would make even large
> transactions propagate that would normally be dropped by fee/kB rules.

Use dust-b-gone and make it someone elses problem to get it relayed. :)



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bitcoin-development] Dust recycling
  2014-03-29 20:05     ` Gregory Maxwell
@ 2014-03-29 20:20       ` Justus Ranvier
  2014-03-29 20:33         ` Gregory Maxwell
  0 siblings, 1 reply; 4+ messages in thread
From: Justus Ranvier @ 2014-03-29 20:20 UTC (permalink / raw)
  To: Gregory Maxwell; +Cc: Bitcoin Dev, Goss, Brian C., M.D.


[-- Attachment #1.1: Type: text/plain, Size: 400 bytes --]

On 03/29/2014 08:05 PM, Gregory Maxwell wrote:
> Use dust-b-gone and make it someone elses problem to get it relayed. :)
> 

That's a sub-optimal solution, as it introduces a third party. What if
his server goes down?

An universal solution is preferable.

-- 
Support online privacy by using email encryption whenever possible.
Learn how here: http://www.youtube.com/watch?v=bakOKJFtB-k

[-- Attachment #1.2: 0x1B438BF4.asc --]
[-- Type: application/pgp-keys, Size: 21521 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bitcoin-development] Dust recycling
  2014-03-29 20:20       ` Justus Ranvier
@ 2014-03-29 20:33         ` Gregory Maxwell
  0 siblings, 0 replies; 4+ messages in thread
From: Gregory Maxwell @ 2014-03-29 20:33 UTC (permalink / raw)
  To: Justus Ranvier; +Cc: Bitcoin Dev, Goss, Brian C., M.D.

On Sat, Mar 29, 2014 at 1:20 PM, Justus Ranvier <justusranvier@gmail•com> wrote:
> On 03/29/2014 08:05 PM, Gregory Maxwell wrote:
>> Use dust-b-gone and make it someone elses problem to get it relayed. :)
> That's a sub-optimal solution, as it introduces a third party. What if
> his server goes down?
> An universal solution is preferable.

Then start the server yourself. There is no replacement for
aggregating multiple bits of dust in single transactions. Other ways
are less efficient.

You can already OP_RETURN to include your dust, but miners aren't
going to automatically take that over transactions paying more in
terms of fee/byte.



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-03-29 20:33 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <mailman.85219.1396122262.2178.bitcoin-development@lists.sourceforge.net>
     [not found] ` <3dfcdc$g3rb2n@ironport9.mayo.edu>
2014-03-29 19:59   ` [Bitcoin-development] Dust recycling Justus Ranvier
2014-03-29 20:05     ` Gregory Maxwell
2014-03-29 20:20       ` Justus Ranvier
2014-03-29 20:33         ` Gregory Maxwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox