Skip to content
Snippets Groups Projects
Commit 64f14f76 authored by inertia's avatar inertia
Browse files

Setup testnet

parent 7f3bcb2d
No related branches found
No related tags found
2 merge requests!61Deploy to Production,!59Setup testnet
Hide whitespace changes
Inline Side-by-side
_quickstart/testnet.md
+ 7
− 92
View file @ 64f14f76
...@@ -4,100 +4,23 @@ position: 3 ...@@ -4,100 +4,23 @@ position: 3
exclude: true exclude: true
--- ---
Hive blockchain software is written in C++ and in order to modify the source code you need some understanding of the C++ programming language. Each Hive node runs an instance of this software, so in order to test your changes, you will need to know how to install dependencies which can be found in the [Hive repo](https://github.com/steemit/steem/blob/master/doc/building.md). This also means that some knowledge of System administration is also required. There are multiple advantages of running a testnet, you can test your scripts or applications on a testnet without extra spam on the live network, which allows much more flexibility to try new things. Having access to a testnet also helps you to work on new features and possibly submit new or improved pull requests to official the Hive GitHub repository. Hive blockchain software is written in C++ and in order to modify the source code you need some understanding of the C++ programming language. Each Hive node runs an instance of this software, so in order to test your changes, you will need to know how to install dependencies which can be found in the [Hive repo](https://gitlab.syncad.com/hive/hive/-/blob/master/doc/building.md). This also means that some knowledge of System administration is also required. There are multiple advantages of running a testnet, you can test your scripts or applications on a testnet without extra spam on the live network, which allows much more flexibility to try new things. Having access to a testnet also helps you to work on new features and possibly submit new or improved pull requests to official the Hive GitHub repository.
## Hive Testnet
More info soon
### Features ### Features
*Old text: Will be replaced:* A Hive testnet is a mirror of the mainnet. This is achieved by copying the existing accounts and transactions from the mainnet state, as the they happen. Accounts are copied from a [snapshot](https://gitlab.syncad.com/hive/tinman#taking-a-snapshot) of mainnet while the module used to copy transactions in real time is called [`gatling`](https://gitlab.syncad.com/hive/tinman#gatling-transactions-from-mainnet). The `gatling` module runs at the final step of each testnet deployment.
The official Hive Testnet is a mirror of the mainnet. This is achieved by copying the existing accounts and transactions from the mainnet state, as the they happen. Accounts are copied from a [snapshot](https://github.com/steemit/tinman#taking-a-snapshot) of mainnet while the module used to copy transactions in real time is called [`gatling`](https://github.com/steemit/tinman#gatling-transactions-from-mainnet). The `gatling` module runs at the final step of each testnet deployment.
The combination of `snapshot` and `gatling` means that this testnet approaches a subset of the same activity that the mainnet experiences. Not everything can be mirrored. For example, if someone comments or votes on a post that hasn't been mirrored to the testnet (because the post itself pre-dates the testnet deploy), those operations will also not be included. The combination of `snapshot` and `gatling` means that this testnet approaches a subset of the same activity that the mainnet experiences. Not everything can be mirrored. For example, if someone comments or votes on a post that hasn't been mirrored to the testnet (because the post itself pre-dates the testnet deploy), those operations will also not be included.
At the time of this writing, the connection information for Hive's testnet is as follows:
* ChainID: `d043ab83d223f25f37e1876fe48a240d49d8e4b1daa2342064990a8036a8bb5b`
* Address prefix: `TST`
* API node: `https://testnet.steemitdev.com`
## Running a Testnet Node ## Running a Testnet Node
First, let's build `hived` specifically for testnet. Recommended specs: See: [Setting Up a Testnet]({{ '/tutorials-recipes/setting-up-a-testnet.html' | relative_url }})
* `Ubuntu Server 18.04 LTS`
* `100GB HDD`
* `16GB RAM` (mostly needed for `hived` build)
```bash
sudo apt-get update && sudo apt-get dist-upgrade
sudo reboot
sudo apt-get install autoconf automake autotools-dev bsdmainutils build-essential cmake doxygen \
git libboost-all-dev libreadline-dev libssl-dev libtool ncurses-dev pbzip2 pkg-config \
python3-dev python3-jinja2 python3-pip libbz2-dev libsnappy-dev\
wget curl screen pv virtualenv nano xz-utils
mkdir -p src
cd src
git clone HIVED_OFFICIAL
cd steem
git checkout master # or a specific testnet branch
git submodule update --init --recursive
mkdir -p build
cd build
cmake \
-DCMAKE_BUILD_TYPE=Release \
-DBUILD_HIVE_TESTNET=ON \
-DLOW_MEMORY_NODE=ON \
-DCHAINBASE_CHECK_LOCKING=ON \
-DCLEAR_VOTES=ON \
-DSKIP_BY_TX_ID=ON \
-DHIVE_LINT_LEVEL=OFF \
..
make -j$(nproc) install
cd
mkdir -p testnet-data
cd testnet-data
nano config.ini
```
### `config.ini`
```ini
log-console-appender = {"appender":"stderr","stream":"std_error"}
log-file-appender = {"appender":"p2p","file":"logs/p2p/p2p.log"}
log-logger = {"name":"default","level":"info","appender":"stderr"}
log-logger = {"name":"p2p","level":"warn","appender":"p2p"}
backtrace = yes
plugin = chain p2p webserver witness database_api network_broadcast_api block_api
shared-file-dir = "blockchain"
shared-file-size = 12G
p2p-endpoint = 0.0.0.0:2001
webserver-http-endpoint = 0.0.0.0:8751
webserver-ws-endpoint = 0.0.0.0:8752
# testnet.steemitdev.com
p2p-seed-node = testnet.steemitdev.com:2001
```
Then execute:
```bash
hived --data-dir=. --chain-id=d043ab83d223f25f37e1876fe48a240d49d8e4b1daa2342064990a8036a8bb5b
```
Now let it sync, and you'll have a shiny new testnet seed node to play with.
## Custom Testnet ## Custom Testnet
In order to create a custom, isolated, testnet separate from the Hive's we need to modify a few things mentioned in the previous section. In order to create a custom, isolated, testnet we need to modify a few things mentioned in the previous section.
In the file named `steem/libraries/protocol/include/steem/protocol/config.hpp`, we can see the first few lines dedicated to the Testnet section. The line starts with `#ifdef IS_TEST_NET`. In the file named `hive/libraries/protocol/include/hive/protocol/config.hpp`, we can see the first few lines dedicated to the Testnet section. The line starts with `#ifdef IS_TEST_NET`.
Let's say we want to create a custom testnet with an initial supply of **1,000,000 HIVE**. We can change `HIVE_INIT_SUPPLY 1,000,000` and by changing `HIVE_CHAIN_ID_NAME "testnet"`, **testnet** to **mytestnet** we will automatically get a unique Chain ID for our testnet. The address prefix can be set to something like **MTN** and of course, we need to change the public and private keys to the genesis account. Note that the genesis account will receive the entire pre-mined supply of 1,000,000. That way, you can execute a setup script to fund any newly created accounts. Such a custom testnet will not have any additional hardware requirements to run. Let's say we want to create a custom testnet with an initial supply of **1,000,000 HIVE**. We can change `HIVE_INIT_SUPPLY 1,000,000` and by changing `HIVE_CHAIN_ID_NAME "testnet"`, **testnet** to **mytestnet** we will automatically get a unique Chain ID for our testnet. The address prefix can be set to something like **MTN** and of course, we need to change the public and private keys to the genesis account. Note that the genesis account will receive the entire pre-mined supply of 1,000,000. That way, you can execute a setup script to fund any newly created accounts. Such a custom testnet will not have any additional hardware requirements to run.
...@@ -105,7 +28,7 @@ A minimum of 8GB RAM should be sufficient to run a custom testnet. Currently, Hi ...@@ -105,7 +28,7 @@ A minimum of 8GB RAM should be sufficient to run a custom testnet. Currently, Hi
One more crucial point to modify is to change the number of witnesses required to accept hardforks for a custom testnet, by default it is set to 17, we can change it to **1** `HIVE_HARDFORK_REQUIRED_WITNESSES 1` so that only one node instance would be sufficient and the network will be still functional and fast. One more crucial point to modify is to change the number of witnesses required to accept hardforks for a custom testnet, by default it is set to 17, we can change it to **1** `HIVE_HARDFORK_REQUIRED_WITNESSES 1` so that only one node instance would be sufficient and the network will be still functional and fast.
Another thing to note is that you can start a new chain with all previous hardforks already accepted, by changing the file named `steem/blob/master/libraries/chain/database.cpp` with the following function: Another thing to note is that you can start a new chain with all previous hardforks already accepted, by changing the file named `hive/blob/master/libraries/chain/database.cpp` with the following function:
`void database::init_genesis( uint64_t init_supply )` inside `try` add this line: `void database::init_genesis( uint64_t init_supply )` inside `try` add this line:
...@@ -115,12 +38,4 @@ This would mean that 19 hardforks have been accepted by witnesses and the new ch ...@@ -115,12 +38,4 @@ This would mean that 19 hardforks have been accepted by witnesses and the new ch
After these changes, all we have to do is compile the source code and get the `hived` executable. And once we fire up the custom testnet we can start testing and experimenting. After these changes, all we have to do is compile the source code and get the `hived` executable. And once we fire up the custom testnet we can start testing and experimenting.
If you want to port some data from Hive main network you can use [Tinman](https://github.com/steemit/tinman), also developed by Hive, to help with taking snapshots of the main network. If you want to port some data from Hive main network you can use [Tinman](https://gitlab.syncad.com/hive/tinman), also developed by the Hive community, to help with taking snapshots of the main network.
#### Custom live testnet
An example of a custom testnet run by Hive community member [@almost-digital](https://hive.blog/@almost-digital). It doesn't have a snapshot of the main network
* ChainID: `79276aea5d4877d9a25892eaa01b0adf019d3e5cb12a97478df3298ccdd01673`
* Address prefix: `STX`
* API node: `https://testnet.steem.vc`
_testnet/index.md
+ 1
− 1
View file @ 64f14f76
...@@ -57,7 +57,7 @@ This would mean that 19 hardforks have been accepted by witnesses and the new ch ...@@ -57,7 +57,7 @@ This would mean that 19 hardforks have been accepted by witnesses and the new ch
After these changes, all we have to do is compile the source code and get the `hived` executable. And once we fire up the custom testnet we can start testing and experimenting. After these changes, all we have to do is compile the source code and get the `hived` executable. And once we fire up the custom testnet we can start testing and experimenting.
If you want to port some data from Hive main network you can use [Tinman](https://github.com/steemit/tinman), also developed by Hive, to help with taking snapshots of the main network. If you want to port some data from Hive main network you can use [Tinman](https://gitlab.syncad.com/hive/tinman), also developed by the Hive community, to help with taking snapshots of the main network.
#### Custom live testnet #### Custom live testnet
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment