# Singularity Docs

> Developer and operator documentation for the Singularity multi-VM blockchain.

- [Consensus, finality, and epoch boundaries](https://docs.thesingularity.sh/docs/architecture/consensus-and-finality): How the Simplex engine orders payloads, how finalized blocks become executed state, and why epoch changes need an execution barrier.
- [Deterministic execution across CPU and GPU lanes](https://docs.thesingularity.sh/docs/architecture/execution-pipeline): How verification, dependency scheduling, VM journals, and ordered state merging preserve transaction semantics while overlapping work.
- [Architecture](https://docs.thesingularity.sh/docs/architecture): Consensus, execution, and the shared state that connects every runtime.
- [Node startup, roles, and task ownership](https://docs.thesingularity.sh/docs/architecture/node-runtime): How svm-vm resolves configuration, recovers state, validates execution engines, and starts role-specific services.
- [One chain, shared state, supported runtimes](https://docs.thesingularity.sh/docs/architecture/system-overview): Shared accounts and one consensus order let supported cross-VM calls contribute to a single transaction outcome.
- [State ownership, roots, and persistent storage](https://docs.thesingularity.sh/docs/architecture/unified-state-and-persistence): Account views, transaction journals, common state commit, deferred WAL durability, QMDB roots, and authenticated recovery artifacts.
- [Bombil financial execution environment](https://docs.thesingularity.sh/docs/architecture/vms/bombil): A financial execution environment for orders, matching and accounting on shared state, with resident CUDA execution currently gated.
- [EVM execution on shared state](https://docs.thesingularity.sh/docs/architecture/vms/evm): CuEVM execution, Ethereum envelope validation, demand-paged state, native-value limits, precompiles, receipts, and build requirements.
- [Virtual machines](https://docs.thesingularity.sh/docs/architecture/vms): Consensus, execution, and the shared state that connects every runtime.
- [Move modules, resources, and calls](https://docs.thesingularity.sh/docs/architecture/vms/move): Move publication and invocation over shared accounts, exact call encodings, raw-argument restrictions, native functions, events, and rollback.
- [SVM accounts and deployed SBF programs](https://docs.thesingularity.sh/docs/architecture/vms/svm): Native program dispatch, canonical BPFCC execution, loader admission, CPI authority, post-image validation, and Solana compatibility boundaries.
- [WASM contracts and host capabilities](https://docs.thesingularity.sh/docs/architecture/vms/wasm): Native Wasmtime contract ABI, deployment authorization, account capabilities, fuel, nested calls, and partial CosmWasm integration.
- [Proof verification and cryptographic interfaces](https://docs.thesingularity.sh/docs/architecture/vms/zk): Groth16 and BN254 formats, reachable native and RPC paths, boolean semantics, resource bounds, and Token-2022 proof binding.
- [Overview](https://docs.thesingularity.sh/docs/assets/diagrams): Explore the Singularity execution environments.
- [Overview](https://docs.thesingularity.sh/docs/assets): Explore the Singularity execution environments.
- [Funding-carry strategy model](https://docs.thesingularity.sh/docs/concepts/funding-carry-strategy): Deterministic opportunity selection, bounded order intents, risk accounting, reconciliation, and the missing execution integrations.
- [Core concepts](https://docs.thesingularity.sh/docs/concepts): Transactions, accounts, assets, and native protocols from first principles.
- [Native programs and product protocols](https://docs.thesingularity.sh/docs/concepts/native-programs-and-product-protocols): Choose account, trading, staking and agent primitives by their state and authority boundaries.
- [Protocol primitives and canonical data](https://docs.thesingularity.sh/docs/concepts/protocol-primitives): Understand account authority, signed transaction identity, block commitments and compatibility boundaries.
- [Universal assets and identity](https://docs.thesingularity.sh/docs/concepts/universal-assets-and-identity): Understand shared token representation, account authenticity and capability-authorized spending.
- [Change the runtime without breaking its contracts](https://docs.thesingularity.sh/docs/contributing/change-guide): Locate the right boundary, choose focused validation and prepare a reviewable change.
- [Contributing](https://docs.thesingularity.sh/docs/contributing): Find an owner, make a focused change, and validate its behavior.
- [Check a program before deployment](https://docs.thesingularity.sh/docs/guides/check-program): Inspect a compiled SBF artifact with the public CLI, interpret ELF-header failures, and distinguish a passed local guard from verified execution.
- [Check a HILSA read or settlement route](https://docs.thesingularity.sh/docs/guides/hilsa-readiness): Use read-only RPC probes to distinguish endpoint health, catalog coverage, committed evidence and settlement prerequisites before integrating HILSA.
- [Build with Singularity](https://docs.thesingularity.sh/docs/guides): Configure a wallet, check a program, assess HILSA readiness, and inspect a transaction.
- [Inspect a transaction after a timeout](https://docs.thesingularity.sh/docs/guides/inspect-transaction): Resolve a saved transaction signature through CLI or RPC receipt lookup, distinguish retrieval from execution success, and avoid duplicate payments after ambiguous responses.
- [Configure the Singularity CLI and wallet](https://docs.thesingularity.sh/docs/guides/singularity-cli): Install a pinned CLI, create and reload a local wallet, select an endpoint and distinguish completed setup from network availability.
- [HILSA and the interoperability landscape](https://docs.thesingularity.sh/docs/hilsa/alternatives): Choose foreign-state reads, messaging or settlement by verification, application control and destination behavior.
- [HILSA writes and settlement](https://docs.thesingularity.sh/docs/hilsa/cross-chain-writes): Follow an outbound instruction from local state through certification, delivery, and destination enforcement, with the distinct asset withdrawal path.
- [HILSA](https://docs.thesingularity.sh/docs/hilsa): Verified foreign state, cross-chain settlement, and interoperability alternatives.
- [HILSA — foreign-state intelligence and cross-chain settlement](https://docs.thesingularity.sh/docs/hilsa/overview): HILSA lets programs act on verified facts from other chains, with application-defined trust requirements and separate external settlement.
- [Reading foreign evidence with HILSA](https://docs.thesingularity.sh/docs/hilsa/verified-reads): Use committed foreign-chain heads and bridge records with explicit verification and finality requirements, and understand the limits of those guarantees.
- [Documentation](https://docs.thesingularity.sh/docs): Build your first signed transaction, connect to other chains with HILSA, or understand how multiple runtimes share one state.
- [Asset bridging and custody](https://docs.thesingularity.sh/docs/integrations/asset-bridge): Trace lock, observation, UTH minting, burn, and external unlock, including the separate proof-backed deposit route and recovery requirements.
- [Clients, the RPC edge, and protocol integration](https://docs.thesingularity.sh/docs/integrations/clients-edge-and-framework): Choose a client surface, understand edge routing and retries, and distinguish executable integrations from the protocol framework's design material.
- [HILSA interfaces and integration contracts](https://docs.thesingularity.sh/docs/integrations/hilsa-interop): Exact HILSA RPC shapes, proof verification, unsigned builders, certificates, and VM read ABIs, with source and observed deployment boundaries.
- [Integrations](https://docs.thesingularity.sh/docs/integrations): Build with RPC, WebSockets, the TypeScript SDK, and bridge interfaces.
- [RPC, WebSocket, and SDK contracts](https://docs.thesingularity.sh/docs/integrations/rpc-websocket-and-sdk): Integrate transaction submission, simulation, receipts, subscriptions, instruction builders, and JavaScript helpers without confusing admission, execution, and durability.
- [Build, run, and configure a node](https://docs.thesingularity.sh/docs/operations/build-run-and-configuration): Choose the correct CPU or CUDA artifact, validate nonsecret startup configuration, and start a disposable testnet with clear role and persistence boundaries.
- [Deployments and upgrades](https://docs.thesingularity.sh/docs/operations/deployment-and-upgrades): Plan an exact-release fleet change, preserve node identity and durable state, and understand coordinated cutover and rollback boundaries.
- [Run a node](https://docs.thesingularity.sh/docs/operations): Build, configure, deploy, observe, and recover the runtime.
- [Observability, incidents and recovery](https://docs.thesingularity.sh/docs/operations/observability-incidents-and-recovery): Diagnose reachability, execution, finality and durable-state failures with bounded probes, and select recovery evidence without confusing liveness with correctness.
- [Your first signed transaction](https://docs.thesingularity.sh/docs/quickstart): Use a published SDK to build one signed transaction containing two transfers, verify its wire round-trip and reject a modified amount without funding an account.
- [Bombil names, admission and activation contracts](https://docs.thesingularity.sh/docs/reference/bombil): Exact legacy identifiers, native command constraints, provisioning errors and reference-wrapper boundaries for Bombil.
- [Singularity CLI reference](https://docs.thesingularity.sh/docs/reference/cli): Exact command, option, configuration, key and output contracts for the public Singularity CLI, with a separate compatibility note for the Rust eto-cli utility.
- [Compatibility and availability](https://docs.thesingularity.sh/docs/reference/compatibility-and-availability): Distinguish Singularity's implemented execution and interoperability contracts from installable packages, enabled node paths and dated public-service observations.
- [Fees and limits](https://docs.thesingularity.sh/docs/reference/fees-and-limits): Calculate execution and priority fees, distinguish quotes from actual debits, and identify transaction, compute, account, RPC and bridge bounds.
- [Glossary](https://docs.thesingularity.sh/docs/reference/glossary): Shared vocabulary for Singularity's execution environments, account state, consensus, HILSA evidence, settlement and client tooling.
- [Reference](https://docs.thesingularity.sh/docs/reference): Look up CLI commands, Bombil interfaces, fees, compatibility, and terminology.
- [Repository map](https://docs.thesingularity.sh/docs/reference/repository-map): Find the authoritative implementation, test and operational entrypoints for a reader question without treating every directory or design note as an active product path.
- [Security](https://docs.thesingularity.sh/docs/security): Understand authority, trust boundaries, and failure semantics.
- [Trust boundaries](https://docs.thesingularity.sh/docs/security/trust-boundaries): Identify who authorizes local execution, foreign evidence, asset custody, privileged RPC and recovery, and what each proof or signature actually establishes.
- [Testing & performance](https://docs.thesingularity.sh/docs/testing): Choose the right checks and understand what a benchmark proves.
- [Performance and benchmarks](https://docs.thesingularity.sh/docs/testing/performance-and-benchmarks): Select the right Singularity benchmark, interpret its workload and timing boundary, and distinguish component regression measurements from network capacity.
- [Validation strategy](https://docs.thesingularity.sh/docs/testing/validation-strategy): Select source, unit, integration, GPU, simulation, contract and operational checks that prove the changed boundary, while reusing archived CI builds and preserving failure evidence.
- [Cross-VM composition](https://docs.thesingularity.sh/docs/workflows/cross-vm-composition): Build ordered calls across execution environments while preserving account authority, shared compute accounting, and transaction rollback.
- [Durability and recovery](https://docs.thesingularity.sh/docs/workflows/durability-and-recovery): Follow a finalized block through the WAL, durable height, QMDB acknowledgement and validated restart, including failure windows and backup requirements.
- [Workflows](https://docs.thesingularity.sh/docs/workflows): Follow transactions, cross-VM calls, validator changes, and recovery.
- [Transaction lifecycle](https://docs.thesingularity.sh/docs/workflows/transaction-lifecycle): Follow signed instructions from client construction and admission to ordered execution, receipts, retries and persistent state.
- [Validator lifecycle and state sync](https://docs.thesingularity.sh/docs/workflows/validator-lifecycle-and-state-sync): Join the registry, follow state while pending, rotate into an epoch-specific consensus engine, and recover without confusing replica trust with validation.