{"id":2607,"date":"2019-12-25T09:39:45","date_gmt":"2019-12-24T20:39:45","guid":{"rendered":"http:\/\/www.talkcrypto.org\/blog\/?p=2607"},"modified":"2020-02-14T00:22:08","modified_gmt":"2020-02-13T11:22:08","slug":"installing-besu-quick-commands","status":"publish","type":"post","link":"https:\/\/www.talkcrypto.org\/blog\/2019\/12\/25\/installing-besu-quick-commands\/","title":{"rendered":"Installing Besu quick commands"},"content":{"rendered":"\n
besu --version \/\/check if  Besu is  installed
brew uninstall besu \/\/uninstall Besu
brew install besu \/\/install Besu (assuming you have already tapped it first with brew tap hyperledger\/besu)
brew cask install adoptopenjdk
<\/pre>\n\n\n\n
Starting Besu<\/h2>\n\n\n\n
To start Besu, just type<\/p>\n\n\n\n
besu<\/pre>\n\n\n\n
This will start Besu pointing it to mainnet. This means that the blockchain will start to synchronise with the real Ethereum blockchain. A database folder (where the blockchain will be stored) will appear at usr\/local\/Cellar\/besu\/1.3.8\/ which is where homebrew installed besu.<\/p>\n\n\n\n
For testing purposes, start Besu with the network flag of dev<\/p>\n\n\n\n
besu --network=dev<\/pre>\n\n\n\n
The other option is to use a config file and then specific the network, as well as other parameters there. <\/p>\n\n\n\n
data-path=\"besudata\"
network=\"dev\"
miner-enabled=true
miner-coinbase=\"0xfe3b557e8fb62b89f4916b721be55ceb828dbd73\"
rpc-http-cors-origins=[\"all\"]
host-whitelist=[\"*\"]
rpc-ws-enabled=true
rpc-http-enabled=true<\/pre>\n\n\n\n
Then reference the config file with:<\/p>\n\n\n\n
besu --config-file=\"\/User\/sean\/config.toml\"
<\/pre>\n\n\n\n
Note that flags in the command line override flags in the config file. For a complete list of other command line options, visit: http:\/\/besu.hyperledger.org\/en\/stable\/Reference\/CLI\/CLI-Syntax\/<\/a><\/p>\n\n\n\n
Checking Besu network<\/h2>\n\n\n\n
To confirm the network you are connected to, you want to query the Besu API for the net_version. <\/p>\n\n\n\n
curl -X POST --data '{\"jsonrpc\":\"2.0\",\"method\":\"net_version\",\"params\":[],\"id\":1}' localhost:8545<\/pre>\n\n\n\n
You can find out what net_version<\/a> does along with all the other API options here<\/a>.<\/p>\n\n\n\n
However, in order for this to work, Besu must be started with the flag:<\/p>\n\n\n\n
--rpc-http-enabled<\/pre>\n\n\n\n
Exercise<\/h4>\n\n\n\n
Enable rpc-http in a config file, but override it in the command line and prove that the override was successful<\/p>\n\n\n\n
besu --config-file=\/Users\/sean\/config.toml --rpc-http-enabled=\"false\"<\/pre>\n\n\n\n
Running the following curl command should yield a “failed to connect error”. <\/p>\n\n\n\n
curl -X POST --data '{\"jsonrpc\":\"2.0\",\"method\":\"net_version\",\"params\":[],\"id\":45}' localhost:8545<\/pre>\n\n\n\n
curl: (7) Failed to connect to localhost port 8545: Connection refused<\/pre>\n\n\n\n
Changing the Besu network<\/h2>\n\n\n\n
So far we have specified the development network with the flag<\/p>\n\n\n\n
--network=dev (or in the config file as network=\"dev\")<\/pre>\n\n\n\n
or omitting the flag defaults to mainnet. However, there are 6 other networks<\/a> that can be chosen. Ropsten, Rinkeby, Goerli, Classic, Mordor and Kotti. eg:<\/p>\n\n\n\n
besu --network=ropsten<\/pre>\n\n\n\n
Fun fact:<\/strong> “Testnets are named after train stations<\/a> as a convention, usually where the respective testnet maintainers are based from.” <\/p>\n\n\n\n