TSUNAGI — 繋ぎ

The cockpit of a Cardano validator.

A 20 MB Zig node that exposes its own forge-time decision model — posterior, expected value, Kelly, and LLR — in real time.

Built on Musubi (結び): connection as a generative force. Operator-first. Deterministic. Honest.

Let It Run. Let It Resolve.

Follows the chain via Ouroboros ChainSync and BlockFetch. Admits transactions through a six-gate hardened mempool. Serves and ingests transactions via bidirectional TxSubmission2. Computes a signed eight-layer trust graph from runtime observations. Deterministic. Verifiable. No garbage collector. No runtime allocator.

Live Node
Network Loading…
Role Follower + Forge
Language Zig
Slot Loading…
Block Loading…
Tip Age Loading…
Status Loading…
Delta Loading…
Connecting…

Position in the ecosystem

Node Language Binary Size Decision Metrics
TSUNAGI Zig 20 MB Yes
cardano-node Haskell 300–500 MB No
Amaru Rust 50–80 MB No
Dingo Go 50–100 MB No

Omotenashi in Engineering

In Japanese culture, omotenashi (おもてなし) means anticipating the needs of the recipient before they are expressed.

TSUNAGI is built the same way:

The operator sees exactly what the node sees.

Decision Model (Live)

TSUNAGI logs its decision metrics for every leader slot:

Correlation data (in progress):

When LLR ≥ 0.5 → acceptance rate: —
When LLR ≤ -0.5 → acceptance rate: —
(collecting live data)

TSUNAGI is a complete Cardano node built from scratch in Zig — no Haskell dependency, no IOG codebase fork. It follows the live chain, decodes blocks, tracks UTxO state, and has proven ChainSync interoperability with real cardano-node relays. Learn more →

Deterministic
Same inputs, same outputs. No hidden state. No ambient configuration.
Observable
Every subsystem explains itself. Health, sync, UTxO, mempool — all visible.
Operator-First
Built for operators who value clarity, control, and correctness.
Live Dashboard Project Guardian
Implementation Diversity
An independent codebase strengthens the network by providing a second perspective on protocol verification.
Operator-First Observability
Every subsystem explains itself. The node makes its internal state legible to the people who run it.
Deterministic Infrastructure
Identical inputs produce identical outputs, unconditionally. No hidden state. No ambient configuration.
Independent Engineering
Built from first principles without institutional funding. Priorities follow engineering judgment, not grant cycles.

Independent Engineering

Real infrastructure work, transparent progress, no institutional dependencies.

TSUNAGI is an independent implementation effort — a deterministic Cardano node architecture written in Zig from scratch. The project began as a solo engineering effort to build node infrastructure grounded in observability, runtime clarity, and operator-first design principles.

The deterministic ledger pipeline, shadow verification system, LMDB persistence layer, four observability subsystems (KAGAMI, YAMORI, TATE, KURA), and continuous preview-network validation have all been built through sustained daily engineering — without institutional grants, governance funding, or venture capital.

The treasury model and support path are publicly documented. Support through the TSUNA stake pool helps sustain ongoing development and infrastructure costs.


Infrastructure Status

TSUNAGI is running infrastructure, verified against a live network.

NodeTSUNAGI preview follower
NetworkCardano preview
TelemetryPublic — /data/status.json
ExplorerLive
DecodeLive
OperatorActive
MaturityActive development
SourcePrivate during active development — public release planned after stability milestone

Propagation Artifact Coherence

Merged on main: #68 — Forge promotion now publishes a coherent sealed artifact with verified fragment ancestry. The propagation server rejects incoherent fragment state rather than serving stale ancestry to a relay.

What Changed
  • Sealed promotion publishes coherent fragment ancestry
  • Propagation server validates ancestry at serve time
  • Stale fragment state is rejected, not served
  • Structured truth logs added at publish and serve time
  • Regression tests pass, ReleaseSafe build passes
