drep Setup Guide¶
This guide is intended to help you setup the
drep application using startup flags.
- Use the latest binary(cli-installation.md) to install
drep. Additional steps will be required if another installation method was used.
- Review how the launch commands for the Command Prompt (Windows) and Bash (macOS/Linux) shells differ here.
drep is the node daemon for Drep. A daemon is a program that works in the background that you do not interface with directly.
drep maintains the entire past transactional ledger (or blockchain) of Drep and allows relaying of transactions to other Drep nodes across the world. You can think of it as your own personal Drep blockchain server. The blockchain is saved in the
data folder within
drep‘s home directory.
Advanced Users: If you are running in headless mode via SSH, you
will need to use a terminal multiplexer such as screen
or tmux. Where you see the instruction to
move to another shell, you’ll need to start a new window in
Connect to the Drep Network¶
The first time launching
drep, it will connect to the Drep network and begin downloading the blockchain.
With the correctly set configuration files, open another shell window in your Drep directory (or use the last window if you have just created your wallet). Type the following command (review this guide’s Prerequisites to determine the right command for your OS/Shell application):
Wait for drep to Sync to the Drep Blockchain
dreplaunches successfully, you should see your shell window begin to fill up with messages as the daemon connects to the network and starts processing blocks. Wait until it is completed - the entire blockchain is being downloaded into the
You will see a line at the start like this:
22:58:04 2016-02-09 [INF] BMGR: Syncing to block height 617 from peer 184.108.40.206:9108
Then, as it continues to download blocks, you will see lines like this:
22:58:16 2016-02-09 [INF] BMGR: Processed 321 blocks in the last 10.03s (544 transactions, height 322, 2016-02-09 09:50:34 +1000 EST)
The blockchain will be fully synced once the most recently processed block is the current block height. You can tell by either comparing the date and time in the log message or by comparing the height of the last block processed against the last block height on the official block explorer.