$100 available to assist with transaction ID problem

Steve Sokolowski · Feb 19, 2017

Hi,

We're in the final stages of implementing X11 mining in our system, which will allow us to mine and pay out in DASH. Unfortunately, we're run into a problem where the transaction IDs the DASH client is generating don't match the ones our software is generating, and 70 hours of investigation has yet to reveal a solution.

Unfortunately, I can't post a link here, since it states that you need to have 3 posts in order to do so. A full description of the problem and how to claim payment for anyone who might know the answer is available in the "development" section of the Prohashing forums, which can be found by searching on Google.

Thanks for anyone who can help!

Updated: the issue has been resolved. No further help is needed and the reward has been claimed.

nmarley · Feb 19, 2017

Steve Sokolowski said:
Hi,

We're in the final stages of implementing X11 mining in our system, which will allow us to mine and pay out in DASH. Unfortunately, we're run into a problem where the transaction IDs the DASH client is generating don't match the ones our software is generating, and 70 hours of investigation has yet to reveal a solution.

Unfortunately, I can't post a link here, since it states that you need to have 3 posts in order to do so. A full description of the problem and how to claim payment for anyone who might know the answer is available in the "development" section of the Prohashing forums, which can be found by searching on Google.

Thanks for anyone who can help!

Link to Steve's issue: https://forums.prohashing.com/viewtopic.php?f=7&t=1083

chaeplin · Feb 19, 2017

wrong answer, deleted.

UdjinM6 · Feb 19, 2017

Hello and welcome

Your tx hex data looks weird, should be no "0a50726f68617368696e67" at the end

Code:

02000000 // version
// vin
01 //vin count
// prevout
0000000000000000000000000000000000000000000000000000000000000000
ffffffff
//scriptSig
1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f
// nSequence
00000000
// vout
02 // vout count
//value
40230e4300000000
// scriptPubKey
19
76a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac
// value
40230e4300000000
// scriptPubKey
19
76a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac
// nlocktime
00000000
// ????
0a50726f68617368696e67

Remove the unknown data and you get this

Code:

> dsha256 02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f000000000240230e43000000001976a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac40230e43000000001976a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac00000000
e24ce540e231bdf22d5f9549163d8c228f7054c7c482e8fbffc782350a768d2c
> hashrev e24ce540e231bdf22d5f9549163d8c228f7054c7c482e8fbffc782350a768d2c
2c8d760a3582c7fffbe882c4c754708f228c3d1649955f2df2bd31e240e54ce2

Code:

decoderawtransaction 02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f000000000240230e43000000001976a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac40230e43000000001976a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac00000000
{
  "txid": "2c8d760a3582c7fffbe882c4c754708f228c3d1649955f2df2bd31e240e54ce2",
  "size": 150,
  "version": 2,
  "locktime": 0,
  "vin": [
    {
      "coinbase": "030660020425c4a95808980000017e0000000c2f364d55394439514652522f",
      "sequence": 0
    }
  ],
  "vout": [
    {
      "value": 11.25000000,
      "valueSat": 1125000000,
      "n": 0,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 2fe1230bd7859268277431bd2c15d1d92bc6b45f OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yQgcK1FPvgUi2KCXMX1pq4FzQyJXXcwuiy"
        ]
      }
    },
    {
      "value": 11.25000000,
      "valueSat": 1125000000,
      "n": 1,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 8f95e6fae491957622ed7fc8021d01e48d7188fb OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yZQf42WWTxzJvawMagJScUnjx2gW7nerBq"
        ]
      }
    }
  ]
}

And now dsha matches expected txid. Have fun!

Steve Sokolowski · Feb 20, 2017

UdjinM6 said:

Hello and welcome

Your tx hex data looks weird, should be no "0a50726f68617368696e67" at the end

Code:

