Before running a node

Prepare the resources, credentials, and release information you need.

Choose the right kind of participation

Is a node the same as browser contribution?

No. Browser contribution uses enabled, bounded capacity while the application runs. Node software is an installation you operate to perform network duties. Becoming a validator or footnote reviewer is a separate admission process; installing software alone does not grant those roles.

Where do I obtain the software?

Use the official Bigfoot Node page for access and release information. Follow the installation instructions shipped with your release. Hardware, storage, and networking requirements must come from that release, not an old example command.

What should I plan for?

Account for storage, bandwidth, electricity, hosting, and maintenance. Decide who can access the machine, where credentials and backups are kept, and how you will apply required upgrades. Running a node does not guarantee recovery of those costs. Participation, accountability, and censorship resistance explains the obligations that come with operating one.

First installation

What should I check before making it reachable?

Confirm the release source, the network it joins, its data location, and the network connections and management controls it exposes. Keep management access restricted to the people and connections that need it. Follow the release’s startup and readiness checks before relying on the installation.

Looking for something else?

Browse product Help, explore Learn, or look up a term in the Glossary. You can also contact us with a question.