Oh !! didnt know that. Cool ! Sorry for the false alarm
I did few times before (when we had troubles with MNs) but I don't keep irc running all the time... hmm.. I almost never keep it running actually...lol, I saw him say he was going to post on here so I had that shit on lockdown waiting for the post here
Sidenote, you ever pop into the #darkcoin channel??
It seems there is some kind of jitter in the list, as nodes dynamically enter and leave it. Judging on the list of payments your node received all is fine - the next payment should occur in the next hours.
So yeah, it seems like a cosmetic bug/minor bug of masternode list and how the peers maintain it. Peers should not remove nodes which have actively pinged durig the last 70mins. We will check that.
What does your MN say? './darkcoind masternode list | grep a.b.c.d:9999'My node disappeared once more from drk.mn and has not reappeared for some time now. Also I have not received a further payment for 3 days
What does your MN say? './darkcoind masternode list | grep a.b.c.d:9999'
drk.mn is not the Word of God, its a site that displays info collected from scripts that query elbereths MNs, sometimes those scrips flake out.
Check your MN is running at source first, then go from there.
I cannot restart now because it's already active ("masternode started remotely").The same - have not received payment after 1400 blocks, but my mn is active according to drk.mn. Will restart now.
Last payment was from 175179 block and the highest is 176685 now, delta is 1506."*:9999" : 1,
Looks fine from my local daemon and the one MN I checked on too.I cannot restart now because it's already active ("masternode started remotely").
Here's the address: https://bitinfocharts.com/darkcoin/address/XdUSY1bcm299hG6eciHRziZNYZ819fh8qb
I've send all except 1000drk vin from it two days ago, it coincided with turning to 30% payments. Nothing else was changed.
Looks active according to drk.mn (active duration: 1w4d4h59m25s), my local wallet and mn itself.
Last payment was from 175179 block and the highest is 176685 now, delta is 1506.
What's the problem? Lazy to change ip, mn privkey, address again.
Found "Status Check Failed (Any)" which is 0 for the last week (I'm using Amazon). Other graphics are uniform.Do your VPS logs/stats show any outages?
MN must be online (reachable) exactly when "my" block is mined?I'm wondering if your MN went down temporarily for some reason at the wrong time and missed its payment 'slot' ?
The liquidity provider setting randomly adjusts the amount of drk to anomymize. After it hits the target, it starts over with a new setting.Possible (small) bug?
I've been running 10.16.16 in the darksend "liquidity provider" mode, with the "-liquidityprovider=1 -anonymizedarkcoinamount=150" parameters on the wallet with 160drks, for the last 10 days or so (since it came out). In this time I've only got hit with 0.1drk charge 4 times, which is a great improvement over previous versions.
I have noticed, that display of the annonymized amount (darksend balance) is fluctuating. I am not sure how this is calculated, but after hundreds of denominations and darksend transactions (and I am not touching this wallet or its balance) I would expect the darksend balance to steadily grow and reach 150 at some point... But instead wallet is today showing darksend balance of 64, but a week ago it was over 120 DRK, and few days ago it was 50DRK...
I think that darksend balance is wrongfully calculated. Maybe balance calculation is based on last X transaction, and does not build on whole history... Could this be the case, or am I missing anything? I can try the -rescan or -reindex but not sure what would happen (in regard to darksend balance).
I can provide 1GB of debug.log on request (i am also using the -debug parameter) ... ?
EDIT: few hours later balance jumped to 119 drk again... vertoe eduffield UdjinM6
Quick idea (right now I'm at work and can't test this):
When the bad node registers let the other nodes ask THAT IP-address for the corresponding vin (or pubkey or whatever else is easy to access).
No correct answer, node not accepted.
- it's a honest node -> it will give you the correct answer
- it's the bad node -> the 'good' node (which owns the physical address) is connected (we don't talk about IP-spoofing here, don't we?) and gives you the wrong answer (it can't return the bad node's vin/pubkey/etc. because it has no idea what's going on).