xian-abci
xian-abci is the CometBFT-facing Xian node runtime. It owns deterministic
chain execution, ABCI request handling, state export and snapshot flows, and
the node-adjacent services (BDS indexing, metrics, the optional dashboard) that
run alongside a Xian validator or full node.
The published PyPI package is xian-tech-abci. Console entrypoints
(xian-abci, xian-dashboard, xian-configure-node, and the BDS / state
helpers) are installed by the package and used both directly and from the
operator-facing xian-cli.
Runtime Shape
flowchart LR
CometBFT["CometBFT"] --> ABCI["ABCI handlers"]
ABCI --> Executor["Transaction processor"]
Executor --> Contracting["xian-contracting runtime"]
Executor --> State["Chain state"]
State --> BDS["BDS indexer"]
State --> Snapshots["Export and snapshot tools"]
ABCI --> Metrics["Metrics"]
ABCI --> Dashboard["Optional dashboard"]
CLI["xian-cli and xian-stack"] --> Entrypoints["xian-abci entrypoints"]
Quick Start
Bootstrap the development environment with uv:
UV_CACHE_DIR=/tmp/uv-cache uv sync --group dev
Inspect the available command surface:
uv run xian-abci --help
uv run xian-dashboard --help
uv run xian-configure-node --help
uv run xian-export-state --help
uv run xian-state-snapshot --help
uv run xian-bds-reindex --help
uv run xian-bds-snapshot --help
uv run xian-bds-spool --help
uv run xian-parallel-estimator-report --help
Optional extras:
vm— enables thexian_vm_v1bindings.native— enables native admission helpers for development and release validation.zk— enables the native zk verifier required by nodes on chains with thezkruntime feature.
For a ready-made local network instead of wiring the node yourself, use
xian-stack. This repo focuses on the runtime and backend
tooling, not the full localnet UX.
Principles
- Deterministic chain execution. The ABCI handlers, transaction execution, rewards, validators, and query behavior live here and must be deterministic across nodes.
- Backend, not UX. Operator-facing lifecycle commands belong in
xian-cli. This repo exposes importable helpers and backend-oriented CLIs only. - Universal node runtime. No network-specific genesis files, seeds, or
snapshots. Committed chain assets live in
xian-configs. - Contract semantics live elsewhere. Changes to contract execution
semantics belong in
xian-contracting, not here. - No Compose / orchestration. Container lifecycle and local-stack
orchestration belong in
xian-stack.
Local uv development requires a sibling checkout of
../xian-contracting. Full validation also uses sibling checkouts of
../xian-contracts, ../xian-configs, and ../xian-stack.
Key Directories
src/xian/— repo-owned node runtime: ABCI handlers, services, utilities, and CLI entrypoints.methods/— ABCI request handlers (CheckTx, DeliverTx, Commit, …).services/— background services such as the simulator and BDS support.cli/— backend and developer entrypoints (configure-node, export-state, BDS helpers, …) wrapping importable helpers.tools/— one-off upgrade data and state-patch payloads. Treated as a transition area; new code should live as importable helpers undersrc/xian/.dashboard/— the optional operator dashboard.
src/abci/— lower-level ABCI server and protocol glue.protos/— vendored CometBFT schemas plus supporting protobuf dependencies.build_proto.py— regenerates checked-in protobuf Python stubs undersrc/.scripts/— repo-level validation and manual benchmark entrypoints.tests/— unit, ABCI-method, integration, governance, tools, and system coverage.docs/— architecture notes, API surface, safety invariants, snapshots / pruning model, governance, and backlog.
Validation
Preferred full validation entrypoint, used for releases:
./scripts/validate-release.sh
It defaults to Python 3.14 (override with XIAN_ABCI_VALIDATE_PYTHON) and
runs:
./scripts/validate-repo.sh- protobuf regeneration / stale-stub checks
- the Python-vs-native processor fuzz parity coverage
(
tests/integration/test_vm_processor_fuzz.py)
Faster local loops:
UV_CACHE_DIR=/tmp/uv-cache uv run ruff check .
UV_CACHE_DIR=/tmp/uv-cache uv run ruff format --check .
UV_CACHE_DIR=/tmp/uv-cache uv run pytest
UV_CACHE_DIR=/tmp/uv-cache uv run pytest tests/unit/test_node_setup.py
CI provisions Postgres for the BDS-backed paths. To mirror that locally, expose
Postgres at postgres://postgres:1234@localhost:5432/xian.
Related Docs
- AGENTS.md — repo-specific guidance for AI agents and contributors
- docs/README.md — index of internal design notes
- docs/ARCHITECTURE.md — major components and dependency direction
- docs/BACKLOG.md — open work and follow-ups
- docs/API.md — ABCI and helper API surface
- docs/SAFETY_INVARIANTS.md — invariants the runtime must preserve
- docs/SNAPSHOTS_AND_PRUNING.md — snapshot, pruning, and BDS retention model
- docs/CHAIN_ASSETS.md — split between this repo and
xian-configs - docs/TIME_SEMANTICS.md — block-time and timestamp rules
- docs/Governance.md — on-chain governance behavior
Metadata
Release files for xian-tech-abci 0.9.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| xian_tech_abci-0.9.3.tar.gz | 265.0 kB | With provenance | Details for xian_tech_abci-0.9.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| xian_tech_abci-0.9.3-py3-none-any.whl | Python 3 | none | any | Details for xian_tech_abci-0.9.3-py3-none-any.whl |
Total release size: 602.3 kB
Release files / xian_tech_abci-0.9.3.tar.gz
| Download URL | xian_tech_abci-0.9.3.tar.gz |
|---|---|
| Size | 265.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5e551f7da53cf15c67a4a00069077da8e80ae5632429511d0aafb49aeb03f8e
|
|
BLAKE2b-256 checksum How to use checksums |
600cb85fdd76d51f8f21c76e3e03e91085057ce4ccb704635a2e4cbedfa2a6cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / xian_tech_abci-0.9.3-py3-none-any.whl
| Download URL | xian_tech_abci-0.9.3-py3-none-any.whl |
|---|---|
| Size | 337.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0fcbd11dd73a1fced97bf35d12a0d90cc17150d51cc0c96d5cb5f754584c6719
|
|
BLAKE2b-256 checksum How to use checksums |
a39700dd8d8cf71da38dcc016226ff1ef39114a239b1c912811e33e27292fb41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logSecurity for xian-tech-abci 0.9.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for xian_tech_abci-0.9.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.