Topic: [MOJO] MOJOv3 has been taken over by new devs - page 18. (Read 167311 times)
I cant find anywhere but there was an ico period right? how much have been raised then?
there will be a testnet ? maybe the community can help you if needed 
Just a quick update!
I know that there have been a lot of issues over the last few weeks and running on this code base there seems to be more issues on the horizon. I am discussing with Limxdev the best way to get onto a new and stable code base. The priority now will be a stable code base so it's possible to plan for other aspects of the development. There will be an update re. the next step and V3 in the next 1-2 weeks and a final decision as to what we do.
I understand that you are inpatient and fed up with all the issues. There will be a V3 and there will be focus on getting a stable system that we can work with.
I know that there have been a lot of issues over the last few weeks and running on this code base there seems to be more issues on the horizon. I am discussing with Limxdev the best way to get onto a new and stable code base. The priority now will be a stable code base so it's possible to plan for other aspects of the development. There will be an update re. the next step and V3 in the next 1-2 weeks and a final decision as to what we do.
I understand that you are inpatient and fed up with all the issues. There will be a V3 and there will be focus on getting a stable system that we can work with.
You're scaring me dude 
The nodes are:
45.63.43.114
45.32.234.45
45.63.43.114
45.32.234.45
I know that it is nodes why there is a following (why wallet tries to be connected to them?):
2016-11-15 10:47:14 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:14 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:26 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:26 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:33 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:33 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:34 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:34 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:40 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:40 ProcessMessage(version, 101 bytes) FAILED
If it
PERMANENT SEED NODES (hardcoded)
mojonode01.mojocoin.org
mojonode02.mojocoin.org
then maybe it's worth remove them from the code?
You can ignored this message. It is only a debug info.
I think there is misunderstanding here.
The real question is: why the hardcoded seednodes are not updated, and are still running old obsolete version?
Why the transaction is not confirmed?
This dev talks the talk, but will fail to deliver. He should have kept Bitz going instead of starting this mojo crap. He had a good following with Bitz but pulled the plug on us just when things were on the up. Leave this project guys, cut your losses, its not worth the time
Thanks for the encouragement, but I am not giving up with this one. We are planning a better code base and we will see what that will be. We are looking for stability so we can move forward with services.
This dev talks the talk, but will fail to deliver. He should have kept Bitz going instead of starting this mojo crap. He had a good following with Bitz but pulled the plug on us just when things were on the up. Leave this project guys, cut your losses, its not worth the time
The nodes are:
45.63.43.114
45.32.234.45
45.63.43.114
45.32.234.45
I know that it is nodes why there is a following (why wallet tries to be connected to them?):
2016-11-15 10:47:14 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:14 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:26 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:26 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:33 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:33 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:34 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:34 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:40 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:40 ProcessMessage(version, 101 bytes) FAILED
If it
PERMANENT SEED NODES (hardcoded)
mojonode01.mojocoin.org
mojonode02.mojocoin.org
then maybe it's worth remove them from the code?
You can ignored this message. It is only a debug info.
The nodes are:
45.63.43.114
45.32.234.45
45.63.43.114
45.32.234.45
I know that it is nodes why there is a following (why wallet tries to be connected to them?):
2016-11-15 10:47:14 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:14 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:26 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:26 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:33 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:33 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:34 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:34 ProcessMessage(version, 101 bytes) FAILED
2016-11-15 10:47:40 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-15 10:47:40 ProcessMessage(version, 101 bytes) FAILED
If it
PERMANENT SEED NODES (hardcoded)
mojonode01.mojocoin.org
mojonode02.mojocoin.org
then maybe it's worth remove them from the code?
The nodes are:
45.63.43.114
45.32.234.45
I'll check the nodes and update
It was succeeded to check?
45.63.43.114
45.32.234.45
getinfo:
"version" : "v2.4.5.0-61402",
"protocolversion" : 90002,
"walletversion" : 60000,
mojocoin.conf:
addnode=128.199.34.210
addnode=130.180.106.26
addnode=194.106.98.24
addnode=222.5.183.201
addnode=46.188.4.74
addnode=73.130.81.250
addnode=81.154.137.240
addnode=85.214.68.75
addnode=91.18.100.227
debug.log:
2016-11-09 09:38:49 UPnP Port Mapping successful.
2016-11-09 09:38:50 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-09 09:38:50 ProcessMessage(version, 101 bytes) FAILED
2016-11-09 09:38:51 socket recv error 10054
2016-11-09 09:39:03 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-09 09:39:03 ProcessMessage(version, 101 bytes) FAILED
"addnode" doesn't work
it tries to be connected only to 45.32.234.45:22255 and 45.63.43.114:22255
45.32.234.45:22255 and 45.63.43.114:22255 - PERMANENT SEED NODES (hardcoded)
?
"version" : "v2.4.5.0-61402",
"protocolversion" : 90002,
"walletversion" : 60000,
mojocoin.conf:
addnode=128.199.34.210
addnode=130.180.106.26
addnode=194.106.98.24
addnode=222.5.183.201
addnode=46.188.4.74
addnode=73.130.81.250
addnode=81.154.137.240
addnode=85.214.68.75
addnode=91.18.100.227
debug.log:
2016-11-09 09:38:49 UPnP Port Mapping successful.
2016-11-09 09:38:50 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-09 09:38:50 ProcessMessage(version, 101 bytes) FAILED
2016-11-09 09:38:51 socket recv error 10054
2016-11-09 09:39:03 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-09 09:39:03 ProcessMessage(version, 101 bytes) FAILED
"addnode" doesn't work
it tries to be connected only to 45.32.234.45:22255 and 45.63.43.114:22255
45.32.234.45:22255 and 45.63.43.114:22255 - PERMANENT SEED NODES (hardcoded)
?I'll check the nodes and update
It was succeeded to check?
getinfo:
"version" : "v2.4.5.0-61402",
"protocolversion" : 90002,
"walletversion" : 60000,
mojocoin.conf:
addnode=128.199.34.210
addnode=130.180.106.26
addnode=194.106.98.24
addnode=222.5.183.201
addnode=46.188.4.74
addnode=73.130.81.250
addnode=81.154.137.240
addnode=85.214.68.75
addnode=91.18.100.227
debug.log:
2016-11-09 09:38:49 UPnP Port Mapping successful.
2016-11-09 09:38:50 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-09 09:38:50 ProcessMessage(version, 101 bytes) FAILED
2016-11-09 09:38:51 socket recv error 10054
2016-11-09 09:39:03 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-09 09:39:03 ProcessMessage(version, 101 bytes) FAILED
"addnode" doesn't work
it tries to be connected only to 45.32.234.45:22255 and 45.63.43.114:22255
45.32.234.45:22255 and 45.63.43.114:22255 - PERMANENT SEED NODES (hardcoded)?
"version" : "v2.4.5.0-61402",
"protocolversion" : 90002,
"walletversion" : 60000,
mojocoin.conf:
addnode=128.199.34.210
addnode=130.180.106.26
addnode=194.106.98.24
addnode=222.5.183.201
addnode=46.188.4.74
addnode=73.130.81.250
addnode=81.154.137.240
addnode=85.214.68.75
addnode=91.18.100.227
debug.log:
2016-11-09 09:38:49 UPnP Port Mapping successful.
2016-11-09 09:38:50 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-09 09:38:50 ProcessMessage(version, 101 bytes) FAILED
2016-11-09 09:38:51 socket recv error 10054
2016-11-09 09:39:03 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-09 09:39:03 ProcessMessage(version, 101 bytes) FAILED
"addnode" doesn't work
it tries to be connected only to 45.32.234.45:22255 and 45.63.43.114:22255
45.32.234.45:22255 and 45.63.43.114:22255 - PERMANENT SEED NODES (hardcoded)
?I'll check the nodes and update
It was succeeded to check?
Zapped, restarted, selected transactions that had 10,000+ confirms via coin control. Now I have to wait and see what happens. How long are people waiting on average to see their transactions get their first confirmation?
Thank you for your debug file. I see you have many wrong nodes in your source (old protocol version). I recommend to delete the peers.dat. I write a new installer with peers.dat replacement.
Okay, i have write a new installer with "peers.dat" replacement. And we a new Mojo version online.
https://github.com/MojocoinV2/mojocoin/releases/tag/v2.4.5.1.0
-stake improvement
What it's about the stake improvement? What is the improvement?
Thanks.
The old qt version had been waiting 1440 blocks (five days(currently eight days)) before begin with staking. The new version begins now in one day.
Ok thanks :-)
Zapped, restarted, selected transactions that had 10,000+ confirms via coin control. Now I have to wait and see what happens. How long are people waiting on average to see their transactions get their first confirmation?
Thank you for your debug file. I see you have many wrong nodes in your source (old protocol version). I recommend to delete the peers.dat. I write a new installer with peers.dat replacement.
Okay, i have write a new installer with "peers.dat" replacement. And we a new Mojo version online.
https://github.com/MojocoinV2/mojocoin/releases/tag/v2.4.5.1.0
-stake improvement
What it's about the stake improvement? What is the improvement?
Thanks.
The old qt version had been waiting 1440 blocks (five days(currently eight days)) before begin with staking. The new version begins now in one day.
Zapped, restarted, selected transactions that had 10,000+ confirms via coin control. Now I have to wait and see what happens. How long are people waiting on average to see their transactions get their first confirmation?
Thank you for your debug file. I see you have many wrong nodes in your source (old protocol version). I recommend to delete the peers.dat. I write a new installer with peers.dat replacement.
Okay, i have write a new installer with "peers.dat" replacement. And we a new Mojo version online.
https://github.com/MojocoinV2/mojocoin/releases/tag/v2.4.5.1.0
-stake improvement
What it's about the stake improvement? What is the improvement?
Thanks.
Even with the newest version, I keep getting:
2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED
Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.
Now let's just wait and see if the transaction eventually broadcasts.
(BTW, what does server=1 do as opposed to server=0?)
Edit: Still no luck broadcasting transactions.
2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED
Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.
Now let's just wait and see if the transaction eventually broadcasts.
(BTW, what does server=1 do as opposed to server=0?)
Edit: Still no luck broadcasting transactions.
I have read your "old" debug.log and you have sent many tx from your masternodes. And you have many masternodes. Hmm....
Well I just created a fresh wallet, and imported two private keys from my previous wallet. Maybe my old wallet was too bloated with all those microtransactions. We'll see what happens. It's been 5 minutes and no confirms yet.
Edit: 10 minutes, no confirms.
I have no problems...try a another pc?
I think this might be the problem, but I have no idea what it means. Found it in debug.log:
2016-11-12 17:47:47 ReacceptWalletTransactions found spent coin 3.10 MOJO 0a7dd87ea2f07b7e68f321f68ad60eee4a3bffc995ee7b0823088e8af8d1408f
Any clue how to fix this?
Even with the newest version, I keep getting:
2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED
Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.
Now let's just wait and see if the transaction eventually broadcasts.
(BTW, what does server=1 do as opposed to server=0?)
Edit: Still no luck broadcasting transactions.
2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED
Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.
Now let's just wait and see if the transaction eventually broadcasts.
(BTW, what does server=1 do as opposed to server=0?)
Edit: Still no luck broadcasting transactions.
I have read your "old" debug.log and you have sent many tx from your masternodes. And you have many masternodes. Hmm....
Well I just created a fresh wallet, and imported two private keys from my previous wallet. Maybe my old wallet was too bloated with all those microtransactions. We'll see what happens. It's been 5 minutes and no confirms yet.
Edit: 10 minutes, no confirms.
I have no problems...try a another pc?
I have other computer - the same problem:
2016-11-12 17:27:14 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 17:27:14 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 17:27:19 socket recv error 10054
2016-11-12 17:27:26 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(bc54da9027, 0), scriptSig=)
2016-11-12 17:28:26 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(bc54da9027, 0), scriptSig=)
2016-11-12 17:29:18 socket recv error 10054
2016-11-12 17:29:27 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(bc54da9027, 0), scriptSig=)
2016-11-12 17:29:51 socket recv error 10054
2016-11-12 17:30:27 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(bc54da9027, 0), scriptSig=)
2016-11-12 17:31:27 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(bc54da9027, 0), scriptSig=)
2016-11-12 17:31:52 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 17:31:52 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 17:32:03 socket recv error 10054
In your conf file, rather than using addnode=, try using connect=
That seemed to stop my wallet from trying to connect to that obsolete IP.
Try replacing all your addnodes in your .conf file with this:
connect=176.9.140.80
connect=184.69.47.154
connect=185.3.34.119
connect=188.170.193.101
connect=192.161.53.47
connect=195.46.241.230
connect=213.136.88.142
connect=213.136.94.226
connect=5.189.136.83
connect=54.167.193.169
connect=64.223.98.232
connect=77.106.70.104
connect=84.200.32.238
connect=92.30.212.215
connect=93.104.209.17
connect=93.75.0.142
connect=95.211.110.151
connect=104.200.151.21
connect=128.199.34.210
connect=194.106.98.24
connect=46.149.43.12
connect=66.11.122.218
connect=73.130.81.250
connect=81.154.137.240
connect=85.214.68.75
connect=92.222.87.172
connect=144.76.71.141
connect=222.5.183.201
connect=24.77.46.60
connect=46.188.4.74
connect=80.31.223.57
connect=104.237.2.192
I just resync'd from scratch. We'll see what happens.
Even with the newest version, I keep getting:
2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED
Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.
Now let's just wait and see if the transaction eventually broadcasts.
(BTW, what does server=1 do as opposed to server=0?)
Edit: Still no luck broadcasting transactions.
2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED
Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.
Now let's just wait and see if the transaction eventually broadcasts.
(BTW, what does server=1 do as opposed to server=0?)
Edit: Still no luck broadcasting transactions.
I have read your "old" debug.log and you have sent many tx from your masternodes. And you have many masternodes. Hmm....
Well I just created a fresh wallet, and imported two private keys from my previous wallet. Maybe my old wallet was too bloated with all those microtransactions. We'll see what happens. It's been 5 minutes and no confirms yet.
Edit: 10 minutes, no confirms.
I have no problems...try a another pc?
I have other computer - the same problem:
2016-11-12 17:27:14 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 17:27:14 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 17:27:19 socket recv error 10054
2016-11-12 17:27:26 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(bc54da9027, 0), scriptSig=)
2016-11-12 17:28:26 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(bc54da9027, 0), scriptSig=)
2016-11-12 17:29:18 socket recv error 10054
2016-11-12 17:29:27 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(bc54da9027, 0), scriptSig=)
2016-11-12 17:29:51 socket recv error 10054
2016-11-12 17:30:27 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(bc54da9027, 0), scriptSig=)
2016-11-12 17:31:27 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(bc54da9027, 0), scriptSig=)
2016-11-12 17:31:52 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 17:31:52 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 17:32:03 socket recv error 10054
Even with the newest version, I keep getting:
2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED
Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.
Now let's just wait and see if the transaction eventually broadcasts.
(BTW, what does server=1 do as opposed to server=0?)
Edit: Still no luck broadcasting transactions.
2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED
Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.
Now let's just wait and see if the transaction eventually broadcasts.
(BTW, what does server=1 do as opposed to server=0?)
Edit: Still no luck broadcasting transactions.
I have read your "old" debug.log and you have sent many tx from your masternodes. And you have many masternodes. Hmm....
Well I just created a fresh wallet, and imported two private keys from my previous wallet. Maybe my old wallet was too bloated with all those microtransactions. We'll see what happens. It's been 5 minutes and no confirms yet.
Edit: 10 minutes, no confirms.
I have no problems...try a another pc?
Even with the newest version, I keep getting:
2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED
Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.
Now let's just wait and see if the transaction eventually broadcasts.
(BTW, what does server=1 do as opposed to server=0?)
Edit: Still no luck broadcasting transactions.
2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED
Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.
Now let's just wait and see if the transaction eventually broadcasts.
(BTW, what does server=1 do as opposed to server=0?)
Edit: Still no luck broadcasting transactions.
I have read your "old" debug.log and you have sent many tx from your masternodes. And you have many masternodes. Hmm....
Well I just created a fresh wallet, and imported two private keys from my previous wallet. Maybe my old wallet was too bloated with all those microtransactions. We'll see what happens. It's been 5 minutes and no confirms yet.
Edit: 10 minutes, no confirms.
Jump to: