https://github.com/tynes/tx-debugger

Transaction Debugger
https://github.com/tynes/tx-debugger

Last synced: 9 days ago
JSON representation

Transaction Debugger

• Host: GitHub
• URL: https://github.com/tynes/tx-debugger
• Owner: tynes
• Created: 2018-02-24T22:04:14.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2015-04-29T04:27:48.000Z (over 9 years ago)
• Last Synced: 2024-11-06T18:01:09.444Z (about 2 months ago)
• Language: JavaScript
• Size: 125 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
tx-debugger

===========

Is your bitcoin wallet software producing a transaction which is being rejected

from the network, and you don't know why? Are you submitting it to bitcoind and

getting "Error Code -22" and wondering what the hell that means? tx-debugger

can help you debug your transaction. It will parse your transaction, retrieve

the inputs automatically using the BitGo API, run a script interpreter on the

inputs, and finally run the equivalent of bitcoind's CheckTransction method.

tx-debugger will tell you where it encountered an error. If your transaction

passes all the tests, then it is valid. A valid transaction may be rejected by

the network if a double-spend transaction also appears in the blockchain - so

if your transaction is valid, and still doesn't broadcast, it may be because of

a double-spend.

Try this example of using tx-debugger with a real transaction:

```

./bin/tx-debugger.js 0100000001795b88d47a74e3be0948fc9d1b4737f96097474d57151afa6f77c787961e47cc120000006a47304402202289f9e1ae2ed981cd0bf62f822f6ae4aea40c65c7339d90643cea90de93ad1502205c8a08b3265f9ba7e99057d030d5b91c889a1b99f94a3a5b79d7daaada2409b6012103798b51f980e7a3690af6b43ce3467db75bede190385702c4d9d48c0a735ff4a9ffffffff01c0a83200000000001976a91447b8e62e008f82d95d1f565055a8243cc243d32388ac00000000

```

Output:

```

Transaction parsed successfully. Gathering inputs.

Gathered input 0 of id cc471e9687c7776ffa1a15574d479760f937471b9dfc4809bee3747ad4885b79

Found input 0 on mainnet

Script interpreter result for input 0: success

Check transaction (script interpreter plus other validations): success

```

Suppose you had gotten the input hashes in reverse, a very common mistake:

```

./bin/tx-debugger.js 0100000001cc471e9687c7776ffa1a15574d479760f937471b9dfc4809bee3747ad4885b79120000006a47304402202289f9e1ae2ed981cd0bf62f822f6ae4aea40c65c7339d90643cea90de93ad1502205c8a08b3265f9ba7e99057d030d5b91c889a1b99f94a3a5b79d7daaada2409b6012103798b51f980e7a3690af6b43ce3467db75bede190385702c4d9d48c0a735ff4a9ffffffff01c0a83200000000001976a91447b8e62e008f82d95d1f565055a8243cc243d32388ac00000000

```

Output:

```

Transaction parsed successfully. Gathering inputs.

Gathered input 0 of id cc471e9687c7776ffa1a15574d479760f937471b9dfc4809bee3747ad4885b79

Found input 0 on mainnet

Error: Input 0 had a reversed hash. Must reverse hash to validate.

Proceeding with additional checks in spite of invalid hash.

Script interpreter result for input 0: success

Check transaction (script interpreter plus other validations): success

```

tx-debugger will automatically determine whether your transaction is on mainnet

or testnet by trying to find it first on the mainnet blockchain and then on the

testnet blockchain. Here's an example of a real testnet transaction:

```

./bin/tx-debugger.js 0100000002e0ea20bcae15a3d63d54cdafc92fea4923f7929e3ea36191522cac87c9fb9356010000006a47304402204a509176ec9634879f5487519b0fbf143936da3d94b887027a9b79182569c79f02206dad3fd761902c1585d6fab841e99aea1dbec735f4e20d4142b1f32cbd1113e701210261bf95c276fdda74106b93d4f3c4923134eccb380b598ddb6cdb7f798a4fdccfffffffffe799ebe4c2e62529195cff4f646faecd49d81ab41a2cd7bf54ba9b481a7b9bdc000000006b483045022100e39bb72c458eefdad89e7040359c12dd90b725a4d525100e1af294efc4e50544022047292abfd2d778fa8f7038c2238bd9c6376a34d65aaccaa860d459c30f5effc1012103301f9cd833888f5e5e7f1d15c5d8181a6c97f481f99b234ab5fca2bc4809a189ffffffff02f2121d860000000017a914805fd258cd7c8cf8249339fb01ed19fb7533ecce87c3295001000000001976a914522fef9fbe6df4d90ad8140d92a418dfbb57a34688ac00000000

```

Output:

```

Transaction parsed successfully. Gathering inputs.

Gathered input 1 of id dc9b7b1a489bba54bfd72c1ab41ad849cdae6f644fff5c192925e6c2e4eb99e7

Found input 1 on testnet

Gathered input 0 of id 5693fbc987ac2c529161a33e9e92f72349ea2fc9afcd543dd6a315aebc20eae0

Found input 0 on testnet

Script interpreter result for input 0: success

Script interpreter result for input 1: success

Check transaction (script interpreter plus other validations): success

```