V12 Testing Thread

v0.12.0.11

This will allow me to reset the budget, it also includes various improvements that should stop the excessive CPU use for nodes that are just turning on, as well as many other improvements.

*** Please delete mnbudget.dat and budget.dat before restarting the client! Thanks***

Evan Duffield:
-version/proto bump
- added spork for reseting budget
- Fixed invalid saved budget.dat issue
- Fix active removal of proposals
- fixed compile error

Udjin:
- use proper naming for variables in masternode-budget
- use spork dependent logic to get the right minimal proto everywhere M… …
- introduce RelayInv
- small fixes
- (Yet) another attempt to get progress displayed right
- Fix GetInputDarksendRounds: …
- Implement safer version of CWallet::prepareDarksendDenominate: …
- Stop banning nodes for unknown masternodes while processing budget me… …

Crowning:
- satoshi(s) -> duff(s) in locales
- Fixed warning QLabel(0xb0049b8, name = "labelCoinControlChangeLabel")… …


Linux32:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux32.tar.gz

Linux64:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux64.tar.gz

Mac:
https://dashpay.atlassian.net/build...n-osx-dash-dist//dash-0.12.0-osx-unsigned.dmg

Win32:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win32.zip

Win64:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win64.zip
 
eduffield said:
v0.12.0.11

This will allow me to reset the budget, it also includes various improvements that should stop the excessive CPU use for nodes that are just turning on, as well as many other improvements.

*** Please delete mnbudget.dat and budget.dat before restarting the client! Thanks***
Click to expand...

I didn't have a mnbudget.dat ?

I just deleted everything except my wallet.dat and dash.conf files

QT wallet didn't automatically start my masternode up on windows 32 however linux 64bit was fine
 
Last edited by a moderator:
TanteStefana said:
I didn't have a mnbudget.dat ?

I just deleted everything except my wallet.dat and dash.conf files

QT wallet didn't automatically start my masternode up on windows 32 however linux 64bit was fine
Click to expand...
I guess it was mncache.dat and budget.dat :rolleyes:
 
