The availability tradeoff

WildRoot community Trust is unanimous. If a required member is unavailable, new application Trust stops instead of allowing separate network islands to create conflicting irreversible histories.

Reconnect and catch-up

Nodes retain the signed evidence and sequence data needed to catch up after reconnect. Rejoin logic must converge on the same Trusted sequence and checkpoint history rather than inventing a local replacement ordering.

Why this is explicit

The design makes the consistency/availability tradeoff visible to operators and application developers. A system is easier to integrate safely when its failure mode is documented rather than hidden behind generic “confirmation” language.

Run it yourself

Download WildRoot.

Use the official GitHub Releases page for downloadable WildRoot artifacts.

GitHub Releases ↗