<page>
<title>How_to_create_and_sign_a_nonstandard_Bitcoin_transaction</title>
<author_name>stjohn_piano</author_name>
<content>


<bold_lines>
Summary
</bold_lines>


Browse to <link>
<type>article</type>
<article_title>Recipe_for_creating_and_signing_a_nonstandard_Bitcoin_transaction_#2</article_title>
<datafeed>edgecase</datafeed>
<datafeed_article_id>172</datafeed_article_id>
<text>Recipe for creating and signing a nonstandard Bitcoin transaction #2</text>
</link> and follow the recipe.

You will need access to various services, which are listed here: <link>
<type>hyperlink</type>
<reference>/pages/transaction_services</reference>
<text>Transaction services</text>
</link>




<bold_lines>
Contents
</bold_lines>


- Summary
- Contents
- Background
- More information




<bold_lines>
Background
</bold_lines>


Edgecase's working definition of a nonstandard transaction:
- It has at least one input and at least one output.
- At least one input or output address is not a standard Pay-To-Public-Key-Hash (P2PKH) address.

Nonstandard Pay-To-Script-Hash (P2SH) addresses begin with the character '3'. Example P2SH address:
The address
<datablock_lines>
328cTqexYnQRbN5Dgs12D89sYiPPvtWVbF
</datablock_lines>

Example nonstandard Bitcoin transaction:
<datablock_lines>
0100000001f492c0c076787d541d0efc55b56a0d6a14f9214075e10ae4d0d98c70843d2cdb000000008b483045022100aadd9eaf24a0f1741c712670ca661081b7e6af0b7d02e22377d5e9dc27a92f2f022005720a2a3c72bd62b819627d4220d8cdeff132a97e61e9a87e33ac88af3749a0014104876224f0d418523de3770a2b5d7ce071932227fbf9f760f788b038edf04d5e6029903f6251a3e13701790982677209703b424411af8ee1cc86b8e992a568a363ffffffff01949204000000000017a9143a1c39fcbfd4a1407deddf47249bbfccb12a74788700000000
</datablock_lines>






<bold_lines>
More information
</bold_lines>


Projects that involved the creation and signing of a nonstandard Bitcoin transaction:

- Browse to the article <link>
<type>article</type>
<article_title>Creating_and_signing_a_standard_raw_Bitcoin_transaction</article_title>
<datafeed>edgecase</datafeed>
<datafeed_article_id>56</datafeed_article_id>
<text>Creating and signing a standard raw Bitcoin transaction</text>
</link>. In this project, a nonstandard transaction was created that transferred bitcoin back from a standard address to a P2SH receiving address at a Bitcoin exchange.

- Browse to the article <link>
<type>article</type>
<article_title>Creating_and_signing_a_standard_raw_Bitcoin_transaction:_Iteration_#2</article_title>
<datafeed>edgecase</datafeed>
<datafeed_article_id>63</datafeed_article_id>
<text>Creating and signing a standard raw Bitcoin transaction: Iteration #2</text>
</link>. In this project, a nonstandard transaction was created that transferred bitcoin back from a standard address to a P2SH receiving address at a Bitcoin exchange.

- Browse to the article <link>
<type>article</type>
<article_title>Using_a_transaction_to_validate_a_Bitcoin_address</article_title>
<datafeed>edgecase</datafeed>
<datafeed_article_id>66</datafeed_article_id>
<text>Using a transaction to validate a Bitcoin address</text>
</link>. In this project, a nonstandard transaction was created that transferred bitcoin back from a standard address to a P2SH receiving address at a Bitcoin exchange.

- Browse to the article <link>
<type>article</type>
<article_title>Storing_bitcoin_on_an_offline_Raspberry_Pi</article_title>
<datafeed>edgecase</datafeed>
<datafeed_article_id>75</datafeed_article_id>
<text>Storing bitcoin on an offline Raspberry Pi</text>
</link>. In this project, four nonstandard transactions were created that transferred bitcoin back from a standard address to a P2SH receiving address at a Bitcoin exchange. Two of these transactions were mined. Of the remaining two, one had a low fee and the other was a double-spend attempt.








</content>
</page>
