Qtum Release Mainnet Ignition v0.14.16 - Improvments and Bug fixes
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
-regtestmode 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:
- The Ethereum Virtual Machine, which allows for compatibility with most existing Solidity based smart contracts.
- 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).
- 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.
- 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.
- 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.
- v0.14.16 - Improvments and Bug fixes
- Fixed a bug where transactions with low fees would get stuck in the local mempool.
- Fix a bug with clearing cache of StorageResults
- Add contract support to "createrawtransaction" rpc call
- Add sender support to "sendtoaddress" rpc call
- v0.14.15 - Recommended Update
- Add EVM global variables to callcontract
- Update gitian build script
- Update CentOS build instructions
- Add exception data to TransactionReceipt
- Fixed a bug where the gas price could not be parsed correctly on certain platforms (reported by APIS)
- Fixed a bug where the logs were not reverted on disconnect block in certain cases
- v0.14.14 - Mandatory Update
- New Qt GUI
- Fix Qt wallet freeze when syncing from scratch with
- Fix a bug with cacheUTXO (hardfork at block 100000 in mainnet, 84500 in testnet)
- Add update checking functionality to Qt wallet
- Fix a bug in token transfers history dates
- Fix a bug with searchlogs rpc call
- Add an extra check when adding token addresses
- Fix compatibility with boost 1.66
- Add checkpoints
- Update nMinimumChainWork and defaultAssumeValid chain params
- Add minmempoolgaslimit startup argument
- Add Gitian build signatures
- v0.14.13 - Mandatory Update
- Fix a callcontract bug which in very specific cases could cause the node to fail to sync the blockchain
- Add ability to save and restore contract addresses and ABI data
- Make the token confirmation view data correct
- v0.14.12 - Recommended Update
- Added option to disable change address usage
- Fixed bug where heavy RPC usage could cause the wallet to crash
- v0.14.11 - Optional Update
- Changed our versioning scheme to be consistent and avoid the two version number confusion
- Add feature to restore wallet in the Qt wallet
- Add new RPC call "waitforlogs" that is particularly useful for Dapp developers
- Add long-polling support to the gettransaction RPC call
- v1.1.4 - Recommended update
- Fixed a bug that would cause syncing to stop
- Fixed a bug that would cause the wallet to crash when using -logevents
- v1.1.3 - Highly recommended update
- Fixed a bug that caused contact addresses to show in receive token address dropdown
- v1.1.2 - Optional update, but recommended if using QRC tokens
- Fixed a bug with token transactions where the transaction ID displayed was incorrect in the Qt wallet
- Allow adding 0 balance addresses as the token receiver in the Qt wallet
- v1.1.1: When sending to contracts, the sender address is now the default change address to reduce confusion; fix -salvagewallet so it works with token transactions
- 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 -daemonit will silently fail to start. You need to use
qtumd -daemon -reindexin this case.
Qtum Documentation and Usage Resources
Basic usage resources:
- Official Qtum Usage GuideUnofficial Qtum staking tutorial
- Unofficial Qtum staking tutorial on Raspberry Pi
- Unofficial guide for keeping your wallet safe
- Block explorer
- Unofficial block explorer
- Unofficial Raspberry Pi Web UIDeploying a custom token to Qtum
- Early example faucet contract
- Unofficial Qtum Hello World tutorial
General Info about Qtum:
- Mainnet event AMA
- Qtum's PoS vs CASPER
- Technical article explaining Qtum's PoS model in depth
- Unofficial What is Qtum article
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.15-win64.zipqtum-0.14.15-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.15-win32.zipqtum-0.14.15-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.15-osx64.tar.gzqtum-0.14.15-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.15-i686-pc-linux-gnu.tar.gzqtum-0.14.15-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.15-arm-linux-gnueabihf.tar.gzqtum-0.14.15-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:
Clone the qtum source code and cd into
git clone --recursive https://github.com/qtumproject/qtum.git cd qtum
Configure and build the headless qtum binaries as well as the GUI (if Qt is found).
You can disable the GUI build by passing
./autogen.sh ./configure make
It is recommended to build and run the unit tests to ensure everything is working correctly:
If you encounter an error like:
make: *** 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/r/Qtum on Reddit
- Qtum Telegram Group
- @QtumOfficial on Twitter
- Qtum on Facebook
- Qtum Forum
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
- 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
coinbaseoperation in Solidity (this address is also the one registered for the continuous staker rewards after 500 blocks).
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: fb0043ccfd64a6ab6b17f3b76f8c2001c161879306fc8b79229191f432df4d10 qtum-0.14.16-osx-unsigned.dmg c8d946aa1d47146724f5fcb7945674424170102c639dd84ca113db9a78948563 qtum-0.14.16-osx-unsigned.tar.gz 0d11bf7c15694eb0ce429c9a4e9032020d4530f4b10dc9b23f5998fece3fe9b0 qtum-0.14.16-osx64.tar.gz 5d621c1dbe3086fade0fb40f5bba0bb7b7b4405423a95b875990269168fc022d src/qtum-0.14.16.tar.gz e41c006e64a1ad82c083598a1df168b7b08cded5d4813a554da109c3c1f2a81f qtum-osx-0.14-res.yml bf823903871e5732810ff6a02b73fef867bfe48574c1e29e92dc201902ebd7b9 qtum-0.14.16-aarch64-linux-gnu-debug.tar.gz c7cd750f3ada4e4024a4d95c89bc75c16c95aa1faa94dd282a79c0cdbdc50363 qtum-0.14.16-aarch64-linux-gnu.tar.gz f9d43ad5d50e156287f161a07589dcf047fc3125ce40d9f51007a541eb10c1b8 qtum-0.14.16-arm-linux-gnueabihf-debug.tar.gz cbf88206bfff102fe3c440357a2b533460a0c75176c3bed4071daea85130d877 qtum-0.14.16-arm-linux-gnueabihf.tar.gz b8caeadab66096eda1b8a95411ce6403dc4cc7c60e8ddd33c7c3e94f81a25e38 qtum-0.14.16-i686-pc-linux-gnu-debug.tar.gz 57f4a98c9c5053baa7029eaafa14d5080c8a566960efca372fa607dee7c42234 qtum-0.14.16-i686-pc-linux-gnu.tar.gz a740adea6ee5148dc357f91493a70adc09faedda8ebe9e1401e73fedda9a029d qtum-0.14.16-x86_64-linux-gnu-debug.tar.gz 3b77a798aa846fa14fd5eb677161e94ae8f41ea8fcb760356cdab129bb5e065f qtum-0.14.16-x86_64-linux-gnu.tar.gz 5d621c1dbe3086fade0fb40f5bba0bb7b7b4405423a95b875990269168fc022d src/qtum-0.14.16.tar.gz e766dc418e8aa48c767f54ff80725eed8a61265a4f19c965229e435df85656f9 qtum-linux-0.14-res.yml e9cd6ed753eb0bf83b0a083dc0cbb1ddf9794a8fb963a37677b9b2377bd7826f qtum-0.14.16-win-unsigned.tar.gz 7476ae4f9124f6bd72165e33b6232fab1be5852581c831d235cd70f439fb5af0 qtum-0.14.16-win32-debug.zip e9d6c499f47a9a847a22809262cde1ffdb9c840c03d9ecf814564792119b6a87 qtum-0.14.16-win32-setup-unsigned.exe 7e5a6947c18d1216a7d864da66be16b9526c2f5f857e983be0eccde8d4e5196a qtum-0.14.16-win32.zip ec05a3668ea88666efb3f31e2c4697f02d8744d80d0b71573bf03e1111a5d082 qtum-0.14.16-win64-debug.zip 620f2bdfd496748f1ed8b62289fc35543370f6177d4510b6a7b73b991e1c1121 qtum-0.14.16-win64-setup-unsigned.exe c525893ddfd0d803b8eff8b5b5aa4547ad120087cd009dfc8f4791f94560d9b3 qtum-0.14.16-win64.zip 55f106ba2428aad868dd5103f8ebd435f650e9abeee24ef64c1ef3acb580be15 src/qtum-0.14.16.tar.gz 7057cd3e1920b91738cc896bb4d858ffff064a44080616c1a27d14d36cb481c8 qtum-win-0.14-res.yml