02000000 // version
// vin
01 //vin count
// prevout
0000000000000000000000000000000000000000000000000000000000000000
ffffffff
//scriptSig
1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f
// nSequence
00000000
// vout
02 // vout count
//value
40230e4300000000
// scriptPubKey
19
76a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac
// value
40230e4300000000
// scriptPubKey
19
76a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac
// nlocktime
00000000
// ????
0a50726f68617368696e67

Remove the unknown data and you get this

Code:

> dsha256 02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f000000000240230e43000000001976a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac40230e43000000001976a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac00000000
e24ce540e231bdf22d5f9549163d8c228f7054c7c482e8fbffc782350a768d2c
> hashrev e24ce540e231bdf22d5f9549163d8c228f7054c7c482e8fbffc782350a768d2c
2c8d760a3582c7fffbe882c4c754708f228c3d1649955f2df2bd31e240e54ce2

Code:

decoderawtransaction 02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f000000000240230e43000000001976a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac40230e43000000001976a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac00000000
{
  "txid": "2c8d760a3582c7fffbe882c4c754708f228c3d1649955f2df2bd31e240e54ce2",
  "size": 150,
  "version": 2,
  "locktime": 0,
  "vin": [
    {
      "coinbase": "030660020425c4a95808980000017e0000000c2f364d55394439514652522f",
      "sequence": 0
    }
  ],
  "vout": [
    {
      "value": 11.25000000,
      "valueSat": 1125000000,
      "n": 0,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 2fe1230bd7859268277431bd2c15d1d92bc6b45f OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yQgcK1FPvgUi2KCXMX1pq4FzQyJXXcwuiy"
        ]
      }
    },
    {
      "value": 11.25000000,
      "valueSat": 1125000000,
      "n": 1,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 8f95e6fae491957622ed7fc8021d01e48d7188fb OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yZQf42WWTxzJvawMagJScUnjx2gW7nerBq"
        ]
      }
    }
  ]
}

And now dsha matches expected txid. Have fun!

Wow, that was fast! I spent days on this and thought I might be stuck for another two weekends. This may be the best money I've ever spent.

I need to go to sleep right now, but when I get up in about eight hours, I'll try this out and make sure you get paid once I get the server working. Talk to you tomorrow!

Steve Sokolowski · Feb 20, 2017

UdjinM6 said:

Hello and welcome

Your tx hex data looks weird, should be no "0a50726f68617368696e67" at the end

Code:

02000000 // version
// vin
01 //vin count
// prevout
0000000000000000000000000000000000000000000000000000000000000000
ffffffff
//scriptSig
1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f
// nSequence
00000000
// vout
02 // vout count
//value
40230e4300000000
// scriptPubKey
19
76a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac
// value
40230e4300000000
// scriptPubKey
19
76a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac
// nlocktime
00000000
// ????
0a50726f68617368696e67

Remove the unknown data and you get this

Code:

> dsha256 02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f000000000240230e43000000001976a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac40230e43000000001976a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac00000000
e24ce540e231bdf22d5f9549163d8c228f7054c7c482e8fbffc782350a768d2c
> hashrev e24ce540e231bdf22d5f9549163d8c228f7054c7c482e8fbffc782350a768d2c
2c8d760a3582c7fffbe882c4c754708f228c3d1649955f2df2bd31e240e54ce2

Code:

decoderawtransaction 02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f000000000240230e43000000001976a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac40230e43000000001976a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac00000000
{
  "txid": "2c8d760a3582c7fffbe882c4c754708f228c3d1649955f2df2bd31e240e54ce2",
  "size": 150,
  "version": 2,
  "locktime": 0,
  "vin": [
    {
      "coinbase": "030660020425c4a95808980000017e0000000c2f364d55394439514652522f",
      "sequence": 0
    }
  ],
  "vout": [
    {
      "value": 11.25000000,
      "valueSat": 1125000000,
      "n": 0,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 2fe1230bd7859268277431bd2c15d1d92bc6b45f OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yQgcK1FPvgUi2KCXMX1pq4FzQyJXXcwuiy"
        ]
      }
    },
    {
      "value": 11.25000000,
      "valueSat": 1125000000,
      "n": 1,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 8f95e6fae491957622ed7fc8021d01e48d7188fb OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yZQf42WWTxzJvawMagJScUnjx2gW7nerBq"
        ]
      }
    }
  ]
}

