bad-tx-type (code 16) (code-1) need help with pool

Status
Not open for further replies.

Dollebrekel

New Member
Jun 27, 2019
7
0
1
35
I forked dash 0.14
The blockchain is up and running. I can connect miners on the blockchain and I have my own miningpool (NOMP software)
I can connect the miners to the pool and it works flawless.

Right now I want to get a masternode running. I did every step. The last step where I need to submit my signed message (protx register_submit tx sig) I recieve the next error "bad-tx-type (code16) (code)"

I tried to find a solution on the internet. What I have seen that DIP3 needs to be activated with spork 15.
This is my outcome with blockchaininfo and spork active
},
"dip0003": {
"status": "started",
"bit": 3,
"period": 4032,
"threshold": 3226,
"windowStart": 4032,
"windowBlocks": 879,
"windowProgress": 0.2724736515809051,
"startTime": 1546300800,
"timeout": 1577836800,
"since": 4032
},
{
"SPORK_2_INSTANTSEND_ENABLED": true,
"SPORK_3_INSTANTSEND_BLOCK_FILTERING": true,
"SPORK_5_INSTANTSEND_MAX_VALUE": true,
"SPORK_6_NEW_SIGS": false,
"SPORK_9_SUPERBLOCKS_ENABLED": false,
"SPORK_12_RECONSIDER_BLOCKS": true,
"SPORK_15_DETERMINISTIC_MNS_ENABLED": false,
"SPORK_16_INSTANTSEND_AUTOLOCKS": false,
"SPORK_17_QUORUM_DKG_ENABLED": false,
"SPORK_19_CHAINLOCKS_ENABLED": false,
"SPORK_20_INSTANTSEND_LLMQ_BASED": false
}

Has anyone a solution how I can fix this with NOMP pool software or anything else to solve the "bad-tx-type (code16) (code)" issue?
 

nmarley

Administrator
Dash Core Team
Moderator
Jun 28, 2014
366
424
133
Seems like your sporks aren't being synced. Are you connecting to valid 0.14.0 nodes?

This is what I see for spork active:

Code:
{
  "SPORK_2_INSTANTSEND_ENABLED": true,
  "SPORK_3_INSTANTSEND_BLOCK_FILTERING": true,
  "SPORK_5_INSTANTSEND_MAX_VALUE": true,
  "SPORK_6_NEW_SIGS": false,
  "SPORK_9_SUPERBLOCKS_ENABLED": true,
  "SPORK_12_RECONSIDER_BLOCKS": true,
  "SPORK_15_DETERMINISTIC_MNS_ENABLED": true,
  "SPORK_16_INSTANTSEND_AUTOLOCKS": true,
  "SPORK_17_QUORUM_DKG_ENABLED": true,
  "SPORK_19_CHAINLOCKS_ENABLED": false,
  "SPORK_20_INSTANTSEND_LLMQ_BASED": false
}
Edit: Sorry, didn't realize you were trying to create a fork of Dash. In that case, please disregard, as I'm not sure what they should be for your fork.
 

Dollebrekel

New Member
Jun 27, 2019
7
0
1
35
@mmarley, Yes it should be. I just create an own coin forked from Dash. And I used the latest version.
 

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,902
6,734
1,283
@mmarley, Yes it should be. I just create an own coin forked from Dash. And I used the latest version.
forking/ copying sounds easier than it is ey ;)
 

Dollebrekel

New Member
Jun 27, 2019
7
0
1
35
forking/ copying sounds easier than it is ey ;)
Yeah it is not that hard. Everything works like a charm. Except for the issue I face right now. I also tried to get support from the pool software creator. But I guess he is not active anymore.

But I think it is not the Dash repo but the pool repo
 

nmarley

Administrator
Dash Core Team
Moderator
Jun 28, 2014
366
424
133
@mmarley, Yes it should be. I just create an own coin forked from Dash. And I used the latest version.
Forks are harder because we move so quickly (with updating our codebase). You probably want to start with your Spork 15 defaulted to the Dash value (which is actually a block height, not just binary).

Here are the current Dash spork values:

Code:
{
  "SPORK_2_INSTANTSEND_ENABLED": 0,
  "SPORK_3_INSTANTSEND_BLOCK_FILTERING": 0,
  "SPORK_5_INSTANTSEND_MAX_VALUE": 2000,
  "SPORK_6_NEW_SIGS": 4000000000,
  "SPORK_9_SUPERBLOCKS_ENABLED": 0,
  "SPORK_12_RECONSIDER_BLOCKS": 0,
  "SPORK_15_DETERMINISTIC_MNS_ENABLED": 1047200,
  "SPORK_16_INSTANTSEND_AUTOLOCKS": 0,
  "SPORK_17_QUORUM_DKG_ENABLED": 0,
  "SPORK_19_CHAINLOCKS_ENABLED": 4070908800,
  "SPORK_20_INSTANTSEND_LLMQ_BASED": 4070908800
}
 

Dollebrekel

New Member
Jun 27, 2019
7
0
1
35
Forks are harder because we move so quickly (with updating our codebase). You probably want to start with your Spork 15 defaulted to the Dash value (which is actually a block height, not just binary).

