|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Qtum||1,173||a day ago||39||mit||C++|
|Qtum Core Wallet|
|Openbazaar Go||933||2 years ago||147||November 20, 2020||301||mit||Go|
|OpenBazaar 2.0 Server Daemon in Go|
|Awesome Lightning Network||909||2 months ago||8|
|⚡ A curated list of awesome Lightning Network projects for developers and crypto enthusiasts|
|Nkn||451||8||3 days ago||76||June 23, 2022||5||apache-2.0||Go|
|Official Go implementation of NKN full node.|
|INACTIVE. Browser based client for stellard. This repository is inactive. It points to the stellard network, which is being replaced by stellar-core. Please refer to the replacement repository, interstellar-client, which points to the stellar-core network.|
|Hellobitcoin||239||6 years ago||June 01, 2021||1||mit||Go|
|A collection of simple programs which can generate bitcoin wallets, create and sign transactions, and send transactions over the bitcoin network.|
|Avalanche Wallet||194||16 days ago||74||bsd-3-clause||Vue|
|The Avalanche web wallet|
|DDN, Data Delivery Network, a next generation blockchain system|
|Fuse Wallet||184||9 months ago||1||mit||Dart|
|Cross platform mobile Ethereum wallet based on Flutter|
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 Fastlane Main Network. This is the main network where the tokens hold value and should be guarded very carefully. If you are testing the network, or developing unstable software on Qtum, we highly recommend using either testnet or regtest mode.
The major features of the Qtum network include:
Note: Qtum Core is considered beta software. We make no warranties or guarantees of its security or stability.
These are some resources that might be helpful in understanding Qtum.
Basic usage resources:
General Info about Qtum:
Qtum Core is our primary mainnet wallet. It implements a full node and is capable of storing, validating, and distributing all history of the Qtum network. Qtum Core is considered the reference implementation for the Qtum network.
Qtum Core currently implements the following:
Qtum Core uses a full node model, and thus requires downloading the entire blockchain. If you do not need the entire blockchain, and do not intend on developing smart contracts, it may be more ideal to use an alternative wallet such as one of our light wallets that can be synchronized in a matter of seconds.
A browser wallet that supports the Ledger hardware wallet, offline cold wallet, restoration from mobile wallets, creation of QRC20 tokens and QRC1155 NFTs.
Web site https://qtumwallet.org
User documentation https://github.com/qtumproject/documents/tree/master/en/QTUM-WebWallet-usage
A light wallet that supports the Ledger and Trezor hardware wallets and is based on the well-known Electrum wallet software.
These wallets run on mobile devices and synchronize quickly.
Android Download: https://play.google.com/store/apps/details?id=org.qtum.newwallet
iOS Download: qtumproject/qtum-ios (open source, deprecated)
This light wallet runs in your Chrome browser as a browser extension, based on the popular MetaMask wallet.
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 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 Gitan Building
This is a quick start script for compiling Qtum on Ubuntu
sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils git cmake libboost-all-dev libgmp3-dev sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev # If you want to build the Qt GUI: sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler qrencode git clone https://github.com/qtumproject/qtum --recursive cd qtum # Note autogen will prompt to install some more dependencies if needed ./autogen.sh ./configure make -j2
Here is a brief description for compiling Qtum on CentOS, for more details please refer to the specific document
# Compiling boost manually sudo yum install python-devel bzip2-devel git clone https://github.com/boostorg/boost.git cd boost git checkout boost-1.66.0 git submodule update --init --recursive ./bootstrap.sh --prefix=/usr --libdir=/usr/lib64 ./b2 headers sudo ./b2 -j4 install # Installing Dependencies for Qtum sudo yum install epel-release sudo yum install libtool libdb4-cxx-devel openssl-devel libevent-devel gmp-devel # If you want to build the Qt GUI: sudo yum install qt5-qttools-devel protobuf-devel qrencode-devel # Building Qtum git clone --recursive https://github.com/qtumproject/qtum.git cd qtum ./autogen.sh ./configure make -j4
The commands in this guide should be executed in a Terminal application.
The built-in one is located in
Install the Mac OS command line tools:
When the popup appears, click
Then install Homebrew.
brew install cmake automake [email protected] libtool [email protected] miniupnpc openssl pkg-config protobuf [email protected] libevent imagemagick librsvg qrencode gmp
After installing all dependencies, make sure to run "brew link [email protected]" NOTE: This will work for building on Intel Macs and Apple Silicon Macs
NOTE: Building with Qt4 is still supported, however, could result in a broken UI. Building with Qt5 is recommended.
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
--without-gui to configure.
./autogen.sh ./configure make
It is recommended to build and run the unit tests:
Then you can either run the command-line daemon using
src/qtum-cli, or you can run the Qt GUI using
Qtum is GPLv3 licensed.
master branch is regularly built and tested, but is not guaranteed to be
completely stable. Tags are created
regularly to indicate new official, stable release versions of Qtum.
The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled in configure) with:
make check. Further details on running
and extending unit tests can be found in /src/test/README.md.
There are also regression and integration tests, written
These tests can be run (if the test dependencies are installed) with:
The CI (Continuous Integration) systems make sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.
Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.
Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.
Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.