And now dsha matches expected txid. Have fun!

Thanks! This is the correct answer, and I resolved the issue.

I posted what caused this problem in the linked thread, thanked everyone for their help, and described how you can get paid for your work. I also made a suggestion as to how DASH can be improved to prevent this from happening in the future.

This is amazing service here.

Steve Sokolowski · Feb 21, 2017

UdjinM6 said:

Hello and welcome

Your tx hex data looks weird, should be no "0a50726f68617368696e67" at the end

Code:

02000000 // version
// vin
01 //vin count
// prevout
0000000000000000000000000000000000000000000000000000000000000000
ffffffff
//scriptSig
1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f
// nSequence
00000000
// vout
02 // vout count
//value
40230e4300000000
// scriptPubKey
19
76a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac
// value
40230e4300000000
// scriptPubKey
19
76a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac
// nlocktime
00000000
// ????
0a50726f68617368696e67

Remove the unknown data and you get this

Code:

> dsha256 02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f000000000240230e43000000001976a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac40230e43000000001976a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac00000000
e24ce540e231bdf22d5f9549163d8c228f7054c7c482e8fbffc782350a768d2c
> hashrev e24ce540e231bdf22d5f9549163d8c228f7054c7c482e8fbffc782350a768d2c
2c8d760a3582c7fffbe882c4c754708f228c3d1649955f2df2bd31e240e54ce2

Code:

decoderawtransaction 02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff1f030660020425c4a95808980000017e0000000c2f364d55394439514652522f000000000240230e43000000001976a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac40230e43000000001976a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac00000000
{
  "txid": "2c8d760a3582c7fffbe882c4c754708f228c3d1649955f2df2bd31e240e54ce2",
  "size": 150,
  "version": 2,
  "locktime": 0,
  "vin": [
    {
      "coinbase": "030660020425c4a95808980000017e0000000c2f364d55394439514652522f",
      "sequence": 0
    }
  ],
  "vout": [
    {
      "value": 11.25000000,
      "valueSat": 1125000000,
      "n": 0,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 2fe1230bd7859268277431bd2c15d1d92bc6b45f OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9142fe1230bd7859268277431bd2c15d1d92bc6b45f88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yQgcK1FPvgUi2KCXMX1pq4FzQyJXXcwuiy"
        ]
      }
    },
    {
      "value": 11.25000000,
      "valueSat": 1125000000,
      "n": 1,
      "scriptPubKey": {
        "asm": "OP_DUP OP_HASH160 8f95e6fae491957622ed7fc8021d01e48d7188fb OP_EQUALVERIFY OP_CHECKSIG",
        "hex": "76a9148f95e6fae491957622ed7fc8021d01e48d7188fb88ac",
        "reqSigs": 1,
        "type": "pubkeyhash",
        "addresses": [
          "yZQf42WWTxzJvawMagJScUnjx2gW7nerBq"
        ]
      }
    }
  ]
}

And now dsha matches expected txid. Have fun!

Payment was made in this transaction: https://prohashing.com/explorer/Das...1eecca93feebb34fe3d7d1e91c409c1b393eeff243393.

UdjinM6 · Feb 21, 2017

Steve Sokolowski said:
Payment was made in this transaction: https://prohashing.com/explorer/Das...1eecca93feebb34fe3d7d1e91c409c1b393eeff243393.

Thanks!

PS. nice explorer you have there, $price + historical $price.. interesting!

$100 available to assist with transaction ID problem

Steve Sokolowski

New member

nmarley

Administrator

chaeplin

Well-known member

UdjinM6

Official Dash Dev

Steve Sokolowski

New member

Steve Sokolowski

New member

Steve Sokolowski

New member

UdjinM6

Official Dash Dev