A research-driven blockchain infrastructure initiative focused on deterministic interoperability, explicit trust boundaries, and auditable system behavior.

AOXC develops coordination infrastructure for heterogeneous blockchain environments. The core thesis is straightforward: cross-chain systems should be engineered as verifiable distributed systems, not assembled as ad-hoc integrations.

The project emphasizes deterministic state handling, explicit trust assumptions, modular architecture, and operational surfaces that remain inspectable as system complexity grows.

AOXC is in an active alpha research phase.

At this stage, the scope is intentionally narrow and iterative. The current priority is to validate deployments, test interoperability assumptions in controlled steps, and expand only after technical stability and operational repeatability are demonstrated.

This phase should be understood as a research-grade baseline: publicly inspectable, practically instantiated, and expected to evolve as core assumptions are validated.

For the current phase, X Layer serves as the primary operational network for AOXC deployments and coordination experiments.

This does not imply final network exclusivity. It reflects the project's current execution focus while interoperability primitives, operational controls, and architectural assumptions are being tested under live conditions.

The following on-chain artifacts are publicly accessible for independent verification:

• Main Contract: https://www.oklink.com/tr/x-layer/address/0x97bdd1fd1caf756e00efd42eba9406821465b365/contract
• Proxy Token Contract: https://www.oklink.com/tr/x-layer/token/0xeb9580c3946bb47d73aae1d4f7a94148b554b2f4?tab=contract
• Multisig Contract: https://www.oklink.com/tr/x-layer/address/0x20c0dd8b6559912acfac2ce061b8d5b19db8ca84/contract

These references are provided to support direct inspection of live on-chain infrastructure rather than abstract project claims.

AOXC is organized into specialized repositories with clear functional boundaries:

• aoxcon — Control Plane & Operations
  Administrative and orchestration surface for policy flow, lifecycle management, and operational visibility.

• aoxcore-xlayer — EVM Execution Module
  Solidity-based execution components for EVM-compatible environments, with X Layer as the current primary deployment domain.

• aoxcore-sui — Move / Object-State Module
  Object-centric execution logic aligned with Sui-style state semantics and related storage-oriented workflows.

• aoxcore-cardano — UTXO Validation Module
  Validation-oriented components informed by UTXO design constraints and formal execution principles.

AOXC is being developed around a small set of engineering priorities:

• Determinism Before Expansion
  Correctness, replayability, and predictable state transitions take precedence over rapid surface-area growth.

• Explicit Trust Boundaries
  Interfaces between modules and networks should be transparent, constrained, and auditable.

• Operational Auditability
  Governance actions, deployment surfaces, and control flows should remain inspectable under real-world conditions.

• Progressive Interoperability
  Additional chains and execution environments are approached incrementally, only after baseline assumptions are validated.

This .github repository provides organization-level profile and documentation content.

For implementation details, deployments, and code artifacts, refer to the repositories published under the aoxc organization.

AOXC should currently be evaluated as an alpha-stage research and engineering initiative.

Public artifacts are available for technical scrutiny, but rapid iteration should be expected while architectural invariants, interoperability assumptions, and governance pathways continue to mature.

AOXC is building infrastructure for teams that value formal clarity, controlled interoperability, and resilient system design over short-term narrative velocity.