feat(tools/talis): vendor talis deployment tool + Fibre experiment runner

[walldiss]

Summary

Brings the celestia-app talis multi-cloud deploy tool into ev-node, plus the wiring needed to deploy a working Fibre DA aggregator end-to-end on top of it. Verified via a fresh AWS run from this branch — talis up → genesis → deploy → setup-fibre → start-fibre → fibre-bootstrap-evnode reaches 24.57 MB/s @ 99.7 % ok rate on a 60 s sustained loadgen (3 × c6in.4xlarge validators + c6in.2xlarge bridge + c6in.8xlarge ev-node + c6in.2xlarge load-gen, all us-east-1).

What's added

• tools/talis/ — vendored from celestia-app's feat/fibre-payments. Provisions AWS / DO / GCP boxes for one or more validators + bridge + ev-node + load-gen, deploys binaries + init scripts, drives a Fibre setup-fibre + start-fibre flow, and ships an fibre-bootstrap-evnode step that scp's the bridge JWT and Fibre payment keyring onto each ev-node before its init script starts the daemon.
• tools/celestia-node-fiber/cmd/evnode-fibre/ — long-lived aggregator runner that wires block.NewFiberDAClient on top of the celestia-node-fiber adapter. Compiled by talis genesis and shipped to evnode-* hosts.
• tools/talis/cmd/evnode-txsim/ — small Go load-gen that pumps the runner's HTTP /tx ingress for a fixed duration; deployed to load-gen boxes and prints a single TXSIM: line on completion.
• tools/talis/Makefile — cross-compiles celestia-appd, the fibre server + load tool, the bridge/light celestia binary, and both runner binaries to linux/amd64 for talis genesis -b.

ev-node-side foundation work that the runner needs

These changes were what turned a "wired but slow" Fibre DA path into something that actually overlaps uploads and survives sustained load:

• pkg/config/config.go — ApplyFiberDefaults() profile (adaptive batching, 1 s DA.BlockTime, 50-deep pending-cache window).
• block/public.go — SetMaxBlobSize to lift the 5 MiB Celestia default to Fibre's 120 MiB headroom; NewFiberDAClient + Fibre type re-exports.
• block/internal/da/{fiber_client.go, fiber/types.go, fibremock/} — Fibre adapter wired through the DA client interface, with a matching mock used by the testing tree.
• block/internal/submitting/da_submitter.go — per-stream upload workers, splitByBlobSize chunking, parallel signing pool, and an oversized-blob safety net that advances the cache instead of looping forever (which OOM'd the daemon under sustained Fibre stalls in the AWS run).
• core/sequencer/sequencing.go + pkg/sequencers/solo/sequencer.go — ErrQueueFull sentinel + bounded mempool queue so the reaper backs off when the executor is paused on the pending-cache cap, instead of feeding an unbounded queue and getting one giant block on resume.

setup-fibre fixes uncovered during the verified run

• The bash script for set-host now retries until the validator's host appears in query valaddr providers. The previous one-shot call relied on --yes returning the txhash before block inclusion; if the chain wasn't ready yet, the tx silently bounced and the validator never registered. The Fibre client cached the partial set on startup and uploads cascaded to host not found → voting power: collected 0.
• The talis CLI side polls query valaddr providers after the per-validator scripts finish and refuses to return until all validators are registered (5-minute deadline, then errors so the operator can re-run).

External dependency

Documented in tools/talis/fibre.md: a sibling clone of celestia-app on a branch with feat/fibre-payments + the sysrex/fibre_url_fix cherry-pick. Without the URL-parse fix the Fibre client rejects every host:port registration with first path segment in URL cannot contain colon and voting power: collected 0 cascades. (This is a celestia-app fix that needs to land separately.)

Test plan

• go test ./block/... ./pkg/... ./types/... — all green
• go build ./... — clean
• make build-bins — all 6 binaries cross-compile cleanly to linux/amd64
• End-to-end AWS run from this branch — 24.57 MB/s, 99.7 % ok on a 60 s sustained loadgen

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 00427446-eabd-4764-ac5d-db634c43c298

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}