Search results

My MNs are set to "donate" 100% of their income to a separate address that I control in order to make things much easier. I have noticed that there is one unintended consequence...I have no clue which masternode is generating the payments that I'm receiving at this "donation" address. Likewise...

This thread is nearly a year old. Everything works much differently now. There is a reference node that keeps track of MN payments and ensures that every MN gets paid in a round-robin type fashion.

No problem Udji--you do great work around here! Glad it's fixed =)

Me and a couple of other people posted on BCT about having gone 5d7h (in my case) without any payments. Evan replied, asking us to PM him our info. Within fifteen minutes, all my MNs and the other people's MNs were paid. I'm still not sure exactly what happened--both in terms of why I went so...

I'm not sure if anybody else is having this problem, but everytime I start dash-qt.exe on my Windows PC, it gets almost to the point of loading and then crashes with no error messages. When I run it again, it comes up without any problems.

eduffield UdjinM6 fernando All: I know this has been brought up before but I've never seen a definitive answer from a dev as to why this would or would not be feasible. With the implementation of pose scoring, it seems like we should be able to move to a Proof of Service model where...

Love #1!

FWIW I'm glad we are using DASH as the ticker rather than that ISO stuff. The whole BTC XBT thing is ridiculously confusing, especially to new members of the crypto community. Stick with one easy abbreviation and go from there. I respectfully submit that DASH is a lot easier for a newbie to...

I'm so confused right now. Is it any wonder MN operators aren't updating? We have network fragmentation, unstable releases that are causing MNs to crash, and now we have a fork. I'm sitting on 11.0.10 for now, and y'all can gripe at me all you want, but until I figure out what the hell is going...

IMO, all major updates (10.x to 11.x, InstantX implementation, etc.) need to be announced at least 24 hours in advance. Major updates (that might cause network issues) should have 72 hours notice, along with a note to upgrade ASAP. These ninja releases are not particularly conducive to fast...

I would suggest that it's a matter of priorities. Improving Darksend and releasing InstantX are higher on the list, at the moment. Start-many is a great thing, but it's trumped at the moment by other items of importance. As Oblox said, there has been progress in calling different wallet files...

I agree with this. Darkcoin's MN network should be sufficient to store and serve the blockchain even without any other nodes running on people's PCs, etc. We currently have 1230 MNs, all serving the complete blockchain, and Evan's target is 2,000 - 3,000 within the next year. So I'm not really...

With all this discussion on debug.log sizes, I went ahead and proactively deleted all my debug.logs on my MNs just to make sure my VPS' don't fill up. They were between 350MB and 900MB...significant but not problematic yet.

I'm confused...what is still broke?

Looks like user error on my part...I forgot to update my local darkcoin.exe from 16.6 to 16.15. Whoops! All is well now =)

On the remote or the local? P.S. I started them last night!

Anybody have any idea why my MNs are not showing on the MN list? I've updated my MNs to 10.16.15 and I did "masternode start" from local and got "masternode successfully started."

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.

Updated three MNs. One shows other masternodes on the network; the other two don't. Going to wait and see if it's a propagation delay. EDIT: Propagated to a second masternode. Still waiting on my third. So I'm thinking it's fine!

Gotcha. Thanks!