• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Search results

  1. flare

    Dash Ninja Related Problems

    Should be resolved by now
  2. flare

    Setting up a node that mine only with 1 thread

    Ya, we absolutely have to protect the ASIC miners from the CPU miners... sigh. Yup, wars have been started over less... *sigh* The sources are here --> https://github.com/dashpay/dash/pull/1790/commits/fa03411150fcb3058e0e9ed5de632b4a2b5dd4f8 - we have merged/wiped them as backport...
  3. flare

    Dash Core v0.14 on Mainnet

    I'm quite sure the delta comes from the # of revived nodes.
  4. flare

    Dash Core v0.14 on Mainnet

    camosoul is stressed out about almost everything related to Dash since he got "stabbed in the back" by Evan back in 2015. Since then he is complaining about everything and everyone - but regularly coming back if he runs into issues with his nodes and needs free support (free as in "free beer")...
  5. flare

    Dash Core v0.14 on Mainnet

    You have noticed that i posted this in context with contributing to DMT documentation? DMT is a open source tool written by @Bertrand256, unrelated to Core wallet. @masternube: I'd appreciate if you stop to quote me out of context and (mis)using my statement to make bold claims.
  6. flare

    Dash Core v0.14 on Mainnet

    $ free -h $ dash-cli masternode status $ dash-cli getinfo
  7. flare

    Dash Core v0.14 on Mainnet

    Hard to debug your issue without any further information.
  8. flare

    Dash Core v0.14 on Mainnet

    No, they are the same since Dash 12.1 - but some operators seem to run their nodes below minimum specs (1GB RAM) which is not sufficient since DKG got activated. 2GB RAM should still be on the safe side, i am hosting all my nodes on 4 GB RAM for more headroom. RAM is a commodity, you should not...
  9. flare

    Dash Core v0.14 on Mainnet

    The trend will revert soon: Nodes are getting updated, configurations reviewed and fixed, hardware/VMs upgraded to recommended specifications and firewall rules adjusted. I have seen worse drops in node count during the last 5 years :) Actually DKG works as expected: Finally a working PoSe...
  10. flare

    Dash Core v0.14 on Mainnet

    Not to forget all the other hosting services available https://docs.dash.org/de/latest/masternodes/hosting.html
  11. flare

    Dash Core v0.14 on Mainnet

    Past performance is not indicative of future results - but thanks for capturing some stats :) There are still 70 "closed port" nodes plus 70 outdated Dash v0.13 nodes registered in the network, so these 140 will be at least added to the body count the next days/weeks.
  12. flare

    Dash Core v0.14 on Mainnet

    Ya, we got it: You are the gaslighted victim, everyone else is a dickhead and anybody who can't see the issue you identified must be a idiot. Btw: So far every report of a banned node turned out to be either user error, misconfiguration or insufficient hardware resources. But as this does not...
  13. flare

    Dash Core v0.14 on Mainnet

    Technically you are right: The period has 260 blocks left. But as we are beyond the 80% threshold already we are past point of no return and i consider it as locked in :)
  14. flare

    Dash Core v0.14 on Mainnet

    Yup, we have locked in
  15. flare

    Dash Core v0.14 on Mainnet

    So you are saying everything is broken beyond repair and someone else should fix it asap?
  16. flare

    Dash Core v0.14 on Mainnet

    It's open source software, feel free to contribute to the documentation to improve it.
  17. flare

    Dash Core v0.14 on Mainnet

    I can only speak for myself, but for me the code is working flawless. The code was tested for weeks on testnet and was deployed to mainnet when we were sure of its production quality. On mainnet the PoSe system works as designed - and i am maintaining 100s of masternodes for my customers...
  18. flare

    Dash Core v0.14 on Mainnet

    What is the output of one of your non-banned, PoSe > 0 nodes for $ dash-cli masternode status?
  19. flare

    v14.0 Testing

    Thanks, will work on that tomorrow.
  20. flare

    Registered masternode and owner address changed

    That's because masternode list still shows the legacy list. The output will change when spork15 is activated on April 2nd. As long as protx info <regtx> shows the correct addresses you are fine dash-cli protx info 460ecc6c1ab6fce1ba4fd88384cae19b988bff82dfae90777ef17aad7c61fe23 {...
Back
Top