Search results

  1. codablock

    v13.0 Testing

    v0.13.0.0-rc2 has just been released. Please upgrade ASAP as otherwise you'll fork away. DIP3 is activating in a few blocks.
  2. codablock

    v13.0 Testing

    Working on this right now (at least for p2pool).
  3. codablock

    v13.0 Testing

    Yeah what I wrote about hardware wallet support was probably misleading, going to edit that. Also, please note that this is all for testnet where I assume most people don't use HW wallets (is that even supported on testnet?). For mainnet, we'll hopefully have the necessay DMT support to make...
  4. codablock

    v13.0 Testing

    Release candidate v0.13.0.0-rc11 is ready for testnet! :) Github release candidate: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc11 Release notes are not ready yet and will be prepared in the next few days. Post will be updated. Gitian sigs can be found here...
  5. codablock

    Secret Sharing and Threshold Signatures with BLS

    Actually, the involvement of random numbers in the signature generation has shown to be the weakest point in ECDSA based schemes. Many of the publicly known hacks were based on bad random number generation at the signing stage. So I'm happy to remove the randomness from signing and verification...
  6. codablock

    v12.3 Testing

    v0.12.3.0-rc5 has just been uploaded to Github.
  7. codablock

    v12.3 Testing

    Sorry, forget to mention one crucial thing for the double spend: It only applies to 0-conf+0-fee (actually, low-fee) transactions. Currently, when calling sendrawtransaction your node will accept low-fee transaction into the local mempool but then very likely fail to relay it. This is because...
  8. codablock

    v12.3 Testing

    0.12.3.0-rc4 has been released, please see the UPDATE in the top post.
  9. codablock

    v12.3 Testing

    v0.12.3.0-rc3 has just been uploaded to Github: https://github.com/dashpay/dash/releases/tag/v0.12.3.0-rc3 Please upgrade, this should fix the mixing issues people were seeing.
  10. codablock

    v12.3 Testing

    Can you try to disconnect one node after another until you get one on top that has a correct starting block height. All the nodes you are connected to are forked or on a too old version. startingheight is the block height reported by the node at the time of connecting to it. It's a good...
  11. codablock

    v12.3 Testing

    What does "Starting Block" of the first node that you're connected to say? And maybe the nodes after the first one?
  12. codablock

    v12.3 Testing

    Sync issue might happen if you got unlucky and your first connection was to a node which has forked away. These are most likely non-upgraded nodes which still run 12.2.x, which does not include the fixes we did after the ASICs were turned on on testnet. To fix it, disconnect the first node you...
  13. codablock

    v12.3 Testing

    That's from the Bitcoin backports and acts as a protection against trigger fingers. It kind of forces you to double check your TX or at least think 3 more seconds. I personally find it ok this way...never forget, in Crypto there is no "reverse my erroneous transaction" ;)
  14. codablock

    v12.3 Testing

    Do I understand you correct that everything is ok now? This is most likely because translations were already done and imported/merged before these features were merged. I would consider this a minor problem and assume that we're going to fix it with one of the future translation imports.
  15. codablock

    v12.3 Testing

    Hello everyone, UPDATE: 0.12.3.0-rc5 has been uploaded to Github: https://github.com/dashpay/dash/releases/tag/v0.12.3.0-rc5 I've also updated the links in this post. Please upgrade to the new version and issue mn-start on your masternodes. RC5 should fix the forking issues currently seen on...
  16. codablock

    v12.2 Testing

    A few of our devs are now running a script on their masternodes to feed the faucets with their tDASH MN rewards. http://test.faucet.masternode.io/ got quite a lot already.
  17. codablock

    Dash Community Q&A (2-Part Post)

    Several people are involved, including @QuantumExplorer, @thephez and me. We will release details in the next 2 weeks.
  18. codablock

    Testnet Issues: Header sync problem

    This is a known issue at the moment and being worked on. Someone has plugged his ASICs into testnet and generated so many blocks in one row that it resulted in a fork. Not sure why exactly the fork happened, but it seems to be connected to superblocks and MN reward payments. Didn't have much...
  19. codablock

    What's Going on at Dash?

    And I'm very happy that I don't have to work on these reports ;) Not a thing I'm known to be good at :D
  20. codablock

    What's Going on at Dash?

    Nathan is one of our most busy guys when it comes to managing all the different teams and topics. He is constantly present in all kinds of technical and team related discussions, holding a lot of stuff together. Don't underestimate the amount of work needed to hold all strings together in a...
Back
Top