go-flare

go-flare is a modified version of [email protected] + [email protected] that incorporates the Flare Specific Features such as Prioritized contract handling and invoking Flare daemon contract.

This code also supports Songbird Network (and Coston testnet) node deployment from the version v0.6.6 onward.

All nodes should upgrade to the version 1.9.0 before the following dates:

• Coston2 network: November 26, 2024 at 12:00:00 UTC
• Flare network: December 17, 2024 at 12:00:00 UTC
• Coston network: January 7, 2025 at 12:00:00 UTC
• Songbird network: January 28, 2025 at 12:00:00 UTC

System Requirements

• go version 1.21.8
• gcc, g++ and jq
• CPU: Equivalent of 8 AWS vCPU
• RAM: 16 GiB
• Storage: 1TB Flare / 3.5TB Songbird
• OS: Ubuntu 20.04/22.04

Compilation

After cloning this repository, run:

cd go-flare/avalanchego && ./scripts/build.sh

Deploy a Validation Node

These servers fulfill a critical role in securing the network:

• They check that all received transactions are valid.
• They run a consensus algorithm so that all validators in the network agree on the transactions to add to the blockchain.
• Finally, they add the agreed-upon transactions to their copy of the ledger.

This guide explains how to deploy your own validator node so you can participate in the consensus and collect the rewards that the network provides to those who help secure it: https://docs.flare.network/infra/validation/deploying/

Deploy an Observation Node

Observation nodes enable anyone to observe the network and submit transactions. Unlike validator nodes, which provide state consensus and add blocks, observation nodes remain outside the network and have no effect on consensus or blocks.

This guide explains how to deploy your own observation node: https://docs.flare.network/infra/observation/deploying/

Tests

See tests/README.md for testing details

Container image

Public container images are hosted on Docker HUB and Github Packages;

docker.io/flarefoundation/go-flare
hgcr.io/flare-foundation/go-flare

Container builds in CI

CI builds on each:

• push on main branch, pushes image tagged as "dev"
• creation of a tag, pushes images tagged as the tag itself

Builds:
two images, go-flare:<TAG> one with leveldb