Why It Mattered
  • Relay disconnects traced to stale fragment / sealed mismatch
  • Promoted sealed tip’s parent was missing from fragment window
  • Relay saw TSUNAGI as stale at connection time (relay_ahead=true)
  • Connection dropped after MsgIntersectFound, before MsgRequestNext

Current Live Target

Observing the relay-facing path on preview under live conditions. Artifact coherence was necessary but not sufficient — relay timing still matters.

Required Runtime Sequence
1. CHAIN_POSITION … relay_ahead=false
2. MsgRequestNext
3. MsgRollBackward
4. MsgRollForward
5. BlockFetch

What Is Proven

Observable, verifiable capabilities — not claims.

ChainSyncFollows live preview chain via Ouroboros
BlockFetchFull block bodies decoded from CBOR
UTxO + LMDBAncestry-verified persistent ledger state
MempoolSix-gate admission with confirmed eviction
TxSubmission2Bidirectional: serve inventory + ingest from peers
Trust StackEight signed layers, all verifiable
PropagationCoherent artifact publish + serve-time ancestry validation
Operator CoreHealth 0–100, runtime state, guardian mode
ValidationInput uniqueness, balance, validity, address
Block ForgeVRF + KES, deferred slot-time, proven on preview
Artifact CoherenceSealed + fragment published coherently at forge time
Accepted BlockNo network-accepted forged block yet
Consensus ParityNot equivalent to cardano-node
Plutus / ScriptsNo script execution yet
Protocol ParamsNo min-fee / min-UTxO enforcement yet
Epoch TransitionsNo stake snapshots / rewards yet
Production BPNot production-ready block producer

Architecture

TSUNAGI is organized as a layered architecture where each subsystem addresses a specific operational concern. The observability stack (KAGAMI, YAMORI, TATE, KURA) monitors and stabilizes the node. The TSURUGI protocol engine manages Ouroboros communication. The deterministic ledger pipeline processes blocks through a modular state machine. LMDB provides persistent storage with transactional guarantees.

TSUNAGI layered node architecture: observability subsystems, protocol engine, deterministic ledger pipeline, and LMDB persistent storage.

Core Pillars

Four foundational capabilities define the TSUNAGI architecture.

Ledger Engine

Deterministic Ledger

A modular pipeline separating delta extraction, state application, undo management, and persistent storage into independently testable components. No global state. Identical inputs produce identical outputs on every execution.

Verification

Shadow Verification

An independent pipeline instance processes identical deltas on every block and compares parity with the primary ledger. Divergence is detected within one block of occurrence. The shadow never influences the primary path.

Persistence

LMDB Truth Mode

Three-stage persistence with preflight coverage scan, atomic LMDB writes, and automatic memory fallback. Shadow-writes progressively converge the store with live chain state. Operators select the persistence guarantee they require.

Operations

Self-Healing Infrastructure

Four observability subsystems — KAGAMI, YAMORI, TATE, KURA — evaluate health, verify integrity, and stabilize artifacts automatically. The node explains its own health rather than requiring external diagnostic inference.


Live Infrastructure

Operational telemetry, decode pipelines, and observability tooling for the TSUNAGI runtime.


Research & Documentation

The architecture, methodology, and vision behind TSUNAGI are documented across four primary documents.


Support TSUNAGI

TSUNAGI is developed independently without institutional funding. Support through TSUNA or the $tsunagi ADA handle helps sustain ongoing development and infrastructure costs.

Pool Name
TSUNAGI Infrastructure
Ticker
TSUNA
ADA Handle
$tsunagi
Pool ID
pool1hnmcevsa69k88nh4d6ud5qyykwmgzrg6crju79zsv2uu65mkgr8

Funding model and transparency principles are documented on the Treasury page.

Development Status

TSUNAGI is under active development. Running live on the Cardano preview network. Latest merged milestone: propagation artifact coherence (#68). Current live target: relay progression past MsgIntersectFound under relay_ahead=false conditions. Not a mainnet replacement at this stage.