[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[stonehedge]

Cheers.  Obvious if I had thought about it.

[1714949115]

1714949115

[1714949115]

1714949115

[1714949115]

1714949115

[AizenSou]

i wonder if anyone on this forum has set up  20 masternodes..and what are the dark rewards per month in total??

Ask Ignition75. That bastard has 100 MNs

[TaoOfSaatoshi]

Hi DRK guys

i switched my trade to bitfinex... im a alone?

My buy orders rest alongside yours...

[dotnetmin]

After updating to onyx my MN on chaplins side is all few hours shown as inactive on SV1...SV6.
After masternode start on lokal wallet it is online again.
I happens now 4x. No payments. As i only have one MN i cant copare what others do.

[TaoOfSaatoshi]

Elbereth monitoring ® update in progress to ONYX.
Great.
After this green = green... ellow will not be ok anymore

Thanks for the update!

[TaoOfSaatoshi]

DARKCOIN TWITTER PR INITIATIVE (DTPI) UPDATE:

http://buff.ly/1wkCiih

Cheers!

[oblox]

After updating to onyx my MN on chaplins side is all few hours shown as inactive on SV1...SV6.
After masternode start on lokal wallet it is online again.
I happens now 4x. No payments. As i only have one MN i cant copare what others do.

Periodically keep checking it (there are times when I have to manually start from local). It doesn't help that there is still RC5 masternode lists and different protocols on the network. Remember, the network is looking for consensus. When Wafflepool, Trademybit, and miningpoolhub update, we'll have around 85% of the network on Onyx and I doubt we'll be having as many issues as it relates to masternodes going inactive.

[Ignition75]

i wonder if anyone on this forum has set up  20 masternodes..and what are the dark rewards per month in total??

Ask Ignition75. That bastard has 100 MNs

Oh... Listen to LTCJesus calling me a whale!

I have zero masternodes  

I'm mixing my stash with a factor of 8 whilst a good friend of ours is building me a bullet proof image to use on my nodes moving forwards  

By the way, could you make the text on your sig just a little larger please?  They are having trouble reading it from the moon...

[raze182]

After updating to onyx my MN on chaplins side is all few hours shown as inactive on SV1...SV6.
After masternode start on lokal wallet it is online again.
I happens now 4x. No payments. As i only have one MN i cant copare what others do.

I was having the same problem. Try deleting peers.dat and restart both local and remote. Worked for me.

http://jira.darkcoin.qa/browse/DRK-104

[stonehedge]

After updating to onyx my MN on chaplins side is all few hours shown as inactive on SV1...SV6.
After masternode start on lokal wallet it is online again.
I happens now 4x. No payments. As i only have one MN i cant copare what others do.

Periodically keep checking it (there are times when I have to manually start from local). It doesn't help that there is still RC5 masternode lists and different protocols on the network. Remember, the network is looking for consensus. When Wafflepool, Trademybit, and miningpoolhub update, we'll have around 85% of the network on Onyx and I doubt we'll be having as many issues as it relates to masternodes going inactive.

Or appearing to go inactive anyway.  One of my apparently unlisted masternodes got paid yesterday!

[camosoul]

As much as people are pushing for Bitfinex, Cryptsy still has most of the volume. Traders are going to go where the volume is.

Traders cause the volume by going where they do. The chicken, not the egg... But I don't expect traders to understand it...

[oblox]

After updating to onyx my MN on chaplins side is all few hours shown as inactive on SV1...SV6.
After masternode start on lokal wallet it is online again.
I happens now 4x. No payments. As i only have one MN i cant copare what others do.

Periodically keep checking it (there are times when I have to manually start from local). It doesn't help that there is still RC5 masternode lists and different protocols on the network. Remember, the network is looking for consensus. When Wafflepool, Trademybit, and miningpoolhub update, we'll have around 85% of the network on Onyx and I doubt we'll be having as many issues as it relates to masternodes going inactive.

Or appearing to go inactive anyway.  One of my apparently unlisted masternodes got paid yesterday!

If you are grepping 1 on the remote daemon, you should be fine and it's showing inactive because of the different lists going across the network. Masternode start can bring it back to "active" but realistically, the masternodes should still be active even if they aren't flashing as active on drk.mn or poolhash.org. I issue the masternode start command because it doesn't take that long to do.

[Laxdude7691]

Thanks to Crowning who posted about the "masternode start" from the cold wallet. I was able to restart myself without the help of my son this time. Unfortunately he is not interested in whats going on as much as I am and I have to hound him about updates. I'm learning though...

So for my own clarification will this MN inactive problem stop once more are running Onyx?
Edit: Nevermind about question...just read above post.

[eahmadov]

After updating to onyx my MN on chaplins side is all few hours shown as inactive on SV1...SV6.
After masternode start on lokal wallet it is online again.
I happens now 4x. No payments. As i only have one MN i cant copare what others do.

Don't worry about it. I also had only sv03 active (green) but got paid today. Didn't delete any peer document either.

[camosoul]

A notion just struck me...

When denominating a large chunk that gets submitted, doesn't get enough entries, gets submitted, doesn't get enough entries... This happens hundreds of times before 3 finally show up... Does the failed entry process give anything away? It happens so much you're pretty much guaranteed to have submitted it to every masternode in the network several times before it actually happens, so couldn't just a single rogue node monitor/track large chunks through this process of repeated submissions?

[eduffield]

A notion just struck me...

When denominating a large chunk that gets submitted, doesn't get enough entries, gets submitted, doesn't get enough entries... This happens hundreds of times before 3 finally show up... Does the failed entry process give anything away? It happens so much you're pretty much guaranteed to have submitted it to every masternode in the network several times before it actually happens, so couldn't just a single rogue node monitor/track large chunks through this process of repeated submissions?

The presubmission phase is where the client just says "hey, I'd like to mix these denominations here", then the masternode broadcasts a message saying it's accepting more clients. If it gets 3 of those "hey, I'd like to mix" messages, it'll tell those users to submit their actual transactions, inputs+outputs. So the system doesn't reveal any information until the actual mixing is about to happen.

Look at the "dsa" and "dsq" message events in main.cpp for more info.

[eahmadov]

A notion just struck me...

When denominating a large chunk that gets submitted, doesn't get enough entries, gets submitted, doesn't get enough entries... This happens hundreds of times before 3 finally show up... Does the failed entry process give anything away? It happens so much you're pretty much guaranteed to have submitted it to every masternode in the network several times before it actually happens, so couldn't just a single rogue node monitor/track large chunks through this process of repeated submissions?

The presubmission phase is where the client just says "hey, I'd like to mix these denominations here", then the masternode broadcasts a message saying it's accepting more clients. If it gets 3 of those "hey, I'd like to mix" messages, it'll tell those users to submit their actual transactions, inputs+outputs. So the system doesn't reveal any information until the actual mixing is about to happen.

Look at the "dsa" and "dsq" message events in main.cpp for more info.

There are 2 people now mixing 400drk/4 rounds on main-net. You guys are welcome to join.

[oblox]

Wafflepool is updated.

[Walter_S]

A notion just struck me...

When denominating a large chunk that gets submitted, doesn't get enough entries, gets submitted, doesn't get enough entries... This happens hundreds of times before 3 finally show up... Does the failed entry process give anything away? It happens so much you're pretty much guaranteed to have submitted it to every masternode in the network several times before it actually happens, so couldn't just a single rogue node monitor/track large chunks through this process of repeated submissions?

The presubmission phase is where the client just says "hey, I'd like to mix these denominations here", then the masternode broadcasts a message saying it's accepting more clients. If it gets 3 of those "hey, I'd like to mix" messages, it'll tell those users to submit their actual transactions, inputs+outputs. So the system doesn't reveal any information until the actual mixing is about to happen.

Look at the "dsa" and "dsq" message events in main.cpp for more info.

Evan, thanks for the explanation there. One question though... I'm trying to test darksend on the main net but no matter what amount i set my client to mix I cannot get any results...

Here's a few minutes of debug.log:

2014-10-19 18:59:20 Darksend is idle
2014-10-19 18:59:31 dssu - state: 2 entriesCount: 0 accepted: -1 error: 
2014-10-19 18:59:31 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 18:59:31 Submitted to masternode, waiting in queue .
2014-10-19 18:59:31 AcceptToMemoryPool: 108.61.205.85:9999 /Satoshi:0.10.14.1/ : accepted c5d45c804681e47c26418f8e2c9ad1057eb54cd58540a9cc320619090c0c1705 (poolsz 7)
2014-10-19 18:59:34 Submiting Darksend for 397.000000 DRK
2014-10-19 18:59:34 DoAutomaticDenominating --- connected (from queue), sending dsa for 39700000007 - denom 14
2014-10-19 18:59:34 dssu - state: 3 entriesCount: 0 accepted: -1 error: 
2014-10-19 18:59:34 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 18:59:34 dssu - state: 2 entriesCount: 0 accepted: 1 error: 
2014-10-19 18:59:34 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 18:59:34 CDarkSendPool::StatusUpdate - set sessionID to 0
2014-10-19 18:59:48 Submitted to masternode, waiting in queue ..
2014-10-19 18:59:52 Submitted to masternode, waiting in queue ...
2014-10-19 18:59:55 Submitted to masternode, waiting in queue .
2014-10-19 19:00:12 Submitted to masternode, waiting in queue ..
2014-10-19 19:00:15 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:00:15 Darksend is idle
2014-10-19 19:00:30 dssu - state: 2 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:00:30 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:00:30 Submitted to masternode, waiting in queue .
2014-10-19 19:00:34 Submiting Darksend for 397.000000 DRK
2014-10-19 19:00:34 DoAutomaticDenominating --- connected (from queue), sending dsa for 39700000007 - denom 14
2014-10-19 19:00:35 dssu - state: 3 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:00:35 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:00:35 dssu - state: 2 entriesCount: 0 accepted: 1 error: 
2014-10-19 19:00:35 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:00:35 CDarkSendPool::StatusUpdate - set sessionID to 0
2014-10-19 19:00:47 Submitted to masternode, waiting in queue ..
2014-10-19 19:00:51 Submitted to masternode, waiting in queue ...
2014-10-19 19:00:54 Submitted to masternode, waiting in queue .
2014-10-19 19:01:11 Submitted to masternode, waiting in queue ..
2014-10-19 19:01:15 Submitted to masternode, waiting in queue ...
2014-10-19 19:01:15 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:01:15 Darksend is idle
2014-10-19 19:01:31 dssu - state: 2 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:01:31 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:01:31 Submitted to masternode, waiting in queue .
2014-10-19 19:01:34 Submiting Darksend for 397.000000 DRK
2014-10-19 19:01:34 DoAutomaticDenominating --- connected (from queue), sending dsa for 39700000007 - denom 14
2014-10-19 19:01:35 dssu - state: 3 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:01:35 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:01:35 dssu - state: 2 entriesCount: 0 accepted: 1 error: 
2014-10-19 19:01:35 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:01:35 CDarkSendPool::StatusUpdate - set sessionID to 0
2014-10-19 19:01:38 Added 1 addresses from 54.84.51.218: 394 tried, 9845 new
2014-10-19 19:01:48 Submitted to masternode, waiting in queue ..
2014-10-19 19:01:52 Submitted to masternode, waiting in queue ...
2014-10-19 19:01:55 Submitted to masternode, waiting in queue .
2014-10-19 19:02:12 Submitted to masternode, waiting in queue ..
2014-10-19 19:02:15 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:02:15 Darksend is idle
2014-10-19 19:02:33 dssu - state: 2 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:02:33 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:02:33 Submitted to masternode, waiting in queue .
2014-10-19 19:02:34 Submiting Darksend for 397.000000 DRK
2014-10-19 19:02:34 DoAutomaticDenominating --- connected (from queue), sending dsa for 39700000007 - denom 14
2014-10-19 19:02:35 dssu - state: 3 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:02:35 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:02:35 dssu - state: 2 entriesCount: 0 accepted: 1 error: 
2014-10-19 19:02:35 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:02:35 CDarkSendPool::StatusUpdate - set sessionID to 0
2014-10-19 19:02:38 ProcessSyncCheckpoint: sync-checkpoint at 00000000000d865d0474e2dfd1b27c3b5f685dd64529c0cce31fc933a1ac4d9f
2014-10-19 19:02:38 received block 000000000014a9cecb4f493471b66a25da11b29fd70179686a92cd367b507305 peer=100
2014-10-19 19:02:38 Committing 315 changed transactions to coin database...
2014-10-19 19:02:38 SetBestChain: new best=000000000014a9cecb4f493471b66a25da11b29fd70179686a92cd367b507305  height=155359  log2_work=60.270123  tx=606103  date=2014-10-19 19:04:02 progress=1.000001
2014-10-19 19:02:38 Closing masternode connection 54.84.51.218:9999
2014-10-19 19:02:38 disconnecting node 54.84.51.218:9999
2014-10-19 19:02:38 send last getblocks for 000000000014a9cecb4f493471b66a25da11b29fd70179686a92cd367b507305 peer=102
2014-10-19 19:02:38 send last getblocks for 000000000014a9cecb4f493471b66a25da11b29fd70179686a92cd367b507305 peer=120
2014-10-19 19:02:38 send last getblocks for 000000000014a9cecb4f493471b66a25da11b29fd70179686a92cd367b507305 peer=150
2014-10-19 19:02:39 send last getblocks for 000000000014a9cecb4f493471b66a25da11b29fd70179686a92cd367b507305 peer=101
2014-10-19 19:02:39 getblocks -1 to 0 limit 500 peer=101
2014-10-19 19:02:39 getblocks -1 to 0 limit 500 peer=96
2014-10-19 19:02:50 Submitted to masternode, waiting in queue ..
2014-10-19 19:02:54 Submitted to masternode, waiting in queue ...
2014-10-19 19:02:57 Submitted to masternode, waiting in queue .
2014-10-19 19:02:57 Flushed 10239 addresses to peers.dat  58ms
2014-10-19 19:03:06 peer=153 says we are misbehaving 20
2014-10-19 19:03:11 received block 00000000001c43f1318fd0eed88b2fc180b8dd3514f85ddb0d84609e8929c526 peer=102
2014-10-19 19:03:11 Committing 3 changed transactions to coin database...
2014-10-19 19:03:11 SetBestChain: new best=00000000001c43f1318fd0eed88b2fc180b8dd3514f85ddb0d84609e8929c526  height=155360  log2_work=60.270133  tx=606105  date=2014-10-19 19:04:47 progress=1.000002
2014-10-19 19:03:11 send last getblocks for 00000000001c43f1318fd0eed88b2fc180b8dd3514f85ddb0d84609e8929c526 peer=150
2014-10-19 19:03:11 send last getblocks for 00000000001c43f1318fd0eed88b2fc180b8dd3514f85ddb0d84609e8929c526 peer=153
2014-10-19 19:03:11 ProcessSyncCheckpoint: sync-checkpoint at 000000000012ee366ce66a334f697bfb781021ae49c2ec299f670007f73aefdd
2014-10-19 19:03:11 send last getblocks for 00000000001c43f1318fd0eed88b2fc180b8dd3514f85ddb0d84609e8929c526 peer=120
2014-10-19 19:03:11 send last getblocks for 00000000001c43f1318fd0eed88b2fc180b8dd3514f85ddb0d84609e8929c526 peer=101
2014-10-19 19:03:11 getblocks -1 to 0 limit 500 peer=120
2014-10-19 19:03:11 getblocks -1 to 0 limit 500 peer=101
2014-10-19 19:03:13 send last getblocks for 00000000001c43f1318fd0eed88b2fc180b8dd3514f85ddb0d84609e8929c526 peer=97
2014-10-19 19:03:13 getblocks -1 to 0 limit 500 peer=97
2014-10-19 19:03:14 Submitted to masternode, waiting in queue ..
2014-10-19 19:03:15 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:03:15 Darksend is idle
2014-10-19 19:03:31 dssu - state: 2 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:03:31 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:03:31 Submitted to masternode, waiting in queue .
2014-10-19 19:03:34 Submiting Darksend for 397.000000 DRK
2014-10-19 19:03:34 trying connection 54.84.51.218:9999 lastseen=15205.4days
2014-10-19 19:03:34 connected 54.84.51.218:9999
2014-10-19 19:03:34 send version message: version 70043, blocks=155360, us=90.244.165.205:9999, them=54.84.51.218:9999, peer=155
2014-10-19 19:03:34 DoAutomaticDenominating --- connected (from queue), sending dsa for 39700000007 - denom 14
2014-10-19 19:03:35 receive version message: /Satoshi:0.10.15.13/: version 70043, blocks=155360, us=90.244.172.143:51565, them=54.164.37.228:9999, peer=155
2014-10-19 19:03:35 send initial getblocks peer=155
2014-10-19 19:03:35 getblocks -1 to 0 limit 500 peer=155
2014-10-19 19:03:35 dssu - state: 3 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:03:35 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:03:35 dssu - state: 2 entriesCount: 0 accepted: 1 error: 
2014-10-19 19:03:35 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:03:35 CDarkSendPool::StatusUpdate - set sessionID to 0
2014-10-19 19:03:36 Added 256 addresses from 54.84.51.218: 394 tried, 9851 new
2014-10-19 19:03:36 Added 287 addresses from 54.84.51.218: 394 tried, 9841 new
2014-10-19 19:03:36 Added 111 addresses from 54.84.51.218: 394 tried, 9834 new
2014-10-19 19:03:48 Submitted to masternode, waiting in queue ..
2014-10-19 19:03:52 Submitted to masternode, waiting in queue ...
2014-10-19 19:03:55 Submitted to masternode, waiting in queue .
2014-10-19 19:03:56 AcceptToMemoryPool: 54.72.232.244:9999 /Satoshi:0.10.15.13/ : accepted 86962d9081c81c68378461e272471ed1e86b6f5f148a3107500036a740128fde (poolsz 1)
2014-10-19 19:03:57 received getdata for: tx 86962d9081c81c68378461e272471ed1e86b6f5f148a3107500036a740128fde peer=155
2014-10-19 19:03:57 received getdata for: tx 86962d9081c81c68378461e272471ed1e86b6f5f148a3107500036a740128fde peer=96
2014-10-19 19:03:57 AcceptToMemoryPool: 94.156.77.166:9999 /Satoshi:0.10.14.1/ : accepted 61f2e810642a85f1301effb0a815a596614b3e2232ed2fcd8b70284286f83a79 (poolsz 2)
2014-10-19 19:03:57 AcceptToMemoryPool: 54.84.51.218:9999 /Satoshi:0.10.15.13/ : accepted bd52b9fc13b890baaa88c9d812121263851fb7cf4c364e0f2ddc7a74a1af7abb (poolsz 3)
2014-10-19 19:04:12 Submitted to masternode, waiting in queue ..
2014-10-19 19:04:15 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:04:15 Darksend is idle
2014-10-19 19:04:32 dssu - state: 2 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:04:32 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:04:32 Submitted to masternode, waiting in queue .
2014-10-19 19:04:34 Submiting Darksend for 397.000000 DRK
2014-10-19 19:04:34 DoAutomaticDenominating --- connected (from queue), sending dsa for 39700000007 - denom 14
2014-10-19 19:04:35 dssu - state: 3 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:04:35 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:04:35 dssu - state: 2 entriesCount: 0 accepted: 1 error: 
2014-10-19 19:04:35 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:04:35 CDarkSendPool::StatusUpdate - set sessionID to 0
2014-10-19 19:04:46 dseep: Couldn't find masternode entry CTxIn(COutPoint(5020de98a77d80c94744db5550c42aad38d188ecfda8992728b66d768645c9a7, 0), scriptSig=)
2014-10-19 19:04:49 Submitted to masternode, waiting in queue ..
2014-10-19 19:04:53 Submitted to masternode, waiting in queue ...
2014-10-19 19:04:56 Submitted to masternode, waiting in queue .
2014-10-19 19:05:13 Submitted to masternode, waiting in queue ..
2014-10-19 19:05:15 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:05:15 Darksend is idle
2014-10-19 19:05:32 dssu - state: 2 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:05:32 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:05:32 Submitted to masternode, waiting in queue .
2014-10-19 19:05:34 Submiting Darksend for 397.000000 DRK
2014-10-19 19:05:34 DoAutomaticDenominating --- connected (from queue), sending dsa for 39700000007 - denom 14
2014-10-19 19:05:35 dssu - state: 3 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:05:35 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:05:35 dssu - state: 2 entriesCount: 0 accepted: 1 error: 
2014-10-19 19:05:35 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:05:35 CDarkSendPool::StatusUpdate - set sessionID to 0
2014-10-19 19:05:42 AcceptToMemoryPool: 5.45.75.6:9999 /Satoshi:0.9.13.15/ : accepted 821b09f01c84969201e7c974724ee9f7fdcdd6382678c308550df5c50f4ca8c0 (poolsz 4)
2014-10-19 19:05:49 Submitted to masternode, waiting in queue ..
2014-10-19 19:05:53 Submitted to masternode, waiting in queue ...
2014-10-19 19:05:56 Submitted to masternode, waiting in queue .
2014-10-19 19:06:00 AcceptToMemoryPool: 74.39.55.146:9999 /Satoshi:0.9.13.15/ : accepted c981d0eaa1b4bb3fa36f7331f9ce7190e393816c86b06c2d2f39f48b2f11b5ab (poolsz 5)
2014-10-19 19:06:13 Submitted to masternode, waiting in queue ..
2014-10-19 19:06:15 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:06:16 Darksend is idle
2014-10-19 19:06:32 dssu - state: 2 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:06:32 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:06:32 Submitted to masternode, waiting in queue .
2014-10-19 19:06:34 Submiting Darksend for 397.000000 DRK
2014-10-19 19:06:34 DoAutomaticDenominating --- connected (from queue), sending dsa for 39700000007 - denom 14
2014-10-19 19:06:35 dssu - state: 3 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:06:35 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:06:35 dssu - state: 2 entriesCount: 0 accepted: 1 error: 
2014-10-19 19:06:35 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:06:35 CDarkSendPool::StatusUpdate - set sessionID to 0
2014-10-19 19:06:50 Submitted to masternode, waiting in queue ..
2014-10-19 19:06:53 Submitted to masternode, waiting in queue ...
2014-10-19 19:06:56 Submitted to masternode, waiting in queue .
2014-10-19 19:07:14 Submitted to masternode, waiting in queue ..
2014-10-19 19:07:15 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:07:15 Darksend is idle
2014-10-19 19:07:32 dssu - state: 2 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:07:32 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:07:32 Submitted to masternode, waiting in queue .
2014-10-19 19:07:34 Submiting Darksend for 397.000000 DRK
2014-10-19 19:07:34 DoAutomaticDenominating --- connected (from queue), sending dsa for 39700000007 - denom 14
2014-10-19 19:07:35 dssu - state: 3 entriesCount: 0 accepted: -1 error: 
2014-10-19 19:07:35 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:07:35 dssu - state: 2 entriesCount: 0 accepted: 1 error: 
2014-10-19 19:07:35 CDarkSendPool::UpdateState() == 3 | 2
2014-10-19 19:07:35 CDarkSendPool::StatusUpdate - set sessionID to 0
2014-10-19 19:07:49 Submitted to masternode, waiting in queue ..
2014-10-19 19:07:53 Submitted to masternode, waiting in queue ...
2014-10-19 19:07:56 Submitted to masternode, waiting in queue .
2014-10-19 19:08:13 Submitted to masternode, waiting in queue ..
2014-10-19 19:08:15 CDarkSendPool::UpdateState() == 2 | 3
2014-10-19 19:08:16 Darksend is idle

Anything unusual in there? I see lots of error state. Is that normal? Any help much appreciated.

Thanks,

Walter

[TanteStefana2]

After updating to onyx my MN on chaplins side is all few hours shown as inactive on SV1...SV6.
After masternode start on lokal wallet it is online again.
I happens now 4x. No payments. As i only have one MN i cant copare what others do.

If your masternode says it "successfully started masternode" when you type in masternode debug, then it's good.  Don't go by the masternode chart.  It is waffling between new and old versions as we're around the 50% point.  Actually the guys are reporting that it should show up correctly now as we're over 60% ATM.  But don't fuss with your setup.  I also haven't gotten paid in the last few days because until the miners update, only masternodes on the old version get paid.  I switch over right away because I want to support the coin, but it's really a great way to lose money...