good to know
i was wondering what was going on as well
but most were zero payments or tiny amounts.
tiny amounts are still traceable though ?!
v0.10.16 - Onyx v2
- Thread starter eduffield
- Start date
good to know
i was wondering what was going on as well
but most were zero payments or tiny amounts.
tiny amounts are still traceable though ?!
499/8
It takes longer now to show up on Elberethzone's website now. Dont stress it, if its :1 then you're good.
I've heard Evan use the word 'weekly' when mentioning the .1 fee -- I should be good for five weeks now! lol
Ok thanks, I'll keep waiting to see if they eventually appear. But what about the fact that most of the ones that do appear on https://drk.mn show the wrong public key for the ip address? I think it's because when I tried to use start-many, some of my mns were stopped and some were already running, so it may have screwed things up?
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.
JGCMiner
Active member
Looking more closely at my transaction list, I also got hit with 3 0.1 fees in just 8 rounds. That is much more expensive compared to previously.
Evan, is this the intended behavior or do you think there may be a bug?
Ok, I understand, thanks. Since there's no masternode stop-many command, is there any way to individually stop different masternodes in one wallet?
oblox
Well-known member
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
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.
flare
Well-known member
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
Well-known member
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
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...
eduffield
Core Developer
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
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
Fixed in v0.10.16.13, thanks!
moli
Well-known member
Or you can do it for us .. hahaha