Qtum (QRC) - Mainnet Ignition v1.1 - Qtum QRC Token Support

  • About Qtum and Mainnet Ignition

    Qtum is a decentralized blockchain project built on Bitcoin's UTXO model, with support for Ethereum Virtual Machine based smart contracts, and secured by a proof of stake consensus model. It achieves this through the revolutionary Account Abstraction Layer which allows the EVM to communicate with Qtum's Bitcoin-like UTXO blockchain. For more general information about Qtum as well as links to join our community, go to https://qtum.org

    Welcome to the Qtum Ignition Main Network. This is the main network where the tokens hold value and should be guarded very carefully. There will be a testnet setup soon for developers, in the meantime you can use -regtest mode for testing needs. We will announce details about the token swap from QTUM ERC20 coins to QTUM mainnet tokens soon, watch our website for details about that.

    The major features implemented in Qtum Ignition include:

    1. The Ethereum Virtual Machine, which allows for compatibility with most existing Solidity based smart contracts.
    2. The Smart Staking Protocol is complete, which is an optimized Proof of Stake implementation designed for a smart contract platform (however, smart contracts can not participate in staking yet).
    3. An early and basic smart contract GUI has been implemented that can be used for creating contracts, sending data and Qtum to them, and checking their status by executing them locally. This functionality is similar to Mist's UI right now, but it is still an early version. We will be working on this more to improve it.
    4. Regtest mode, which is ideal for developers who wish to create their own private blockchain. It is tuned specifically to make development easier. It will stake blocks automatically every 30 seconds, and can generate proof-of-work blocks instantly as needed.
    5. The Decentralized Governance Protocol is completely implemented and functional, which allows certain network parameters to be modified without a fork.

    For more technical information for how to start developing with Qtum please read the Guidefaucet smart contract (it hasn't yet been updated for Mainnet for obvious reasons, but all the instructions are the same and you can try them in regtest mode)

    Note: Qtum Core is considered beta software. We make no warranties or guarantees of its security or stability.

    Update History

    • v1.1.0: Add GUI support Qtum QRC tokens, allowing full management of tokens on the Qtum blockchain from the Qt wallet
      • Sending to a contract no longer requires ABI data, allowing easy participation in simple crowdsale contracts
    • v1.0.4: Fix bug where certain circumstances when staking could cause the displayed balance to be inaccurate until completely redownloading the blockchain.
    • v1.0.3: Fix staker bug that reported false messages; slightly increases staking performance; optimize staker parameters; fix white send button in GUI
    • v1.0.2: Various UI fixes, minor gas overflow consensus fix, per-txout exploit fix, testnet mode setup and functioning
    • v1.0.1: Fixed network magic bytes and minimum version to ensure the main network does not conflict with the Skynet network
    • v1.0: Initial release

    Reindex Required When Upgrading from v1.0.1

    When you first start the Qtum 1.0.2 GUI wallet after using Qtum v1.0.1 it will prompt you that it must reindex the database. This is normal and is a result of switching our internal database format from per-transaction to per-txout. If you use qtumd -daemon it will silently fail to start. You need to use qtumd -daemon -reindex in this case.

    Qtum Documentation and Usage Resources

    Basic usage resources:

    Development resources:

    General Info about Qtum:


    The easiest way to get started with Qtum is to simply download the binaries below. To give a brief breakdown of the different versions available:


    • qtum-0.14.6-win64.zipqtum-0.14.6-win64-setup-unsigned.exe - A version of Qtum-Qt, qtumd, and qtum-cli built for 64bit x86 machines using Windows. This includes an installer and will install Qtum system wide.
    • qtum-0.14.6-win32.zip - A version of Qtum-Qt, qtumd, and qtum-cli built for 32bit x86 machines using Windows. If you have an older Windows computer and don't care about installing Qtum system-wide,
    • qtum-0.14.6-win32-setup-unsigned.exe - A version of Qtum-Qt, qtumd, and qtum-cli built for 32bit x86 machines using Windows. This includes an installer and will install Qtum system wide. If you have an older Windows computer and want to install Qtum then this is for you.


    • qtum-0.14.6-osx64.tar.gz - A version of Qtum-Qt, qtumd, and qtum-cli built for 64bit x86 machines using OSX. If you use a modern Mac and want development tools, this is what you want; we do not support older 32bit or PowerPC based Macs.
    • qtum-0.14.6-osx-unsigned.dmg - A version of Qtum-Qt built for 64bit x86 machines using OSX in a .DMG installable format. If you use a modern Mac and aren't a developer, this is what you want; we do not support older 32bit or PowerPC based Macs.


    • qtum-0.14.6-i686-pc-linux-gnu.tar.gz - A version of Qtum-Qt, qtumd, and qtum-cli built for 32bit x86 PC platforms running Linux. This is probably what you want for older computers running Linux
    • qtum-0.14.6-x86_64-linux-gnu.tar.gz - A version of Qtum-Qt, qtumd, and qtum-cli built for 64bit x86 PC platforms running Linux. This is probably what you want for any modern PC or server running Linux
    • qtum-0.14.6-arm-linux-gnueabihf.tar.gz - A version of qtumd and qtum-cli built for 32bit ARM platforms using Linux. This includes the Raspberry Pi and many of it's clones
    • qtum-0.14.6-aarch64-linux-gnu.tar.gz - A version of qtumd and qtum-cli built for 64bit ARM platforms using Linux

    Below in the full list of binaries, there are also versions that include debug symbols. These are useful for developers, but will run slower and are significantly larger to download.

    Build Qtum Core

    If you want to build it from source, it's recommended to follow the specific "build" documentation for your platform. But mostly it boils down to the following:

    1. Clone the qtum source code and cd into qtum

       git clone --recursive https://github.com/qtumproject/qtum.git
       cd qtum
    2. Build qtum-core:

      Configure and build the headless qtum binaries as well as the GUI (if Qt is found).

      You can disable the GUI build by passing --without-gui to configure.

    3. It is recommended to build and run the unit tests to ensure everything is working correctly:

      make check

    If you encounter an error like:

    make[2]: *** No rule to make target ‘cpp-ethereum/utils/libscrypt/b64.c’, needed by ‘cpp-ethereum/utils/libscrypt/libbitcoinconsensus_la-b64.lo’. Stop.

    Then you did not checkout the cpp-ethereum submodule for Qtum. To do that, simply:

    cd qtum
    git submodule update --init --recursive

    Validate and Reproduce Binaries

    Qtum uses a tool called Gitian to make reproducible builds that can be verified by anyone. Instructions on setting up a Gitian VM and building Qtum are provided in doc/gitian-building.md

    Community Resources

    Make sure to check out these resources as well for more information and to keep up to date with all the latest news about Qtum. At least 1 developer is always around, so if you're developing on Qtum and need help, we'd love to welcome you to our community.

    Qtum Smart Contract Limitations

    • EVM smart contracts can not receive coins from or send coins to any address type other than pay-to-pubkeyhash (starts with Q) addresses. This is due to a limitation in the EVM
    • Contracts are not allowed to create contracts with an initial endowment of coins. The contract must first be created, and then be sent coins in a separate transaction. Humans are also not allowed to create contracts with an initial endowment of coins.
    • Although all of the infrastructure is present, Qtum Core does not currently parse Solidity event data. You must parse this yourself using either searchlogs or -record-log-opcodes features.
    • It is not possible to send a contract coins without also executing the contract. This is also the case of Ethereum. This was promised in earlier discussions and technically does work, but due to lack of time for testing this feature was disabled. We hope to reenable this feature with release of the x86 virtual machine in 2018.
    • In Qtum there can be multiple addresses used to create a proof-of-stake block. However, the EVM can only see the first output using the coinbase operation in Solidity (this address is also the one registered for the continuous staker rewards after 500 blocks).

    Hash Validation

    -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 If you would like to validate that the binaries you download are exactly the same as those provided and built by the Qtum team, then you can compare your binaries to the following sha256sum hashes: f969b3f59a8a62bed2419766580cf0a9849db141e5fb22adc538ba27dc26f2ba qtum-0.14.6-osx-unsigned.dmg 143cc4dd0dc7c27d37f0577be90244c27d9bc774f1ad2f880cd6b2d2eff48db3 qtum-0.14.6-osx-unsigned.tar.gz 58de033b5f091de665e2d50e1c18adbf2867451c555e187582f36238b4dfcbfa qtum-0.14.6-osx64.tar.gz 1a4f407ad165177a9950c33053778e44c5b1a1d5d913a8fcd27f7ada698087f8 src/qtum-0.14.6.tar.gz 9aac11978cf3aa1fa814885253fdb0c59b3d050113597786d07446929dc6b01a qtum-osx-0.14-res.yml 2a404b42149dc1ef617b1d582e5690cb2d4cb386e4e4e6aa94fc412c8017ef41685 qtum-0.14.6-aarch64-linux-gnu-debug.tar.gz 8dae9d9a8bc38d18b53bafa1ac4a87c93b3308cea69c10558c04cbfe155249de qtum-0.14.6-aarch64-linux-gnu.tar.gz 206a6b32953ebafa5cb26c435334fba780222a84860025953cefe623487614b1 qtum-0.14.6-arm-linux-gnueabihf-debug.tar.gz 1063aa207afa9bf61e4633a28d8ec8c3d2f72f8cc43e284f58346a8a96bf9970 qtum-0.14.6-arm-linux-gnueabihf.tar.gz d2eb64462f63bd5e83a822103d0edb6d6be1ed2c1bc91ac26000dfffb42d0a1b qtum-0.14.6-i686-pc-linux-gnu-debug.tar.gz e1a8790e4810c6a999fa76119b319f4cffaa336f3716477b02b00f77b1182eaf qtum-0.14.6-i686-pc-linux-gnu.tar.gz b267fe4342610e17351528d1334a427092f1e36479cd68e63d7e76ccc21e7445 qtum-0.14.6-x86_64-linux-gnu-debug.tar.gz 35122c1a05745aad43b6044c83a9d93c0c0725b2461c40eab5afd5dd598cd4ae qtum-0.14.6-x86_64-linux-gnu.tar.gz 1a4f407ad165177a9950c33053778e44c5b1a1d5d913a8fcd27f7ada698087f8 src/qtum-0.14.6.tar.gz 89484b7caa427959dfee542358489e7a1c50a840f286102af0a428e3cfd0891f qtum-linux-0.14-res.yml a1ebed92a95f69008116e55585deacea18279407bd6612664d1d349c4588a3a3 qtum-0.14.6-win-unsigned.tar.gz 818b32af02061c3c173b538701297018ba90c96a90d207837a7ee2071483ca39 qtum-0.14.6-win32-debug.zip 6c2d3d0bdb947cab3a3a4e360c007c25644ed58806edf42aa334af37431a664b qtum-0.14.6-win32-setup-unsigned.exe 9b5ab577dd843da6195d0d0d78f4676a468e56d73936c774cdebd970f2d24a23 qtum-0.14.6-win32.zip ce0e1d041a771bfd83a934208ca6fbc28f0cb5cbdc415d0d86d527c794900bb2 qtum-0.14.6-win64-debug.zip 28f5e68958eebb97499b6e150b922ede2cd6a80b4d385eeb19e073a38e066b33 qtum-0.14.6-win64-setup-unsigned.exe 715e65dc007a52d52dc1bb43a723cdd84a225d843c4c2786e8c402fdae3a0440 qtum-0.14.6-win64.zip 44c87b827304adef7febf9feaf39ef897eadaf42dbadf52e22be639dc47799a6 src/qtum-0.14.6.tar.gz bb8f6868c07e0aab8a6d9fd0f096b4c2a4e13651baf1b958bd9fe8c631ea2574 qtum-win-0.14-res.yml In addition, as of the time of this writing, VirusTotal detects 0 false positives on the Windows 32bit and 64bit zip files, and 1 false positive on the Windows 32bit and 64bit installer: installer win32: https://www.virustotal.com/#/f... 1 false positive ("unsafe" by Cylance) installer win64 https://www.virustotal.com/#/f... 1 false positive ("unsafe" by Cylance) zip win32 https://www.virustotal.com/#/f... 0 false positives zip win64 https://www.virustotal.com/#/f... 0 false positives You can validate this message is from Earlz at https://keybase.io/verify -----BEGIN PGP SIGNATURE----- Version: Keybase OpenPGP v2.0.76 Comment: https://keybase.io/crypto wsFcBAABCgAGBQJZ/N9fAAoJEAKXMK2l7Ra+GIIP/R/wOpXWb9/H2q0XJEgH9hKd RCtpzzNO+Qfbeg4gGLim2DRtfnlbvUnvXOCJSGMPDmUEc50e5r5saGwWLS0TYzQk SfyIbgMEHwMTrOI3Ri8V8P+T1vQKoXB1A7hYZJw8RpKg0ymu148SykEye6mlLqXj lon80axyE+qqphuGuDmnjvXCp1N7PifNCIZBTs5+G20By3j+1lcT6fL7+4aIDws4 P2dhQY3ZY6M4jPe7qp2LDCHZt/5foIcekaIZsg8foXVyVN5nPSq1v+SJLFpDrD18 0eF1xnxUeR1be1KJ7UfVOECHMLrwrWNhVlyYxgh03+qRg5Kx8KUK7yyyM5mg8wsO SFZDWiA5LjiHDsggq7utOyejWZQDqC22Yv198ALDaG6b4BISw1XMYz+8rg3tOrac cckMXLLQUdtYRpBPcXK3ItXFIOKbXFoQ+YMrHZrw780NAEEVWj0cKCa2JdCniRIP uohzRMuG+4wyK6uP+uK7E/BBjWz98mqn75WRuZIkMxIYbyxClz9hwxpLewkCssAt q5Z2/HP0xJDHDCFOYdsrwJzpN+HbQODqigzlf+Q97ukfJ8ZBcogPtyohh4oDJC2U dIq5Jj2KuXQpMpi7F1CYG+Oy295p67cjSoDg2w73+QayjDSUdKs0yWiNxjtAYLYr 9iG+3V1xROLj+cm0N9KL =+svp -----END PGP SIGNATURE-----



Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.