Skip to main content
Octra is a layer-1 blockchain with native support for fully homomorphic encryption (FHE) and programmable isolated execution environments called Circles. Xpectrum’s contracts run directly on Octra’s AML virtual machine.

​
AML: the smart contract language

Octra contracts are written in AML (AppliedML) and compiled to OCTB bytecode. AML is Octra’s native contract language. Xpectrum’s contracts (Xcollection, Xlist, Xmarket) are all AML programs. Octra enforces atomicity across cross-contract calls: if a call() to another contract reverts, the whole transaction reverts, including any transfer() that ran earlier in the same function (verified on-chain, June 2026). Xpectrum uses pull-based proceeds for this reason: recipients claim their funds in a separate transaction rather than having them pushed during settlement, keeping every payout clear of a downstream-call failure.

​
FHE: Fully Homomorphic Encryption

Octra has native FHE support at the VM level. Operations like fhe_mul, fhe_add_const, and fhe_verify_range are available to contracts. Xpectrum v1 doesn’t use FHE directly. It’s on the research roadmap for future versions: private collection state, sealed bids, that kind of thing.

​
Circles

Circles are isolated execution environments on Octra. They run AML/OCTB bytecode, hold their own state, and can call other on-chain contracts via call(address, "method", args). Xpectrum deploys one Circle per collection. It stores the collection’s metadata and art on-chain, and those assets are public: anyone can read them. “Sealed” refers to writes, once a collection is frozen its assets cannot be altered. NFT-gated access applies to a Circle’s programmable interactions, not to reading the public assets.
Circles are live on Xpectrum. The current implementation is collection-wide: one Circle per collection, gated by NFT ownership. We are actively refining the access-control paths for efficiency.

​
Network endpoints

Xpectrum runs on Octra mainnet. To call a view function: