AIMB-XLABS
Public evidence register

What can be checked today.

This page separates published code, public network facts, and first-party statements. It does not turn one kind of evidence into another.

Review the GitHub organization (opens in a new tab)Read the technical paper (opens in a new tab)
Deployment evidence

Reference environment. No deployment record.

The current AIMB-X technical proposal names Avalanche Fuji as a reference environment; it does not present a traceable AIMB-X deployment.

No AIMB-X deployment identifiers are published

A public testnet can only be used as deployment evidence when readers can follow a specific onchain identifier. The publication currently provides no AIMB-X contract address, deployment transaction, verified source record, or block number.

  • AIMB-X contract addressNot published
  • Deployment transaction hashNot published
  • Verified contract sourceNot published
  • Deployment block numberNot published
Open source

Four public project repositories.

These repositories are the current public engineering record. Their maturity labels are kept distinct so a preview or example is not presented as a release.

aimbx-sdk

JavaScript

Canonical transaction construction and a minimal JSON-RPC client.

Developer previewPublic source repository
Open repository (opens in a new tab)

aimbx-examples

JavaScript

Runnable local examples for ordered .sync payloads and deterministic replay.

Local examplesPublic source repository
Open repository (opens in a new tab)
Network reference

Avalanche Fuji, without the guesswork.

These are Fuji C-Chain connection details from Avalanche documentation. They describe the public network; they do not identify an AIMB-X contract on it.

Check the Avalanche documentation (opens in a new tab)
Public testnet
Avalanche Fuji C-Chain
Chain
C-Chain
Chain ID
43113 0xA869
Native currency
AVAX
Official public RPC
https://api.avax-test.network/ext/bc/C/rpc
Historical references

Older work, classified by what remains verifiable.

These references appeared on the company LinkedIn page before the current GitHub organization opened. They are recorded here for continuity, not presented as active products or part of the current repository count.

November 2025

zkLayer

Testnet bytecode confirmed

Matching 7,240-byte runtime code is present at the addresses named in the linked paper on Ethereum Sepolia and Scroll Sepolia. Both contracts were created by the same deployer within two minutes.

This is a historical company-linked reference, not a current AIMB-X product record. No source repository, ABI, verified source, zkVerify job ID, IPFS CID, or proof artifact is published with the paper, so the claimed functionality is not reproducible from public materials.
Company post (opens in a new tab)Linked technical note (opens in a new tab)Sepolia contract (opens in a new tab)Sepolia creation transaction (opens in a new tab)Scroll Sepolia contract (opens in a new tab)Scroll Sepolia creation transaction (opens in a new tab)
December 2025

SCFVS

Prototype only

The company post links to a four-commit prototype in a personal GitLab namespace. Its Coq and Iris integrations explicitly use placeholders and simulated success paths; no tag, release, or public CI run is available.

The repository is useful as historical prototype evidence, but it does not support a production-ready or formally verified claim.
Company post (opens in a new tab)Public prototype (opens in a new tab)Coq engine evidence (opens in a new tab)Iris engine evidence (opens in a new tab)
Source register

Follow every reference.

Last reviewed . Repository and network state can change after this date.