v0.10.16 - Onyx v2

maky

Member
Nov 14, 2014
71
32
58
Upgraded to v10.16.5 early morning (and it works fine)
Upgraded to v10.16.6 now (and it works fine too)
 

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
If our great and wise and beloved leaders could post a quick example of how to get start-many set up it would be greatly appreciated, pretty pretty please. :kiss:
 

paperThin

Member
Jun 13, 2014
106
19
68
I noticed Even mentioned something about "Darksend request incomplete. Last darksend was too recent". That it would not happen often, but it could still come up under some circumstances and when you first start up.

I am trying to "Mix" and I am getting this "Darksend request incomplete. Last darksend was too recent". Anyone else seeing this continuously? (I have not used my wallet for about a week before opening it today.)
 

qwizzie

Well-known Member
Aug 6, 2014
1,581
737
183
I noticed Even mentioned something about "Darksend request incomplete. Last darksend was too recent". That it would not happen often, but it could still come up under some circumstances and when you first start up.

I am trying to "Mix" and I am getting this "Darksend request incomplete. Last darksend was too recent". Anyone else seeing this continuously? (I have not used my wallet for about a week before opening it today.)
i would wait with mixing untill the network has stabilised somewhat.... in a few days the network will be a lot more stabile and up to date.
 
  • Like
Reactions: fernando

oaxaca

Well-known Member
Foundation Member
Jul 8, 2014
573
832
263
I assume that there is still a need for "liquidity providers". Can we get new fangled binaries?
 

paperThin

Member
Jun 13, 2014
106
19
68
i would wait with mixing untill the network has stabilised somewhat.... in a few days the network will be a lot more stabile and up to date.

Thanks Quizzie... I will wait a little... I thought the warning was strange, saying "too recent". It seems like it should say something else if the network has not stabilized like... "nodes not found" or "no matching transactions to mix" etc. I will wait a bit, but I am anxious to try out this new hot rod!
 

Lebubar

Active Member
Mar 15, 2014
249
213
103
6.5 MN updated without problem all seen all of them.
Great work again!

But they don't see the same number of MN :
[email protected]:~$ ./darkcoind masternode list | grep ": 1" | wc -l
204
____
[email protected]:~$ ./darkcoind masternode list | grep ": 1" | wc -l
163
__________
[email protected]:~$ ./darkcoind masternode list | grep ": 1" | wc -l
173

we have to wait to stabilized =)
 
Last edited by a moderator:
S

snogcel

Guest
updated with no problems!

question -- with removed darksend fees, does that mean there is now no cost of running a liquidity provider?
 

tungfa

Administrator
Dash Core Team
Moderator
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,895
6,723
1,283
Question:
There was somewhere a comment/post that this update has
Start Multiple for MN's build in ?!
Can anybody please provide a guide/explanation how this works
Tx
 

strix

Well-known Member
Foundation Member
Sep 14, 2014
140
121
193
The Shadow Lands
I noticed Even mentioned something about "Darksend request incomplete. Last darksend was too recent". That it would not happen often, but it could still come up under some circumstances and when you first start up.

I am trying to "Mix" and I am getting this "Darksend request incomplete. Last darksend was too recent". Anyone else seeing this continuously? (I have not used my wallet for about a week before opening it today.)
I am getting the same thing, but I had my wallet opened last night before updating today. How long should I wait before trying again?
 

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
Sorry to annoy you but there is still something wrong :rolleyes:
Code:
masternode list lastseen
...........
........
"104.156.231.81:9999" : 1416014572,
"176.31.190.77:9999" : 1416013860,
"188.226.180.119:9999" : 2045615525,
"188.226.228.88:9999" : 2045775280,
"80.240.135.83:9999" : 2045945974,
"95.85.1.197:9999" : 2046103671,
"107.170.157.166:9999" : 2046184866,
"95.85.48.49:9999" : 2046343833,
"188.226.196.182:9999" : 2046506665,
"188.226.201.140:9999" : 2046666796,
"107.170.242.110:9999" : 2046790382,
........
......
And that just can't be true: 1416014572 for example is Sat, 15 Nov 2014 01:22:52 GMT but 2045615525 is Sat, 28 Oct 2034 02:32:05 GMT
( http://www.onlineconversion.com/unix_time.htm )
and there are a lot of them...
I wouldn't be worry too much about it but I guess that could prevent "DarkSend Election Entry Ping" (dseep) message from propagating and that's actually the message that should tell everyone else that your MN is alive as far as I understand (normally you should send it every 20 minutes)
https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L178-L181
The source of such behavior is there I believe
https://github.com/darkcoin/darkcoin/blob/master/src/activemasternode.cpp#L227
It should say
Code:
masterNodeSignatureTime = GetAdjustedTime();
and not
Code:
masterNodeSignatureTime = GetTimeMicros();
eduffield flare
 

JGCMiner

Moderator
Moderator
Jun 8, 2014
360
211
113
I am getting the same thing, but I had my wallet opened last night before updating today. How long should I wait before trying again?
Having the same "last Darksend too recent" problem as well. No successful denominations thus far on 16.6...
 
Last edited by a moderator:

djcrypto

Member
May 27, 2014
180
94
88
All my MNs are updated and showing up on client debug window 'masternode list' command.
No rewards yet though. Will give it a day or two.
Cheers!
 

Lebubar

Active Member
Mar 15, 2014
249
213
103
Well after maybe 2 hours all my MN were unlisted...
Restared them from local. Will monitor later again.
They list more or less 200 Mn, with small diference from one to other.

Edit: and again after some times all unlisted again...
All now have 205 :
[email protected]:~$ ./darkcoind masternode list | grep ": 1" | wc -l
205

Am I alone with this problem, all my MN get unlisted after some times?

In the trace I can only see for the moment message like this :
2014-11-15 02:18:25 Removing inactive masternode 108.61.219.39:9999
 
Last edited by a moderator:
  • Like
Reactions: djcrypto and tungfa

djcrypto

Member
May 27, 2014
180
94
88
Same all mine got unlisted. Just restarted them. Will see how long they last...FYI I did get a paid once in that time period so I think they're "working". Just maybe a problem with stability?
 

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,336
574
283
Finland
Same all mine got unlisted. Just restarted them. Will see how long they last...FYI I did get a paid once in that time period so I think they're "working". Just maybe a problem with stability?
Same here, ALL my MN:s drops off from the list.
Its my new dayjob, starting all day long my MN:s.:sad:
 
Last edited by a moderator:
  • Like
Reactions: djcrypto

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,336
574
283
Finland
Any info how fast they drop off the list?
Watching this how long MN:s are listed and when they drop off the list, reporting back when they get unlisted.
Last start: 10:49...
 

jpr

Active Member
May 11, 2014
493
393
133
same here they dissapear after like 2 hours
When I do
Code:
masternode start password
in local wallet they come back
 

Raico

Well-known Member
Foundation Member
Dash Support Group
May 28, 2014
138
142
193
Same here, ALL my MN:s drops off from the list.
Its my new dayjob, starting all day long my MN:s.:sad:
Same Here~ log send~
Hope may help~

Edit: drop list about one hour.
 
Last edited by a moderator:

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,336
574
283
Finland
Watching this how long MN:s are listed and when they drop off the list, reporting back when they get unlisted.
Last start: 10:49...
OK, MN:s dropped about after one hour, not good if need restart every hour.
 

GilAlexander

Member
Jun 26, 2014
84
23
48
Dropped off after an hour too, just now.

Suddenly I got two payments on onyx2: 13 hours ago and now.
 
Last edited by a moderator: