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.
v0.10.16 - Onyx v2
- Thread starter eduffield
- Start date
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).
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...
Yeah currently the cost is quite high for something that has "zero-fees". :tongue:
Well, I am confident Evan will get it sorted in short order. He always does.
Well, I am confident Evan will get it sorted in short order. He always does.
I've fixed this in v0.10.16.13, just need the masternode operators to update againouch: 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
Fixed in v0.10.16.13, thanks!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
and/orCode:mn.UpdateLastSeen(lastUpdated);
move it inside next "if" https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L97
EDIT: http://jira.darkcoin.qa/browse/DRK-126
I was waiting for v.13 because UdjinM6 said he likes number 13, so I kinda knew it was coming.. lol
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
◦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:
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.
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.
I guess you meant 16.12 ?
A quick test showed 9 duplicates over here with v0.10.16.12.
changes from 16.13
https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L92
dsee that was sent from dseg will not move into this and will add multiple entries to MN list
https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L146
it's 16.14 out, I compiled by myself
eduffield
https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L92
dsee that was sent from dseg will not move into this and will add multiple entries to MN list
https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L146
it's 16.14 out, I compiled by myself
eduffield
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.
its kinda like looking over the shoulders of Evan while he is at work but he doesnt mind. eh, he doesnt.. right ?
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
- 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
Well... I'm not forcing him to push updates to github... and also - "fail faster" is the rule for success :tongue:its kinda like looking over the shoulders of Evan while he is at work but he doesnt mind. eh, he doesnt.. right ?
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.