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 {...
  21. flare

    Problem creating my own bootstrap file

    Simply download the latest bootstrap from https://github.com/UdjinM6/dash-bootstrap#for-mainnet and unzip it to you datadir - that should give you a bootstrap.dat file. Wipe everything else (files/directories) from the datadir (except wallet.dat and dash.conf of course) and start your wallet. It...
  22. flare

    Create a Mining Pool

    What kind of error did you get?
  23. flare

    Attention Dash Masternode Owners: Please register with the Deterministic Masternode List now

    Ya, that may be it. dash-cli is in my path, so you may need to add ./ in front of the calls Try for n in `./dash-cli protx list|head -n -1|tail -n +2` ; do n=${n//\"/} ; ./dash-cli protx info ${n//,} ; done | grep service|sort assuming that dash-cli is in your current directory.
  24. flare

    Attention Dash Masternode Owners: Please register with the Deterministic Masternode List now

    What issue are you running into? Does $ for n in `dash-cli protx list|head -n -1|tail -n +2` ; do echo $n ; done Work for you?
  25. flare

    Attention Dash Masternode Owners: Please register with the Deterministic Masternode List now

    Number of registered nodes: $ dash-cli protx list|head -n -1|tail -n +2|wc -l List of IPs registered: $ for n in `dash-cli protx list|head -n -1|tail -n +2` ; do n=${n//\"/} ; dash-cli protx info ${n//,} ; done | grep service|sort
  26. flare

    $50 available to determine what is wrong with this block

    Thanks for the kind words, much appreciated - the crypto space is highly abrasive sometimes but we will continue to stick to our netiquette standards nevertheless.
  27. flare

    Looks like MasterNodes and Miners are taking a stand...

    Antpool started signalling as well, so 98% of net hashrate is on v0.13.0+ now. The new DIP3 period will start in 88 blocks, from there we need 3226 out of 4032 blocks with DIP3 flag set to lock in.
  28. flare

    Looks like MasterNodes and Miners are taking a stand...

    It's the small sample size plus the chart updating each 30mins - and not each hour. This makes the 1h datapoint jitter up and down during the hour. 1h MA --> last 23 blocks --> 1 block is +/- 4.5% So if we have a streak of 4 non-signalled blocks the datapoint will be 13.5% lower than the one...
  29. flare

    Looks like MasterNodes and Miners are taking a stand...

    Yup, small sample size + variance. I don't even look at the 1h moving average line :rolleyes:
  30. flare

    How to set up ec2 t1.micro Ubuntu for Masternode part 2/3

    Hi and welcome to the forum. If you have followed the guide to create the AWS instance you should still be able using the ubuntu account with the ssh-key you have created/downloaded there. If you did not save the ssh-key there will be no way of logging in to your instance.
  31. flare

    Dashd is not synching when downloaded from repository.

    Hi and welcome to the forum. Like you've already noticed, the version in the repo is outdated. Currently there is no newer version available from a ppa, so you will need to download the dashd/dash-cli binaries from github and install them manually. --> https://github.com/dashpay/dash/releases...
  32. flare

    v12.3 Testing

    Sent 10k - no need to give them back.
  33. flare

    PIVX/Dash masternode governance, building the worlds first decentralised partnerships

    Welcome back to our forum. Regarding your idea, I'd vote no: Some time ago a lead dev of PIVX (s3v3nh4cks) publicly claimed on Slack that "the project manager(s) of Dash who worked out the partnership with Coinfirm should be hanged". I strongly oppose this kind of call for violence/murder and...
  34. flare

    Dash Core Group Q2 2018 Summary Call - 10 August 2018

    It was clearly stated that the other questions will be answered here in the forum.
  35. flare

    Rate the Forum rules

    Thanks for the heads up, threads deleted - some times these slip through, please keep on reporting whenever you see them.
  36. flare

    Which masternodes voted and what exactly voted on various proposals (v2)

    Yes, as soon as someone finds time to add a routing layer for the masternode network - or keep a node list for each supported network stack. Due to Evolution this is not on our top priorities list though, so any contributions are welcome.
  37. flare

    Which masternodes voted and what exactly voted on various proposals (v2)

    Both are not disabled because of centralisation but for technical reasons: We don't have a working routing of messages between the different connected nodes as of yet. So a IPv4 client is not able to connect to a Tor/IPv6 masternode. And as this live connection is crucial for the mixing we have...
  38. flare

    Which masternodes voted and what exactly voted on various proposals (v2)

    I did not delete what he said, all his comments were deleted due to his account being suspended. It is not my job to keep backups of his posts, here are some excerpts from my email spamfolder: These were posted to https://github.com/dashpay/dash/pull/2083 - which is a pull request and as such...
  39. flare

    Which masternodes voted and what exactly voted on various proposals (v2)

    Demo is constantly spamming 230 people with off-topic messages in the dashpay github repo. He has been asked to stop it or his user will get reported to the Github admin team for violating the Github terms of services. --> https://github.com/dashpay/dash/pull/2083#issuecomment-393590786 As he...
  40. flare

    v12.2 Testing

    Resources are not the issue, Amazon just deprecated the AWS instance and i take the opportunity to clean up and update some backend stuff.