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

Recent content by Figlmüller

  1. Figlmüller

    Dash Core v18.2.2 (Hotfix) Released, All nodes, please update ASAP

    I don't think that this is weird, considering their branching strategy. Also, the releases are properly signed. Gitian builds also check out. The lack of official announcement and contradicting information on the tagged release VS the README (one highly recommending the update, the other...
  2. Figlmüller

    Dash Core v18.0.1 Released

    I also noticed that. On the first launch when building the block index, dashd would show around 5GB resident size, allocating around 10GB in total. Restarting dashd after the initial rebuild would let it return to normal levels and stop my monitoring from sending me SMS every 15 minutes x)...
  3. Figlmüller

    Dash Core v18.0.1 Released

    Sorry, I was talking about dashd and dash-cli being used headless as masternodes on Linux. All images use en_US.UTF-8 as their locale and I have to override it to C by setting the LC_ALL env var. Using Debian LTS (currently 10). Related issue in bitcoin After about when dash/darkcoin stopped...
  4. Figlmüller

    Dash Core v18.0.1 Released

    Looks like the latest update to dashd (v18) reintroduced the locale issues, causing the process to terminate with: std::terminate() called due to unhandled exception Exception: type=std::runtime_error, what="locale::facet::_S_create_c_locale name not valid" unless the locale is automatically...
  5. Figlmüller

    Dash Core v0.14 on Mainnet

    What's the point in restarting masternodes regularly? Using the stop command or by killing the process with a SIGTERM? I generally would recommend to use scripts which only start the daemon when it is not running (based on the PID file or by process name in a single node setup).
  6. Figlmüller

    Dash Core v0.14 on Mainnet

    No PoSe penalty problems here either, except for usual DoS Attacks which require proper mitigation.
  7. Figlmüller

    Dash Core v0.14 on Mainnet

    Build & update worked seamlessly. Thanks!
  8. Figlmüller

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

    Alright, looks like I missed that. I'm sorry. I'll take that claim back :)
  9. Figlmüller

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

    When trying to register we came across the following error message, which does not tell what's exactly wrong: bad-protx-key-not-same (code 16) (code -1) But the sources reveal the following: if (!deterministicMNManager->IsDeterministicMNsSporkActive(pindexPrev->nHeight)) {...
  10. Figlmüller

    Bitmain slows down

    To me, at least here in central Europe it seems to be dead. Most people I know did GPU Mining at home with a few rigs (50-100 GPUs) back in the days - they mined the most profitable coin and did some trading. That was years ago. But there are still some people mining with ASICs - and they are...
  11. Figlmüller

    Dash Core v0.13 on Mainnet

    Okay, thanks. Maintaining JSON scheme validity seems reasonable :) Btw, do you know what measures are in place to verify the resources loaded and compiled by the new `depends` system? Previously we just used the dependencies installed on the build server which we could have audited (by...
  12. Figlmüller

    Dash Core v0.13 on Mainnet

    Thanks for your explanation and clarifying the order of the steps! I have a few more questions: If one has not sent the registration yet, how come the fields "owneraddress" and "votingaddress" are already filled out? (according to the masternode list) Where do the addresses come from (after...
  13. Figlmüller

    Dash Core v0.13 on Mainnet

    Hmm, ok. The build works fine here with the new depends arch. Looks like the libraries have been linked statically - thus increasing the binary size. LDD shows no deps on local libs except the essential ones (libc, ...) Anyways, what is the supposed way to start a masternode now? The protocol...
  14. Figlmüller

    Dash Core v0.13 on Mainnet

    Hi, I figured that out too. The deps took ages to compile. Is there a way to exclude qt? And: I used BerkleyDB > 4.8 before - this will be in conflict now, as the "depends" contain BerkleyDB 4.8, right? Also, even though proper dependencies are being used to build dash-core - they are still...
  15. Figlmüller

    Dash Core v0.13 on Mainnet

    Hi, I'm unable to compile Dash 0.13.0 due to the following error: CXX bls/libdashconsensus_la-bls.lo In file included from bls/bls.cpp:5:0: bls/bls.h:14:27: fatal error: chiabls/bls.hpp: No such file or directory #include <chiabls/bls.hpp> ^ compilation...
Back
Top