The concept of BTCU is similar to the concept of the second cryptocurrency by capitalization - Ethereum. Like Ethereum, the Bitcoin Ultimatum blockchain provides smart contracts in the blockchain protocol as one of the important functions for the implementation of transactions and DAPP applications. The BTCU team sets itself the task of developing the direction of smart contracts and implementing atomic swap technology natively into the blockchain protocol to allow carry out transactions not only within the framework of a single blockchain protocol, but also interact with other protocols, which will globally expand the possibilities of this technology. The main goal is to make a hybrid of LPoS mining algorithm and PoA to make a real decentralizing infrastructure with limited validators.
BTCU Core is the original BTCU client and it builds the backbone of the network. However, it downloads and stores the entire history of BTCU transactions; depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more. Thankfully you only have to do this once.
The following are some helpful notes on how to run BTCU Core on your native platform.
Download from Releases latest version, unpack the files into a directory and run:
btcu-qt(GUI) orbtcud(headless)
Download from Releases latest version, unpack the files into a directory and run:
btcu-qt.exe(GUI) orbtcud.exe(headless)
Download from Releases latest version, unpack the files into a directory and run:
BTCU-Qt(GUI)
- See the documentation at the BTCU Wiki for help and more information.
The following are developer notes on how to build BTCU Core on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.
- Developer Notes
- Release Notes
- Release Process
- Translation Process
- Unit Tests
- Unauthenticated REST Interface
- Dnsseed Policy
Distributed under the MIT software license. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com), and UPnP software written by Thomas Bernard.