Assemble a set of nonstandard Bitcoin transactions, including the private keys, for use in future tests of Bitcoin software. These transactions must have already been added to the Bitcoin blockchain.







- Goal
- Contents
- Summary
- Notes
- Bitcoin Nonstandard Transaction Test Set







I have collected 8 nonstandard transactions.

Actions:
- Read through previous articles. Record any nonstandard Bitcoin transactions. Record the input addresses corresponding to the input private keys. Record the onchain txid of the transaction.
- Generate the addresses from the input private keys. Confirm that the new addresses are identical to the original ones.
- Construct the transactions from the input data values. Confirm that the new transactions are identical to the original ones.

To generate the addresses, I used the recipe and assets from this article:
Recipe for generating a Bitcoin address

To construct the transactions, I used the assets listed in the Downloadable Assets section of this article:
Creating a Bitcoin transaction with two outputs
and I used the recipe from this article:
Recipe for creating and signing a nonstandard Bitcoin transaction







My working definition of a standard transaction:
- It has at least one input and at least one output.
- All input and output addresses are Pay-To-Public-Key-Hash (P2PKH).
- All input scriptSigs contain uncompressed public keys.

Pay-To-Public-Key-Hash (P2PKH) addresses start with the character '1'.
Example: The address

begins with a '1' and is therefore a P2PKH address.

My 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.

Example of a nonstandard address:
- A Pay-To-Script-Hash (P2SH) address.

Pay-To-Script-Hash (P2SH) addresses begin with the character '3'.
Example: The address

begins with a '3' and is therefore a P2SH address.

Per the article Bitcoin transaction test set, the following pieces of information are the necessary input and output components for a standard Bitcoin transaction:

1) For each input:
- The txid of the previous transaction that transferred the unspent output to the input address. When its byte order is reversed, it becomes the "previous_output_hash".
- The index of this unspent output in the previous transaction (the "previous_output_index"). This index is implicit and starts at zero, and can be found by examining the list of outputs in the previous transaction, and looking for the particular unspent output that you wish to transfer.
- The private key (in hex bytes) of the input address.
- The bitcoin amount (or satoshi amount) contained within the unspent output. Let's call this the "input amount".
- A 32-byte random value (1 per input). The transaction will be signed once using each input and each signature requires 32 bytes of entropy.

2) For each output:
- The output address.
- The bitcoin amount (or satoshi amount) that you wish to transfer to the output address. Let's call this the "output amount".

3) For the whole transaction:
- The fee (in satoshi). The fee must be an integer e.g. .

Additionally:
- For each input, I have recorded the "input address" that corresponds to the input private key.
- For each transaction, I have recorded the "change address" setting.

For some transactions, in the source article, the hash type (4 bytes, ) was erroneously appended to the final signed form of the transaction. This has been noted in each case. For further details, see the Bitcoin Transaction Toolset Hash Type Problem section of the article Creating a Bitcoin transaction with two outputs.





















Source: Creating and signing a standard raw Bitcoin transaction


Transaction name: "transaction 2"



Signed transaction:


Onchain txid:


Note: A little work was required to change the original random value in raw bytes:

into a 32-byte hex value.










Source: Creating and signing a standard raw Bitcoin transaction: Iteration #2

Transaction name: "tx2"



Signed transaction:


Onchain txid:


Notes:
- A little work was required to change the original random value in raw bytes:

into a 32-byte hex value.
- In the source article, the hash type (4 bytes, ) was erroneously appended to the final signed form of the transaction.










Source: Using a transaction to validate a Bitcoin address


Transaction name: "tx1"



Signed transaction:


Onchain txid:


Note: In the source article, the hash type (4 bytes, ) was erroneously appended to the final signed form of the transaction.










Source: Storing bitcoin on an offline Raspberry Pi


Transaction name: "tx1c"



Signed transaction:


Onchain txid:


Note: In the source article, the hash type (4 bytes, ) was erroneously appended to the final signed form of the transaction.




Transaction name: "tx3"



Signed transaction:


Onchain txid:


Note: In the source article, the hash type (4 bytes, ) was erroneously appended to the final signed form of the transaction.










Source: Creating a Bitcoin transaction with two outputs


Transaction name: "tx_2b"



Signed transaction:


Onchain txid:





Transaction name: "tx_3"



Signed transaction:


Onchain txid:











Source: Creating a Bitcoin transaction with two inputs


Transaction name: "tx3"



Signed transaction:


Onchain txid: