Documentation
¶
Overview ¶
Command evnode-fibre runs a long-lived ev-node aggregator wired to a celestia-node-fiber adapter. It is the binary that ships to the ev-node instance during a `talis deploy` for the multi-FSP throughput experiment.
Topology (smallest variant of the experiment):
[ load-gen ]
│ POST /tx
▼
[ evnode-fibre (this binary) aggregator + InMem executor ]
│ block.NewFiberDAClient → cnfiber.New
▼
[ celestia-node bridge ]
│ blob.Subscribe / blob.Submit
▼
[ Fibre Server (per validator) ] + [ celestia-app validators ]
CLI flags map to talis/SSM-friendly env vars; everything that changes per-deploy can be set via flag *or* CELES_* env var.
This binary is intentionally not part of the testapp tree — testapp is the canonical small-chain example and we don't want to drag the celestia-node-fiber adapter (with its celestia-node + celestia-app deps) into testapp's go.mod. By living under tools/celestia-node-fiber the runner reuses the adapter's existing dep set as-is.