v0.10.16 - Onyx v2

flare

Grizzled Member
May 18, 2014
2,286
2,404
1,183
Germany
That's how it works
https://darkcointalk.org/threads/v10-16-onyx-v2.2982/page-16#post-29792
Wallet just reads IP + masternodeprivatekey from single line in masternode conf and takes the first vin that is available (contains unspent 1000 DRK) and use it to start masternode.
Then it repeats until the end of the file.
So there is no right or wrong public key for the ip address because there is no column for vin or corresponding public key in masternode.conf - they are not tied now.
This is why i don't use start-many in the current version - as long as you can't bind vins to IPs it's useless for me.
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Same, I've had five over the span of 2.5 hours doing 8 rounds and the sad part is the lower denominations are already through 8 rounds... I still have a 500 that is sitting in round 1 so I'd imagine there will be more .10 charges.
Oblox, are you talking about your Testnet wallet? My 500 got 8 rounds, but my total anonymized amount is only 699, not 1000.
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
Oblox, are you talking about your Testnet wallet? My 500 got 8 rounds, but my total anonymized amount is only 699, not 1000.
No, I'm talking mainnet (I had both going). My testnet wallet is done (849 for a 850 target).
 

UdjinM6

Official Dash Dev
Core Developer
Dash Core Group
May 20, 2014
3,639
3,537
1,183
Ok, I understand, thanks. Since there's no masternode stop-many command, is there any way to individually stop different masternodes in one wallet?
I'm not sure but I guess you can simply fill masternodeaddr and masternodeprivkey in local darkcoin.conf with appropriate info for that individual masternode and issue masternode stop command...
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,323
183
ouch: collaterals! (top wallet balance was static, bottom wallet had deposits occur across earlier ds rounds )
six fees occured on bottom wallet
(no internet outages, no stop/starting darksend)
both win-qt v0.10.16.12-gc588770-beta

I've fixed this in v0.10.16.13, just need the masternode operators to update again :)
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,323
183
Another find.

When any client start it ask at least 3 other nodes for full MN list https://github.com/darkcoin/darkcoin/blob/master/src/darksend.cpp#L1978
and get them by dsee messages https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L260
While first response will pass this loop https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L90
without entering there and will keep lastTimeSeen equal to received lastUpdated https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L141
next responses from other 2+ nodes will go inside loop and override lastTimeSeen with current time https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L95
giving every masternode another 70 minutes of "life" on this particular client. So when someone else will start his client and connect to this client to get MN list he will refresh time for every masternode in his own list again.
I think MNs could "drift" quite a while by this feature :)
Solution:
modify this line https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L95
to
Code:
mn.UpdateLastSeen(lastUpdated);
and/or
move it inside next "if" https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L97

EDIT: http://jira.darkcoin.qa/browse/DRK-126
Fixed in v0.10.16.13, thanks!
 

splawik21

Yeah, it's me....
Dash Core Group
Foundation Member
Dash Support Group
Apr 8, 2014
1,953
1,315
1,283
Evan will you write mass email to inform about the update or we will start to inform all?
 

qwizzie

Well-known Member
Aug 6, 2014
1,804
955
183
will this be a protocol version update (meaning restart MN from cold wallet) or not ?
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
eduffield, you might need v.14 next because oblox and I don't like the denominate amount 500 (seems very traceable) and you might have to increase the pair number to 4 or more....
 
Last edited by a moderator:
  • Like
Reactions: splawik21

qwizzie

Well-known Member
Aug 6, 2014
1,804
955
183
eduffield, when you have time can you pls adjust page 1 of the bitcointalk forum :

◦Masternode Status 2 : https://drk.mn/masternodes.htm

pls fix into

◦Masternode Status 2 :
https://drk.mn/masternodes.html <-- this ''l'' is missing right now)

and maybe put it on top of the MN links as its the only working link right now (or will be the only working link once you fixed it ;) )

thanks

qwizzie
 
Last edited by a moderator:

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
eduffield, you might need v.14 next because oblox and I don't like the denominate amount 500 (seems very traceable) and you might have to increase the pair number to 4 or more....
Yeah, hard to really say being that we did the test on testnet where two parties are involved, but the 500 seems rare as is and even from an initial denominating standpoint, breaking the 500 into five 100s makes sense. Nothing says 500 can't be added back in the future but right now, it would fix the speed and the narrowing of parties to reduce the 500 into the 100s. As for the increasing pairs to 4 or more--I wouldn't worry about that right now, especially with the usage as is. When more people are denominating, it would be worth looking into again at that time.
 
  • Like
Reactions: moli

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
will this be a protocol version update (meaning restart MN from cold wallet) or not ?
Doesn't look like any change in protocol. I won't be able to update until after work in a few hours but from what I am seeing on github, no bump.
 

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,341
575
283
Finland
Yeah, hard to really say being that we did the test on testnet where two parties are involved, but the 500 seems rare as is and even from an initial denominating standpoint, breaking the 500 into five 100s makes sense. Nothing says 500 can't be added back in the future but right now, it would fix the speed and the narrowing of parties to reduce the 500 into the 100s. As for the increasing pairs to 4 or more--I wouldn't worry about that right now, especially with the usage as is. When more people are denominating, it would be worth looking into again at that time.
Good point, i agree.
 

David

Well-known Member
Jun 21, 2014
618
628
163
Ah, thanks. Fixed in v15
Does this mean that v.15 is out, or do we have to wait for it to be compiled?

Also, on each forum page there is still a message saying that the latest version is 15.21 with a link.
 

crowning

Well-known Member
May 29, 2014
1,414
1,997
183
Alpha Centauri Bc
v0.10.16.15 is available!

- Fixed dsee timestamp drift (thx UdjinM6)
- 90%+ reduction in collateral charges, should happen every 20+ mixes.
- Changed ping time to 5m (would have to have 14 bad propagation events to fall off the list)

https://github.com/darkcoin/darkcoin

* In the process of compiling it
My friends sort and uniq still think there are 2 duplicates with v0.10.16.15, in this case Masternode 108.61.172.141 exists 2x.

Maybe a simple check of the existing Masternodes before adding a new one would be a good idea.
 
  • Like
Reactions: UdjinM6