Unfortunately, this still doesn't work for me
I'm still getting the same error
This is my masternode.conf
SazMasternode [My onion address]:10743 [My masternode private key] 9a5181bf8dc996bdd8422254d65b8cbbfb3b9647f53bb21c6754ddb56811b4f6 1
What's usually the issue when it is unable to allocate my transaction id to my masternode? My masternode is running in a ubuntu 16.04 linux VPS. Would it help if i recreate a new onion address and a new private key for my masternode? What else can i try?
Thanks.
Your VOUT info is not right. You have 501 sent and may be backwards normally the 500 is at the top where the 0.26xxx is. It needs to be 500 exactly and then pay extra for the TX fee. Also, did you keep the coin in the local wallet or did you send the coins to somewhere else? If you make a new Address and send them From the Local Wallet to the new Address in the Local wallet, the coins have to stay there for the masternode to be valid.
Is this what you see when you decoded RAW TX in the console? If not then post your TX or the Console for the RAW TX. If you are on a windows local wallet you may have problems too. I tested on windows and it locked up until I took out the masternode info.
"vout": [
{
"value": 0.26238329,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 001cf85f9594a8597b71731b0c8320aa37354295 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a914001cf85f9594a8597b71731b0c8320aa3735429588ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"K7Dk1mmNDNmgPyqM8SMf4XpPc4cpwuCEiw"
]
}
},
{
"value": 501,
"n": 1,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 af5d2cbc993876a35f2f703dea10bc6b0c5487cb OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a914af5d2cbc993876a35f2f703dea10bc6b0c5487cb88ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"KPCPBMRPHMByyCXZZjJAW3beKGf5p43pTd"
]
}
}