Qtum Development Update(01-01-2017)

  • qtum team


     1) Qtum Design Model:

    One of the biggest challenges of the Qtum project was integrating the Ethereum Virtual Machine with Bitcoin’s UTXO model. The EVM natively uses a state database, so we had to extend its capabilities to work with a UTXO based account model.

    While we decided to keep a state database for storing smart contracts code and data, our model uses UTXOs for all financial operations of the EVM. After finishing the design model, we moved to the implementation phase.

     2) Qtum Implementation:

    The foundation of Qtum is based on Bitcoin Core 0.13 and cpp-Ethereum EVM. After integrating the EVM code and dependencies for Bitcoin Core, we worked on implementing the Qtum model. This required additional support for Qtum Smart Contract creation, funding, and calling through the Bitcoin scripting language since we had to add UTXO support for the EVM.

    Other implementation details were also finished, including the Qtum gas model, EVM coin picking algorithm and much more.

    We now have a fully working implementation of the Qtum model which is currently being tested.

     3) Bitcoin Core Proof-of-Stake:

    The proof-of-stake (PoS 3.0) algorithm was ported from Blackcoin to Bitcoin core 0.13 and is now in the final stages of testing with dozens of nodes deployed.

    What’s next?

     1) Qtum wallets:

    Work is in progress to make new wallets for desktop and mobile Qtum users. For the desktop wallet, we are working on a dynamic and user-friendly interface which will include support for Smart Contract operations with an innovative design.

    Our Mobile wallet is also in the works, with versions for iOS and Android, the initial mobile versions are already in testing.

     2) Merging with Proof-of-Stake:

    We are currently working on merging the EVM and PoS branches of Qtum.

     3) Testing Qtum:

    We are extensively testing the Qtum implementation. In addition to Bitcoin and EVM automated tests, we are writing a Qtum specific test suite.

    Other than automated testing, manual testing is currently taking place as well.

    After in-house testing, we will request external code reviews and tests from independent software developers and companies.

    1. Releasing Qtum Sparknet (Testnet):

    Once our initial Qtum prototype has passed testing procedures, it will be time to launch the Qtum testnet, codenamed Sparknet. This will be the final real world test before the official release.

    —Happy New Year, from the Qtum Team

Log in to reply