BWG LOONSHOTS
We document the problems, alternatives, experiments, and lessons that emerge while designing distributed ledgers and financial infrastructure.
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.
Execution environments, performance, verification, observability, and upgrades
View articlesFinancial workflows, settlement finality, tokenization, and ledger boundaries
View articlesState models, history, auditability, and privacy
View articlesConsensus, finality, fault tolerance, and state replication
View articlesApplication security design for authentication, authorization, secrets, and attack resistance
View articlesTechnical principles and design background of inventions documented in patents
View articles