Bitcoin Forum
August 16, 2018, 01:43:05 AM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 [2]  All
  Print  
Author Topic: Send full amount as a fee to miners  (Read 2180 times)
tspacepilot
Legendary
*
Offline Offline

Activity: 1456
Merit: 1013


I may write code in exchange for bitcoins.


View Profile
September 01, 2015, 07:56:47 PM
 #21

So the one output would have a value of 0 Satoshis and the script part would just be OP_RETURN + 40 bytes of data?
If this is the preferred dust cleanup transaction I'm happy to know it.
Yes. You are not forced to add 40 bytes of data.
The one-byte-output-script OP_RETURN and zero amount to it will send all your inputs to miner
for example:
https://blockchain.info/tx/3d665c1eb25160444cf053988a0d7d0c3ec5e68e3897a917d59447052788cfc5
note, that blockchain.info can not decode this output script to address and shows message "Unable to decode output address - (Unspent)"

I do not know what client is able to create such transactions.
It is quite easy, but I use my own tools.

One follow-up, according to the OP codes listed here https://en.bitcoin.it/wiki/Script, it seems that OP_RETURN:

Quote
Marks transaction as invalid. A standard way of attaching extra data to transactions is to add a zero-value output with a scriptPubKey consisting of OP_RETURN followed by exactly one pushdata op. Such outputs are provably unspendable, reducing their cost to the network. Currently it is usually considered non-standard (though valid) for a transaction to have more than one OP_RETURN output or an OP_RETURN output with more than one pushdata op

This is a little confusing because "valid" seems to be being used more than one way in the same paragraph.  I guess this isn't the kind of marking invalid which would cause a node not to relay the transaction?  What's the correct understanding of "valid" here?
1534383785
Hero Member
*
Offline Offline

Posts: 1534383785

View Profile Personal Message (Offline)

Ignore
1534383785
Reply with quote  #2

1534383785
Report to moderator
1534383785
Hero Member
*
Offline Offline

Posts: 1534383785

View Profile Personal Message (Offline)

Ignore
1534383785
Reply with quote  #2

1534383785
Report to moderator
1534383785
Hero Member
*
Offline Offline

Posts: 1534383785

View Profile Personal Message (Offline)

Ignore
1534383785
Reply with quote  #2

1534383785
Report to moderator
BOUNTY PORTALS
BLOG
WHERE BOUNTY MANAGEMENT
MEETS AUTOMATION
SIGNATURE CAMPAIGNS
TWITTER
FACEBOOK
MEDIA CAMPAIGNS
AND MORE!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1534383785
Hero Member
*
Offline Offline

Posts: 1534383785

View Profile Personal Message (Offline)

Ignore
1534383785
Reply with quote  #2

1534383785
Report to moderator
amaclin
Legendary
*
Offline Offline

Activity: 1260
Merit: 1000


View Profile
September 01, 2015, 08:05:30 PM
 #22

What's the correct understanding of "valid" here?
Valid = the redeem transaction can be included in blockchain
But.
It is impossible to create such scriptSig, because OP_RETURN in scripPubkey will always fail the execution.
So, this is provable unspendable output.

https://en.bitcoin.it/wiki/Script#Provably_Unspendable.2FPrunable_Outputs
tspacepilot
Legendary
*
Offline Offline

Activity: 1456
Merit: 1013


I may write code in exchange for bitcoins.


View Profile
September 01, 2015, 08:55:48 PM
 #23

What's the correct understanding of "valid" here?
Valid = the redeem transaction can be included in blockchain
But.
It is impossible to create such scriptSig, because OP_RETURN in scripPubkey will always fail the execution.
So, this is provable unspendable output.

https://en.bitcoin.it/wiki/Script#Provably_Unspendable.2FPrunable_Outputs

Got it.  And thanks for the pointer to the bottom of that page, I had overlooked that.  I think this also answers OP's question pretty definitively.
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!