Consensus, finality, fault tolerance, and state replication
The last healthy response does not establish that a node is healthy now. Explore why the nigo-protocol operations console distinguishes sample times, failed observations, command acceptance, and actual completion.
Running the same tests to prepare for a new storage backend exposed defects in the existing Memory implementation. Partial snapshot writes and state history classification show where shared contracts end and backend-specific durability checks begin.
What happens when a validator moves to the next round and discards finality evidence that arrives late? A reproduction and fix in nigo-protocol show why casting new votes and learning an existing decision are different operations.
What must a consensus node save so it remembers its own votes after a restart? A look at commit, durability confirmation, and signature broadcast in nigo-protocol's local safety records.
A responding server, a running consensus engine, and finalized transactions require different evidence. How nigo-protocol distinguishes normal idle time, delayed progress, and missing observations.
Block execution took 18% less time, but the full local processing path improved by only 2.4%; nigo-protocol's benchmark records show how validation costs, transaction dependencies, and measurement order change the performance comparison.
How a DAG represents the waiting required between transactions, how WAVE, READY_QUEUE, and WORK_FIRST_CONTINUATION schedule the same dependencies, and where these strategies apply to nigo-protocol's Direct Cell and Native Program paths.
A split-and-join example with 100 units of an asset explains how transaction independence, isolated execution, and ordered result application produce the same ledger as sequential execution.
Starting with verification data shared by several states, nigo-protocol's load tests show why stopping safely and completing automatic cleanup are different outcomes.
A transfer of 100 units shows how absence from historical state differs from uncaptured or unretained data, what a single Cell proof establishes, and who must keep that data available.