Here are the current Dash spork values:

Code:
{
  "SPORK_2_INSTANTSEND_ENABLED": 0,
  "SPORK_3_INSTANTSEND_BLOCK_FILTERING": 0,
  "SPORK_5_INSTANTSEND_MAX_VALUE": 2000,
  "SPORK_6_NEW_SIGS": 4000000000,
  "SPORK_9_SUPERBLOCKS_ENABLED": 0,
  "SPORK_12_RECONSIDER_BLOCKS": 0,
  "SPORK_15_DETERMINISTIC_MNS_ENABLED": 1047200,
  "SPORK_16_INSTANTSEND_AUTOLOCKS": 0,
  "SPORK_17_QUORUM_DKG_ENABLED": 0,
  "SPORK_19_CHAINLOCKS_ENABLED": 4070908800,
  "SPORK_20_INSTANTSEND_LLMQ_BASED": 4070908800
}
Thanks for the reply. I will take a look if I can solve the problem. I will let you know.
 

Dollebrekel

New Member
Jun 27, 2019
7
0
1
35
The spork is active right now. But the bad-tx-type (code16) (code) still remains. See here my outputs;


masternode status
{
"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
"service": "[::]:0",
"state": "WAITING_FOR_PROTX",
"status": "Waiting for ProTx to appear on-chain"
}

getblockchaininfo
{
"chain": "main",
"blocks": 8441,
"headers": 8441,
"bestblockhash": "000000000000592985db427843a46947782e924b0b81b1f30ae4d90ac90ad51e",
"difficulty": 70905.72805916925,
"mediantime": 1561977519,
"verificationprogress": 1,
"chainwork": "0000000000000000000000000000000000000000000000000d12a6003c218f42",
"pruned": false,
"softforks": [
{
"id": "bip34",
"version": 2,
"reject": {
"status": true
}
},
{
"id": "bip66",
"version": 3,
"reject": {
"status": true
}
},
{
"id": "bip65",
"version": 4,
"reject": {
"status": true
}
}
],
"bip9_softforks": {
"csv": {
"status": "active",
"startTime": 1486252800,
"timeout": 9999999999,
"since": 15
},
"dip0001": {
"status": "active",
"startTime": 1508025600,
"timeout": 9999999999,
"since": 15
},
"dip0003": {
"status": "locked_in",
"startTime": 1546300800,
"timeout": 1577836800,
"since": 8064
},
"dip0008": {
"status": "locked_in",
"startTime": 1557878400,
"timeout": 1589500800,
"since": 8064
},
"bip147": {
"status": "active",
"startTime": 1524477600,
"timeout": 9999999999,
"since": 15
}
}
}


spork active
{
"SPORK_2_INSTANTSEND_ENABLED": true,
"SPORK_3_INSTANTSEND_BLOCK_FILTERING": true,
"SPORK_5_INSTANTSEND_MAX_VALUE": true,
"SPORK_6_NEW_SIGS": false,
"SPORK_9_SUPERBLOCKS_ENABLED": false,
"SPORK_12_RECONSIDER_BLOCKS": true,
"SPORK_15_DETERMINISTIC_MNS_ENABLED": true,
"SPORK_16_INSTANTSEND_AUTOLOCKS": false,
"SPORK_17_QUORUM_DKG_ENABLED": false,
"SPORK_19_CHAINLOCKS_ENABLED": false,
"SPORK_20_INSTANTSEND_LLMQ_BASED": false
}

getblocktemplate
{
"capabilities": [
"proposal"
],
"version": 536870936,
"rules": [
"csv",
"dip0001",
"bip147"
],
"vbavailable": {
"dip0003": 3,
"dip0008": 4
},
"vbrequired": 0,
"previousblockhash": "000000000000592985db427843a46947782e924b0b81b1f30ae4d90ac90ad51e",
"transactions": [
],
"coinbaseaux": {
"flags": ""
},
"coinbasevalue": 5000000000,
"longpollid": "000000000000592985db427843a46947782e924b0b81b1f30ae4d90ac90ad51e19",
"target": "000000000000d9f5000000000000000000000000000000000000000000000000",
"mintime": 1561977520,
"mutable": [
"time",
"transactions",
"prevblock"
],
"noncerange": "00000000ffffffff",
"sigoplimit": 40000,
"sizelimit": 2000000,
"curtime": 1561978258,
"bits": "1b00d9f5",
"previousbits": "1b00ec9c",
"height": 8442,
"masternode": [
],
"masternode_payments_started": true,
"masternode_payments_enforced": true,
"superblock": [
],
"superblocks_started": false,
"superblocks_enabled": false,
"coinbase_payload": ""
}
 

OmarBaruzzo

New Member
May 19, 2020
1
0
1
44
Hi, I saw that in this topic you had a "bad transactions" problem while synchronizing the masternodes of a fork of the Dash. I have the same problem, can you suggest me how you solved it? What did you change in the code? I would be grateful. Thank you, Omar
 
Status
Not open for further replies.