UdjinM6 said:
Disclaimer: I'm not perfectly follow what Evan is doing in budgets part so I might miss smth
With that ^^^^ being said:
I was thinking of ways to stop this and restricting MNs to send proposals doesn't sound like a good idea, we need to stop actual proposal submitters from spamming in the first place imo. So here what I got in my thoughts so far:
1. proposal tx (ptx): one should spend 0.01 whatever amount from proposal address paying proposal_fee as a tx fee confirming that (s)he has access to this wallet and effectively paying the network for service some collateral to prevent spam (proposal_fee could be some % of proposal amount but not less then 1DASH for example)
2. submit proposal (include ptx txid:eek:ut as a part of it) signing it with private key that corresponds to the same proposal address (this now must be done from submitter's normal wallet, no need for MN in that case which is absolutely nice imo)
3. network can now say if this proposal is legit by simply verifying that:
- proposal signature match proposal address
- ptx is confirmed (N required confirmations?) and the right fee was payed
and store proposals by hash.
4. to update proposal (s)he needs to create another ptx, proposals with the same ptx should not be allowed - in case there are two of them the one with the earliest valid sig wins and the older one is rejected (applying some ban score to that node (submitter's wallet) to prevent CPU usage attack on network)
5. MNs/MNers should vote by hash to avoid confusions
Click to expand...

Sure that would work and might be a good deal better. But the current system has some limitations per masternode here:
https://github.com/dashpay/dash/blob/v0.12.0.x/src/masternode-budget.cpp#L847

I'm not really sure why they're getting through yet.

Edit: Found the issue with why flare is succeeding at flooding the system.
 
Last edited by a moderator:
coingun said:
Also is it just me or does anyone else feel that a 1 month time frame for proposals might be too quick. I'm watching how long we have worked on testnet and thinking to myself how is anyone going to pull off a massive project in under 30 days? I guess there isn't a specific setting saying the proposal has to be done but if we have a ton of proposals going out and never getting finished it might be a major pita. I wonder if Quarterly would be better?

Also what about doing an actual live dry run on mainnet before we actually open up the proposals. I was thinking we do a multisig wallet and actually do some real world testing voting for that proposal live on mainnet trying to stop us from having another "instamine" fiasco.

I'm also seeing a lot of moving parts and don't want to see this release rushed out to mainnet like some others have in the past just to see 5 more updates on launch day. It's great that we are just taking our time under no major constraints and just working to get this all right.
Click to expand...

The idea is the proposals are long standing, something like this:

1. Initial Proposal To Community
2. Gain traction and get votes
3. Proposal Setup - PaymentCount = 12, BlockStart = Current BlockHeight (This means they'll receive 12 payments over the course of a year)
4. Get enough votes to get it into the finalized budget
5. Proposer or whoever starts the work
6. Proposer gets the first payment
7. Proposer submits progress reports for target milestones (if the community doesn't like what they're doing they can down vote them at this point or any time and stop future payments)
8. Proposer gets another payment 30 days later, submits another milestone report
9. Repeat 8 until the work is complete
 
Last edited by a moderator:
crowning said:
My proposal :grin: to prevent SPAM/DoS is to allow each Masternode to create exactly one single proposal in its lifetime.
Click to expand...

This would work great if we weren't going to have the open portal. That's going to have 1 masternode behind it that's submitting on behalf of the users.
 
eduffield said:
This would work great if we weren't going to have the open portal. That's going to have 1 masternode behind it that's submitting on behalf of the users.
Click to expand...

I still think that charging a small non-refundable amount, like 5 USD for each submission to the network would solve the spam issue :).

Pablo.
 
fible1 said:
I still think that charging a small non-refundable amount, like 5 USD for each submission to the network would solve the spam issue :).

Pablo.
Click to expand...
And maybe we could do something specific with the proposal submission dollars like have it go to foundation? Have it go to some sort of Digital endowment fund? Who knows but there is some opportunity there for PR as well.
 
eduffield said:
The idea is the proposals are long standing, something like this:

1. Initial Proposal To Community
2. Gain traction and get votes
3. Proposal Setup - PaymentCount = 12, BlockStart = Current BlockHeight (This means they'll receive 12 payments over the course of a year)
4. Get enough votes to get it into the finalized budget
5. Proposer or whoever starts the work
6. Proposer gets the first payment
7. Proposer submits progress reports for target milestones (if the community doesn't like what they're doing they can down vote them at this point or any time and stop future payments)
8. Proposer gets another payment 30 days later, submits another milestone report
9. Repeat 8 until the work is complete
Click to expand...
Thanks for explaining it. This wasn't entirely clear to me from the start that this is how it's going to monitored.
 
Wallets with no Masternodes have no problem to sync, shutdown, and restart. But MN wallets have problems:
- "mnbudget show" takes a long time to load the list, and when i tried to shut down the console, it crashed my wallet (win32)
- MN wallets have problem to shut down, the little shutdown window takes longer to close.
- One of my MN wallets could not sync after a restart, so I retarted it again with -reindex, and now even with reindex it's being stuck at block 75799:

upload_2015-7-9_1-19-33.png
 
I've had my qt wallet take it's sweet time to shut down. The "don't close this window" window would show for quite a while, not the second or so I usually get. But if I leave it alone, it does close, usually in under a minute, and the program starts back up without problems.

I don't know if maybe you forced closed it and caused some corruption? I just closed mine again, but I only had a second delay.
 
moli said:
Wallets with no Masternodes have no problem to sync, shutdown, and restart. But MN wallets have problems:
- "mnbudget show" takes a long time to load the list, and when i tried to shut down the console, it crashed my wallet (win32)
- MN wallets have problem to shut down, the little shutdown window takes longer to close.
- One of my MN wallets could not sync after a restart, so I retarted it again with -reindex, and now even with reindex it's being stuck at block 75799:

View attachment 1584
Click to expand...
eduffield UdjinM6
I left this wallet on over night to see if it could sync and it could only get to block 76237 currently. This wallet has 10 MNs, could this be the reason it's trying to sync but can't do it faster? I noticed my other wallet (with only 2 MNs) was slow to sync but wasn't this slow.
Note: the good thing about this new version is it's not hogging the CPU memory like the previous version.

upload_2015-7-9_8-48-47.png


EDIT: In the debug log there's a lot of these lines:
2015-07-09 10:22:17 Loaded info from mncache.dat 3ms
2015-07-09 10:22:17 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 12
2015-07-09 10:22:17 Writting info to mncache.dat...
2015-07-09 10:22:17 Written info to mncache.dat 1ms
2015-07-09 10:22:17 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 12
2015-07-09 10:22:17 Masternode dump finished 7ms
2015-07-09 10:25:50 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:25:50 ERROR: invalid header received
2015-07-09 10:25:50 ProcessMessage(headers, 162003 bytes) FAILED peer=84
2015-07-09 10:25:52 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:25:52 ERROR: invalid header received
2015-07-09 10:25:52 ProcessMessage(headers, 162003 bytes) FAILED peer=73
2015-07-09 10:25:53 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:25:53 ERROR: invalid header received
2015-07-09 10:25:53 ProcessMessage(headers, 162003 bytes) FAILED peer=72
2015-07-09 10:25:56 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:25:56 ERROR: invalid header received
2015-07-09 10:25:56 ProcessMessage(headers, 162003 bytes) FAILED peer=71
2015-07-09 10:26:01 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:26:01 ERROR: invalid header received
2015-07-09 10:26:01 ProcessMessage(headers, 162003 bytes) FAILED peer=70
2015-07-09 10:26:11 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:26:11 ERROR: invalid header received
2015-07-09 10:26:11 ProcessMessage(headers, 162003 bytes) FAILED peer=74
2015-07-09 10:27:14 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:27:14 ERROR: invalid header received
2015-07-09 10:27:14 ProcessMessage(headers, 162003 bytes) FAILED peer=57
2015-07-09 10:28:23 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:28:23 ERROR: invalid header received
2015-07-09 10:28:23 ProcessMessage(headers, 162003 bytes) FAILED peer=57
2015-07-09 10:29:00 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:29:00 ERROR: invalid header received
2015-07-09 10:29:00 ProcessMessage(headers, 162003 bytes) FAILED peer=84
2015-07-09 10:29:02 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:29:02 ERROR: invalid header received
2015-07-09 10:29:02 ProcessMessage(headers, 162003 bytes) FAILED peer=72
2015-07-09 10:29:06 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:29:06 ERROR: invalid header received
2015-07-09 10:29:06 ProcessMessage(headers, 162003 bytes) FAILED peer=70
2015-07-09 10:29:11 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:29:11 ERROR: invalid header received
2015-07-09 10:29:11 ProcessMessage(headers, 162003 bytes) FAILED peer=57
2015-07-09 10:29:16 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:29:16 ERROR: invalid header received
2015-07-09 10:29:16 ProcessMessage(headers, 162003 bytes) FAILED peer=74
2015-07-09 10:29:23 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:29:23 ERROR: invalid header received
2015-07-09 10:29:23 ProcessMessage(headers, 162003 bytes) FAILED peer=71
2015-07-09 10:31:55 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:31:55 ERROR: invalid header received
2015-07-09 10:31:55 ProcessMessage(headers, 162003 bytes) FAILED peer=72
2015-07-09 10:32:07 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:32:07 ERROR: invalid header received
2015-07-09 10:32:07 ProcessMessage(headers, 162003 bytes) FAILED peer=57
2015-07-09 10:32:12 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:32:12 ERROR: invalid header received
2015-07-09 10:32:12 ProcessMessage(headers, 162003 bytes) FAILED peer=71
2015-07-09 10:32:14 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:32:14 ERROR: invalid header received
2015-07-09 10:32:14 ProcessMessage(headers, 162003 bytes) FAILED peer=74
2015-07-09 10:32:20 UPnP Port Mapping successful.
2015-07-09 10:32:42 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:32:42 ERROR: invalid header received
2015-07-09 10:32:42 ProcessMessage(headers, 162003 bytes) FAILED peer=84
2015-07-09 10:32:51 ERROR: AcceptBlockHeader : block is marked invalid
2015-07-09 10:32:51 ERROR: invalid header received
2015-07-09 10:32:51 ProcessMessage(headers, 162003 bytes) FAILED peer=73
Click to expand...

I just restarted this wallet with Udjin's bootstrap and it's syncing fine now.
BUT... now it's taking up about ~50% CPU again!
 
Last edited by a moderator:
Have you tried restarting but deleting everything in the .dash/testnet3 or /appdata/roaming/dash/testnet3 folder except your wallet.dat, dash.conf and masternode.conf files? Something could have gotten corrupted?
 
eduffield UdjinM6
win32 - v0.12.0.11-0e89bba - (I installed this version after deleting mncache.dat, budge.dat, and peers.dat from the previous version).
The console keeps freezing while "mnbuget show" is trying to load the list. So many "flarexxx" proposals are still in the list. Client's still taking up ~50% CPU.

upload_2015-7-9_12-43-10.png
 
actually, when I do mnbudget show or mnbudget getinfo or anything, nothing happens, it just hangs on the daemon, or doesn't give any info back on qt

Wait, the qt budget show command did come through, it just took a long time. so far the daemon hasn't.... waiting...

Still nothing on the daemon, and my qt wallet is now laggy, like moli said :) something aint right, LOL.

And debug file too big to open (almost 1 gb??? How'd that happen?)

Daemon finally came through, but debug log also exploded to over a gig. Now this is very strange??

My notepad and notepad++ can't open the file because it's too big. I'm trying to open the remote debug.log file via WinSCP which will take a while, to see what's inside ;P

moli it's probably the large debug file that is slowing down the wallet/cpu etc... It used to slow down the wallet when it was only a few tens of megabytes, that's why Evan stopped logging some stuff. But whatever problem the wallets are having with this, it's spamming the debug log to death :)
 
Last edited by a moderator:
eduffield - Reporting again on my above wallet... v0.12.0.11-0e89bba... After shutting it down for about an hour, I tried to restart it back up, it got stuck at "1 hour behind", block 81001 and got a lot of these spamming messages in the debug log:
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
2015-07-09 18:09:59 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(fbc16ae5229d6d99181802fd76a4feee5e7640164dcebc7f8feb04a7bea026f8, 0), scriptSig=)
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
2015-07-09 18:09:59 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(c8b21368a81b6af2ebe65461342a6e7e3dbe9e9dc89528622182f8538680ffbb, 1), scriptSig=)
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
2015-07-09 18:09:59 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(fbc16ae5229d6d99181802fd76a4feee5e7640164dcebc7f8feb04a7bea026f8, 0), scriptSig=)
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
2015-07-09 18:09:59 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(c8b21368a81b6af2ebe65461342a6e7e3dbe9e9dc89528622182f8538680ffbb, 1), scriptSig=)
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
2015-07-09 18:09:59 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(423a55966cb0c30a18f400302d94a80b6b0278275e60f639f87770aaaf3db850, 1), scriptSig=)
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
2015-07-09 18:09:59 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(9bb457af616a2151884f9f3ccb477c57fdcb566ea4f3580a3c2fb968287ab00a, 0), scriptSig=)
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
2015-07-09 18:09:59 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(fbc16ae5229d6d99181802fd76a4feee5e7640164dcebc7f8feb04a7bea026f8, 0), scriptSig=)
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
2015-07-09 18:09:59 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(a62ab8b54bd1e3d016a848cfda25dd3fc034b4f95587362f6808a61c25355b35, 0), scriptSig=)
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
2015-07-09 18:09:59 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(36af6be87db5088236090fa2398c224b95080a61627d9a38feb2739f489319fa, 1), scriptSig=)
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
2015-07-09 18:09:59 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(055f6fb0a1c6db5dc083b8d03ea0eca19346a1bd239228d6850d4547c824b3e9, 1), scriptSig=)
2015-07-09 18:09:59 CBudgetManager::ResignInvalidProposals -- proposal - resigning proposal
Click to expand...
 
