Publish the boundary
A prototype should say what it omits. The current protocol release has no public network transport, persistent storage, validator key management, or cryptographic vote signatures.
AIMB-X Labs / Company
A small lab for reviewable systems.
AIMB-X Labs researches deterministic execution, verifiable AI boundaries, and resilient decentralized infrastructure. We publish early work with its limitations attached.
Read the public codeFour public project repositories, one tagged protocol release, a draft RFC process, and a technical paper.
Current public scope.
The public protocol reference is intentionally narrow: canonical transactions, atomic execution, resource metering, weighted quorum checks, and an in-memory finalized chain. It is research software, not a production validator or custody system.
That distinction matters. We would rather show a small mechanism that can be run and inspected than imply that an unfinished system has already solved networking, proof verification, economic security, or production operations.
Company record
Founded in 2023. The current public code record began in 2026.
AIMB-X Labs’ LinkedIn profile lists the company in Blockchain Services and gives 2023 as its founding year. The current GitHub organization and public repositories were opened in August 2026.
No headquarters address is published in the company’s official profiles, so no location is listed here. The public channels are the company domain, LinkedIn, GitHub, and support email.
Keep AI outside consensus authority
Our draft RFC treats model output as advisory. It cannot determine transaction validity, voting power, committed state, or safety-critical behavior.
Make execution reproducible
Canonical messages, explicit state transitions, conformance vectors, and deterministic tests make a result easier to challenge than a performance claim.
Separate a paper from a deployment
A design described in a technical paper is not independently verifiable until its source, addresses, deployment transaction, and operating assumptions are public.
Public implementation
Inspect protocol v0.1.0.
Review the implementation, specifications, threat model, conformance vectors, and known integration boundaries.
Read the protocol recordEvidence register
See what is—and is not—verified.
We separate public code, company statements, network facts, and deployment claims so they are not mistaken for one another.
Review public evidenceResearch contactContact AIMB-X Labs
Bring a specific systems question.
We welcome reproducible bug reports, protocol critiques, RFC feedback, and technically scoped collaboration proposals.