Protocol core v0.1.0
Executable Python covers canonical messages, atomic state transitions, gas, validator votes, quorum certificates, and an in-memory finalized chain.
AIMB-X / public research
Published work, with the boundaries left in.
AIMB-X Labs currently publishes one tagged protocol reference, one draft RFC, and a set of local developer examples. This page links to the source material and says what each artifact does—and does not—establish.
Reading the evidence
Artifact maturity.
The status belongs to the artifact—not to an imagined future product.
Conformance suite
Twenty-eight dependency-free tests cover serialization, execution, tampering, quorum boundaries, replay, and malformed input. Passing them is evidence of this reference behavior, not a security audit.
RFC 0001
The AI advisory boundary is open design work. The draft explicitly says that no implementation is designated while it remains in Draft status.
Read Draft RFC 0001 (opens in a new tab)Market Bridge paper
The paper describes a broader architecture for agent registries, capital guardrails, adapters, settlement, and reputation. Those ideas are not the v0.1.0 implementation.
Read the technical proposalProtocol v0.1.0
Primary artifacts
Every protocol link below is pinned to the published v0.1.0 tag, so later edits cannot silently change the cited record.
System modelThe replicated-state-machine model and the authority boundaries between network, consensus, execution, proof, and interop components.Specification (opens in a new tab)Execution specificationCanonical transaction encoding, deterministic gas, atomic batches, .sync operations, and state commitments.Specification + reference code (opens in a new tab)Consensus specificationProposal validation, state-root reproduction, weighted two-thirds quorum checks, and local finalization rules.Validation and finalization (opens in a new tab)Networking boundaryThe authentication, replay protection, admission control, and resource limits required from a future transport layer.Integration requirements (opens in a new tab)Threat modelThreats handled by the reference core, plus the security obligations left to integrating systems.Security assumptions (opens in a new tab)Conformance vectorsPublished v1 inputs, gas values, identifiers, and commitments for detecting implementation drift.Machine-readable evidence (opens in a new tab)
Known limitations
What the release leaves to an integration.
The core assumes that callers authenticate vote objects before quorum verification. It supplies no transport, persistence, signing infrastructure, proof verifier, or external-chain client.
No public network deployment is presented here. A credible testnet record needs an address, deployment transaction, verified source, and block reference; v0.1.0 publishes none of those identifiers.
- Network transport and peer discovery
- Persistent storage and crash recovery
- Validator keys, rotation, and vote signatures
- Live BFT rounds, timeouts, and fork recovery
- Proof-system verification
- External-chain clients and bridge infrastructure
Developer preview
Local developer examples.
These JavaScript examples model local .sync payloads. They do not connect to a network, sign transactions, manage keys, or replace a canonical SDK.
JavaScript exampleHello .sync
The smallest complete local .sync transaction.
View source (opens in a new tab)JavaScript exampleBatch profileSeveral ordered writes in one local payload.
View source (opens in a new tab)JavaScript exampleCounterA value derived from explicit prior state.
View source (opens in a new tab)JavaScript exampleDeterministic replayOrdered transactions replayed into local state.
View source (opens in a new tab)Review path
Review and reporting.
Start with the tagged source and vectors. Use the repository’s private reporting path for a suspected vulnerability; use the RFC repository for a design objection.