Search results

  1. HinnomTX

    v0.10.15.x Testing

    IMHO, a revised blockchain based voting system is what you should strive for. The growth of the network will come from establishing completely decentralized, trustless relationships. A payment system that touts anonymity must be as trust-free as possible.
  2. HinnomTX

    v0.10.15.x Testing

    This appears to be a critical problem that needs to be solved. If we can share one blockchain among all the clients, surely there is a way to share one masternode list too. Perhaps this list cannot be updated in real time, but I bet it could be updated once per block. Then build in some...
  3. HinnomTX

    v0.10.15.x Testing

    Agreed. Personally, I'm more concerned about fixing the theft of MN payouts from cheating miners and other potential exploits than I'm concerned about low variance payments. As it stands, I would rather keep the flawed but 95% effective high variance (RC5) system we have today than move to a...
  4. HinnomTX

    v0.10.15.x Testing

    Sorry, but I don't think this is going to fly. The community is speaking to you and they are saying that the uber nodes run by 'trusted members of the community' are not acceptable. We've already tarnished the decentralized nature of Bitcoin by introducing masternodes. As a community, we have...
  5. HinnomTX

    v0.10.15.x Testing

    I suppose. Is there a way to empower the entire masternode network to implement a consensus style checkpoint? Sunny King referred to a wind down of checkpoints in PPC due to undesirable centralization (not sure if it ever came to pass). At the least, he did refer to a user enabled emergency...
  6. HinnomTX

    v0.10.15.x Testing

    Yep, much better now. :smile: { "178.62.203.249:19999" : 1, "92.222.10.179:19999" : 1, "107.170.168.162:19999" : 1, "188.226.225.170:19999" : 1, "198.50.148.87:19999" : 1, "69.160.84.100:19999" : 1, "107.170.157.216:19999" : 1, "176.126.247.191:19999" : 1...
  7. HinnomTX

    v0.10.15.x Testing

    My MN (108.61.198.220) matches $ ./darkcoind getblockhash 46877 00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26
  8. HinnomTX

    v0.10.15.x Testing

    If that's your MN list, that's not what I see at all: $ darkcoind getinfo { "version" : 101508, "protocolversion" : 70042, "walletversion" : 60000, "balance" : 19751.98471125, "darksend_balance" : 0.00000000, "blocks" : 46877, "timeoffset" : 0, "connections" : 19, "proxy" ...
  9. HinnomTX

    v0.10.15.x Testing

    Good question. Is there any plan to remove the checkpointing that's done now? It seems we are creeping toward a central authority by checkpointing and using 'privileged nodes'. Essentially we are building trust into the DNA of the coin, and that's scary.
  10. HinnomTX

    v0.10.15.x Testing

    This issue started out as a proposed gaming of the system by naxin: https://bitcointalk.org/index.php?topic=421615.msg9180781#msg9180781 12 hours later, Evan has rolled out the above fix. I love how this collaboration worked out.
  11. HinnomTX

    Please Update To v10.14.1 - Masternode Security Update

    Here is a workaround, and a solution: http://www.reddit.com/r/DRKCoin/comments/2iaajy/stuck_at_loading_wallet_on_os_x_1095_after/
  12. HinnomTX

    v0.10.15.x Testing

    This bug is being tracked here: http://jira.darkcoin.qa/browse/DRK-97
  13. HinnomTX

    Please Update To v10.14.1 - Masternode Security Update

    The rogue client is not actually a masternode owner. He/she is not staking any coins for the exploit. He/she can keep the exploit running indefinitely. However, the rogue's future earnings will evaporate as more peers upgrade to 0.10.14.x. There is a stricter version of masternode payment...
  14. HinnomTX

    v0.10.15.x Testing

    I restarted a test MN. Here's what I see at the command line: nBlockHeight2 44272 44461 nBlockHeight2 44273 44461 nBlockHeight2 44273 44461 nBlockHeight2 44274 44461 nBlockHeight2 44274 44461 nBlockHeight2 44274 44461 Is this an issue? Note here's my getinfo: { "version" : 101501...
  15. HinnomTX

    Please Update To v10.14.1 - Masternode Security Update

    You can still wear a black hat (or helmet) if you want to. With our combined strength, we can end this destructive conflict, and bring order to crypto currency.
  16. HinnomTX

    Please Update To v10.14.1 - Masternode Security Update

    Yeah, his run rate is about 78k DRK per year. Current salary in fiat would be $165k/year. Not bad for 8 hours of coding. I hope he turns white hat and joins the dev team.
  17. HinnomTX

    Please Update To v10.14.1 - Masternode Security Update

    Masternodes up to date! Fastest patch ever. Thanks!
  18. HinnomTX

    Development Update - Oct 1, 2014

    LOL! I knew my comment would conjure up pictures like that. I really only had two mining rigs in an office, but even with just two rigs the maintenance time was pretty significant. I have real respect for miners after my 6 month journey into the hobby.
  19. HinnomTX

    Development Update - Oct 1, 2014

    Ok, here are my two cents (having digested most of the proposals here). 1. Changing the coin dynamics at this stage is risky and appears a bit fascist to newcomers sizing up the coin. I think we should keep the mining PoW as-is or close to the status quo. 2. We don't know how the masternode...
  20. HinnomTX

    Development Update - Oct 1, 2014

    This definitely will lower the barrier to entry, and you can bet Vertoe will be a good actor. I haven't researched how these work though. Must the coins go to the pooling service? If so, there is a trust issue there. In NXT, one can delegate his/her proof of stake without losing control of the...
Back
Top