Another MN wallet I shut down a little while ago, now trying to restart.. It's stuck at "0 hours behind", block 81033, and has these messages in the debug log:

2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(9bb457af616a2151884f9f3ccb477c57fdcb566ea4f3580a3c2fb968287ab00a, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(148c0dd7ba17115fb02d3d2613549ed55d12891462bb33c9618f8cef98763cdb, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(148c0dd7ba17115fb02d3d2613549ed55d12891462bb33c9618f8cef98763cdb, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(9bb457af616a2151884f9f3ccb477c57fdcb566ea4f3580a3c2fb968287ab00a, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(fbc16ae5229d6d99181802fd76a4feee5e7640164dcebc7f8feb04a7bea026f8, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(fbc16ae5229d6d99181802fd76a4feee5e7640164dcebc7f8feb04a7bea026f8, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(9bb457af616a2151884f9f3ccb477c57fdcb566ea4f3580a3c2fb968287ab00a, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(9bb457af616a2151884f9f3ccb477c57fdcb566ea4f3580a3c2fb968287ab00a, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(fbc16ae5229d6d99181802fd76a4feee5e7640164dcebc7f8feb04a7bea026f8, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(fbc16ae5229d6d99181802fd76a4feee5e7640164dcebc7f8feb04a7bea026f8, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(9bb457af616a2151884f9f3ccb477c57fdcb566ea4f3580a3c2fb968287ab00a, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(fbc16ae5229d6d99181802fd76a4feee5e7640164dcebc7f8feb04a7bea026f8, 0), scriptSig=)
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
2015-07-09 18:51:30 CBudgetProposalBroadcast::SignatureValid() - Verify message failed
Click to expand...
EDIT: Now it's finally synced.
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top