Developer documentation

Many runtimes.
One Singularity.

Use different runtimes as parts of one application. Singularity gives them shared accounts and one consensus order, so supported cross-VM calls can build on each other's updates and commit or roll back together.

Start building Explore the docs
Many paths in.One shared state.
45 chapters. From first principles to code.

Learn by doing

Sign a transaction, change an amount, and watch verification reject it. No funds or node required.

Start the tutorial

Complete a task

Configure a wallet, check a program, assess HILSA readiness, or inspect a transaction.

Find a how-to guide

Look up a detail

Find exact CLI commands, Bombil interfaces, fees, limits, and compatibility.

Open the reference

Understand the design

See why different runtimes share accounts, how their calls compose, and where consensus fits.

Read the explanation

Explore Bombil

Give orders, matching, and accounting their own execution environment on shared state. Resident CUDA execution is currently gated.

Understand Bombil

Use the Singularity CLI

Install a pinned public CLI, create a wallet you can reload, and choose your endpoint explicitly.

Open the CLI guide

What is HILSA?

Use verified facts from other chains in local transactions. Set the evidence your application accepts and follow how external settlement completes.

Explore HILSA

Different runtimes. Shared state.

Each environment has its own execution rules. Shared accounts connect their results; each cross-VM route needs a supported adapter.

Cross-VM composition
SVMSolana programsEVMSolidity contractsWASMWebAssembly modulesMoveResource-oriented executionZKProof verificationBombilFinancial execution · runtime gated

Find your next answer.

The complete field guide to Singularity.

11 sections

Build with Singularity

Configure a wallet, check a program, assess HILSA readiness, and inspect a transaction.

4 chapters

HILSA

Verified foreign state, cross-chain settlement, and interoperability alternatives.

4 chapters

Architecture

Consensus, execution, and the shared state that connects every runtime.

11 chapters

Core concepts

Transactions, accounts, assets, and native protocols from first principles.

4 chapters

Workflows

Follow transactions, cross-VM calls, validator changes, and recovery.

4 chapters

Integrations

Build with RPC, WebSockets, the TypeScript SDK, and bridge interfaces.

4 chapters

Run a node

Build, configure, deploy, observe, and recover the runtime.

3 chapters

Testing & performance

Choose the right checks and understand what a benchmark proves.

2 chapters

Security

Understand authority, trust boundaries, and failure semantics.

1 chapters

Contributing

Find an owner, make a focused change, and validate its behavior.

1 chapters

Reference

Look up CLI commands, Bombil interfaces, fees, compatibility, and terminology.

6 chapters