crowning Thanks for updating http://178.254.18.153/~pub/masternode_count.png - V3 masternode count currently at 230 and catching up
Waiting for elbereth to update drk.mn
Perfect! Can you lower the update time to 15mins until drk.mn has been updated?For the records: http://178.254.18.153/~pub/Darkcoin/masternode_locations.html is updated as well, so if someone likes to check if other clients (or in this case, MY client) see his/her Masternode you can check there.
Perfect! Can you lower the update time to 15mins until drk.mn has been updated?
Maybe you can create a stripped down version, just showing the IPs without geolocationDone. I'll leave it at that for the rest of the day.
I'll change it back to 60 minutes once the network is stable again, because I fear the geo-location provider will ban me when I create too much traffic.
I had to switch the provider already 3x....
Nodes offline until broadcast/announce bug and fragmentation are fixed.
My guess is that the changes related to making MNs more pingable, somehow islanded the announce call from start-many. Start-many does all it's stuff, but calls the announcement and the name of that process has changed. It's untrapped, so no output except telling me that all is well while it does nothing instead.
No idea why I'm seeing shards tho...
Cool! One more pair of eyes and hands would be very helpful! :smile:I can confirm this, had the same problem. Had nothing but issues so far using start-many so I decided to move the funds to seperate wallets again.
I intend to review the code next week and submit a pull request for better start-many support. I'm thinking of adding the transaction and output index as a parameter for each masternode in masternode.conf so that one can manage each vin and associated masternode individually from the same wallet. Individual masternodes could then also be started/stopped from the same wallet. Any feedback is appreciated.
Cool! One more pair of eyes and hands would be very helpful! :smile:
Drop a link to pull request there <link> when you have it :wink:
I don't use the start-many as I know it hasn't really been a targeted feature for full functionality, however, with the new -wallet argument, it's as easy as using the -conf and -wallet arguments in a shortcut (all OS's support them) adjusted for each masternode's config and respective wallet file. I opted not to use the -datadir argument as I wanted to use one blockchain instead of having a folder for each. Yes that means I have to load each masternode manually but it's far better than renaming wallet files to wallet.dat and specifying which config to load. When I'm done, I just delete the wallet and config files from the computer and go back on with my day.The only reason we were getting this high MN counts was because of start-many... The coins needed are already out there. I don't want to throw stones, but neglecting this most obvious thing while claiming to want to get MN count up seems more like artificially keeping the pie slices fat... More MNs is bad in the eyes of those already running them... Be that the case or not, that's how it looks, and it's been looking that way for many months. The Ouija Board/Market Watcher types wonder why the price doesn't move but we surge almost 50% in nodes? Cuz the coins are already held, but like me, who wants to dick around copying dozens of files full of money and make just one mistake... No. We don't do that with our money. Go juggle stacks of hundred dollar bills in a tornado, go ahead, I'll watch... I ain't fuckin' doing it, and neither are a lot of other people. They're not stupid.
The market doesn't have to move one duff to double the MN count. So, why are we keeping thos duffs out of MNs while saying we want more MNs? Did you not see the adjacent blocks of MN IPs going up in stacks at a time?
I wouldn't suggest it as true, but it makes DRK look like it's devs are up to something... Perception.
Oh, and was that 2000DRK mix limit supposed to make it into the non-test-net release? Because it did... I was going to mix out a bunch of coins I had geocached and set up a few more racks of MNs, but grr.... MN tool I need is busted, mixing won't let me mix big piles... RAWR!
The only reason we were getting this high MN counts was because of start-many... The coins needed are already out there. I don't want to throw stones, but neglecting this most obvious thing while claiming to want to get MN count up seems more like artificially keeping the pie slices fat... More MNs is bad in the eyes of those already running them... Be that the case or not, that's how it looks, and it's been looking that way for many months. The Ouija Board/Market Watcher types wonder why the price doesn't move but we surge almost 50% in nodes? Cuz the coins are already held, but like me, who wants to dick around copying dozens of files full of money and make just one mistake... No. We don't do that with our money. Go juggle stacks of hundred dollar bills in a tornado, go ahead, I'll watch... I ain't fuckin' doing it, and neither are a lot of other people. They're not stupid.
The market doesn't have to move one duff to double the MN count. So, why are we keeping thos duffs out of MNs while saying we want more MNs? Did you not see the adjacent blocks of MN IPs going up in stacks at a time?
I wouldn't suggest it as true, but it makes DRK look like it's devs are up to something... Perception.
Oh, and was that 2000DRK mix limit supposed to make it into the non-test-net release? Because it did... I was going to mix out a bunch of coins I had geocached and set up a few more racks of MNs, but grr.... MN tool I need is busted, mixing won't let me mix big piles... RAWR!