This project is primarily developed on a community-hosted GitLab instance. Please visit the community GitLab repository for the latest updates, issues, and contributions.
Hive is a Graphene-based social blockchain that was created as a fork of Steem and born on the core idea of decentralization. Originally, Hive was announced on the Steem blockchain prior to the initial token airdrop. Hive did not have any ICO or mining period.
The Hive blockchain eliminates the elements of centralization and imbalanced control that plagued the Steem blockchain. Since its launch on March 20, 2020, Hive has been continuously growing and evolving. Hive's prime selling points are its decentralization, 3-second transaction speed, and ability to handle large volumes. It is an ideal platform for a variety of innovative projects focused on a broad range of fields, from open source development to games.
Hive serves as the operational home for all kinds of projects, companies, and applications. With a highly active and passionate community, Hive has become a thriving environment for both new and experienced developers to quickly bootstrap their applications. On top of this, Hive is extremely rewarding to content creators and curators alike.
The technical development of the Hive blockchain is carried out by a founding decentralized group of over 30 open source developers, many of whom were instrumental in creating Steem back in 2016. This core team is supported by a growing community of additional open source developers and witnesses.
- Developer Portal: https://developers.hive.io/
- Hive Fund
- Truly Decentralized Community
- Free Transactions (Resource Credits = Freemium Model)
- Fast Block Confirmations (3 seconds)
- One Block Irreversibility
- Time Delay Security (Vested Hive & Savings)
- Hierarchical Role Based Permissions (Keys)
- Integrated Token Allocation
- Lowest Entry-Barrier for User Adoption in the market
- Dozens of dApps already built on Hive and many more to come
- Currency symbol HIVE
- HBD - Hive's very own stable coin with a two-way peg
- Delegated Proof-of-Stake Consensus (DPoS)
- 10% APR inflation narrowing to 1% APR over 20 years
- 65% of inflation to authors/curators.
- 15% of inflation to stakeholders.
- 10% of inflation to block producers.
- 10% of inflation to Hive Fund.
Getting started with Hive is fairly simple. You can either choose to use pre-built Docker images, build with Docker manually, or build from source directly. All steps have been documented and while many different OSes are supported, the easiest one is Ubuntu 22.04 LTS.
Want to get up and running quickly? We offer pre-built Docker images for your convenience. More details can be found in our Quickstart Guide.
We strongly recommend using one of the pre-built Docker images or building Hive using Docker. Both processes are described in the Quickstart Guide.
However, if you prefer to build from source, we also provide build instructions for Linux (Ubuntu LTS).
Building a hived docker image is described in detail here: Building under Docker.
If you'd like to use our pre-built official binary images, download them from the Docker Hub registry with the specific version tag. For example, to use version 1.27.7, run:
docker pull hiveio/hive:1.27.7
Please note that the latest tag is not supported; you must explicitly specify the version tag to avoid issues with new versions that require replay.
A script is available to simplify the use of a docker run command by emulating direct hived usage: run_hived_img.sh. This script is the recommended method for launching the hived Docker container.
General usage: run_hived_img.sh <docker_img> [OPTION[=VALUE]]... [<hived_option>]...
Read more about using run_hived_img.sh to explore its usage in various scenarios.
We provide a basic cli wallet for interfacing with hived. The wallet is self-documented via command line help. The node you connect to via the cli wallet needs to be running the account_by_key_api, condenser_api, database_api, account_history_api, wallet_bridge_api plugins and needs to be configured to accept WebSocket connections via webserver-ws-endpoint.
The cli_wallet offers two operating modes:
- interactive mode: commands are entered on an interactive command line
- daemon mode: wallet commands are sent via RPC calls. In daemon mode it is important to specify which IP addresses are allowed to establish connections to the wallet's HTTP server. See
--rpc-http-endpoint,--daemon,--rpc-http-allowipoptions for details.
To prepare transactions, you need to execute a few setup steps in the cli_wallet:
- use set_password call to establish a password protecting your wallet from unauthorized access
- use unlock to turn on full-operation mode in the wallet
- import private key(s) using import_key "WIF-key" command
Keys and password are stored in the wallet.json file.
See doc/devs/testing.md for testing build targets and info on how to use lcov to check code coverage of tests.
Run hived --dump-config to generate a data directory and a config file. The default data directory location is ~/.hived. If you want to modify the config to your liking, we have example config used in the docker image. All options will be present in the default config file and there may be more options that need to be changed from the docker configs (some of the options actually used in images are configured via command line).
A list of some seed nodes to get you started can be found in doc/seednodes.txt.
This same file is baked into the binary and can be overridden by --p2p-seed-node
command option set to a whitespace-delimited list of seed nodes (with port).
Running a Hive consensus node requires the following hardware resources:
- data directory to hold a blockchain file(s) (~550GB of disk storage is required)
- storage to hold a shared memory file (~30GB of memory is required at the moment to store state data)
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.