Flexible deployment
Run it where it works for you.
Use Linux on ordinary hardware. The Bigfoot-provided container is the recommended way to deploy, and the included CLI lets you configure the node for your environment.
Run a Bigfoot node
Run a Bigfoot node on Linux. No special hardware required.
One unified network
Nodes contribute resources to store and process Bigfoot protocol transactions. Adding a node expands shared capacity rather than creating a separate instance.
Flexible deployment
Use Linux on ordinary hardware. The Bigfoot-provided container is the recommended way to deploy, and the included CLI lets you configure the node for your environment.
Configurable resources
Set the capacity and network access you want to make available. The protocol determines which accepted data and operations use those resources, keeping every node part of the same network.
Availability
Your node builds standing by staying online and doing its work. Planned maintenance is covered by credit it builds up along the way, and unplanned outages cost standing.
Credited through use
When people use eligible services your node provides and the network accepts the work, the network credits that contribution in BFT.
Role guide
Anyone can run a node, and the network credits a node BFT for the work it does. In return, it offers only the capacity it really has, relays traffic, and stays available. The guide covers maintenance, BFT credits, and how to retire a node.
What you need
One protocol. One network.
Every node follows the same protocol and adds capacity to the same shared network. Bigfoot is unified rather than federated: node operators contribute resources without creating separate instances or choosing a different set of accepted operations.
Network roles
Apply to become a governance member, a footnote reviewer, or a validator. Or contribute footnotes and run a node, which anyone can do.