Golos is an experimental Proof of Work blockchain with an unproven consensus algorithm.

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.

Rather than attempt to describe the rules of the blockchain, it is up to each individual to inspect the code to understand the consensus rules.

Just want to get up and running quickly? Try deploying a prebuilt dockerized container. Both common binary types are included.

To run a p2p node (ca. 2GB of memory is required at the moment):

docker run \
    -d -p 2001:2001 -p 8090:8090 --name golos-default \
    goloschain/golos

docker logs -f golos-default  # follow along

To run a node with all the data (e.g. for supporting a content website) that uses ca. 14GB of memory and growing:

docker run \
    -d -p 2001:2001 -p 8090:8090 --name golos-full \
    goloschain/golos

docker logs -f golos-full

A list of some seed nodes to get you started can be found in documentation/seednodes.

This same file is baked into the docker images and can be overridden by setting STEEMD_SEED_NODES in the container environment at docker run time to a whitespace delimited list of seed nodes (with port).

The mining algorithm used by Golos requires the owner to have access to the private key used by the account. This means it does not favor mining pools.

./golosd --miner=["accountname","${WIFPRIVATEKEY}"] \
    --witness="accountname" --seed-node="95.85.13.229:2225"

Make sure that your accountname is unique and not already used by someone else or your proof of work might not be accepted by the blockchain.

See documentation/building.md for detailed build instructions, including compile-time options, and specific commands for Linux (Ubuntu LTS) or macOS X.

See documentation/testing.md for test build targets and info on how to use lcov to check code test coverage.