ApexChainx is a smart contract platform built on the Stellar network for deterministic SLA (Service Level Agreement) calculation, payment escrow, and multi-party settlement.
These contracts run on the Stellar network using the Soroban smart contract platform.
The contract takes severity level, measured MTTR (Mean Time To Repair), and configured thresholds to determine whether SLA targets were met. Results include status (met/violated), payment type (reward/penalty), and rating.
No. All contract invocations must go through the backend API layer. The frontend never interacts with contracts directly.
The contract includes a version negotiation protocol (get_version_info()) that
allows backends to verify compatibility before deployment.
calculate_sla is idempotent: resubmitting an outage with an unchanged config
hash and identical inputs returns the stored result and writes nothing — no
history entry, no statistics, no telemetry, no events — so retries are safe and
cannot skew reported violation rates. Resubmitting the same outage with
different inputs is rejected (DuplicateOutageInput), and a config change opens
a new stored generation for that outage, capped at 16 retained entries
(OutageRecalcLimit) so one outage cannot crowd others out of the retention
window. Admin pruning frees that headroom again.
No. The contract is not natively upgradeable. Upgrades require deploying a new contract and migrating state through the backend.
Soroban-based SLA calculator and multi-contract coordination suite for the Stellar network.
This repository is the execution-layer side of the 3-repo architecture.
| Repository | Description |
|---|---|
| apexchainx-fe | Frontend application (React/TypeScript) |
| apexchainx-be | Backend API and contract bridge |
A dev container is provided for GitHub Codespaces and VS Code:
# Open in Codespaces or VS Code — the devcontainer auto-configures:
# - Rust toolchain + wasm32-unknown-unknown target
# - just command runner
# - Node.js + npx for tooling scripts# Bootstrap the dev environment
just bootstrap
# Run the full CI pipeline locally
just ciSee CONTRIBUTING.md for detailed setup instructions.
- Release Artifact Provenance Policy — Guidelines for WASM output checksums and snapshot check-ins.
- Dependency auditing:
cargo auditruns on CI for every push - WASM integrity: Release artifacts include SHA-256 manifests
- Reproducible builds: Local builds can be verified against CI-generated manifests