v1.1.0 - AIP for AIP #1
githubscum
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
AIP v1.1.0 - "AIP for AIP"
This is the first public release of the Agent Interoperability
Protocol (AIP) as a standalone, brand-neutral, open-source module.
v1.1.0 aligns the reference implementation to the canonical AIP
whitepaper, ships a real
aip-attest-v1Poseidon-Merkle-in-circuit,and - most importantly - moves the reference implementation from
AGPL-3.0 to Apache License 2.0 with an explicit patent grant.
The protocol is meant to be adopted. Permissive licensing is the
mechanism. The spec remains CC BY 4.0; the implementation is now
permissive so anyone - including closed-source products - can ship
AIP primitives without contagion to their host project.
What's new in v1.1.0
The headline: Apache-2.0 with explicit patent grant
The reference implementation is now Apache License 2.0. The spec
(under
docs/aip-v1.0-spec.mdanddocs/AIP-whitepaper.md) isCC BY 4.0. The combination - permissive reference impl + permissive
spec - is what makes AIP a credible foundation for third-party stacks.
The change from AGPL-3.0-or-later to Apache-2.0 is intentional and
documented in
docs/AIP-whitepaper-concise.md§10.1. The reasoning,in two sentences: AGPL was correct for a host product but wrong for
a protocol that aspires to be a public primitive. Apache-2.0
maximizes adoption (no copyleft contagion for adopters) while
preserving an explicit patent grant.
Wire-format alignment to the whitepaper
v1.1.0 is wire-breaking with v1.0.1. The reference impl now
matches the canonical spec.
§4):messageId→envelopeId,sender.did→from,recipient.did→to,timestamp→issuedAt. Newrequired fields:
expiresAt(defaultissuedAt + 5 min) andpreviousHash(chain anchor).§10):auditId→entryId,actorDID→actorAgentType,timestamp→issuedAt,previousEntryHash→previousHash. New required field:aipVersion: "1.1.0".§5):did:aip:<AGENT_TYPE>:<base32>(CrockfordBase32 of a 128-bit CSPRNG). The v1.0.1
AIP_NAMESPACEenv varis removed. The AIP module is fully brand-neutral at the contract
level.
§5.2): W3CverificationMethodarray withEd25519VerificationKey2020keys. v1.0.1'spublicKey/controller/ownerfields are gone.§6): 2-stepHANDSHAKE_OFFER/HANDSHAKE_REPLYwith capability intersection. The 4-stepHELLO/CAPABILITY/ACCEPT/REJECT state machine is gone.
§12): numeric0..3(SELF_DECLARED,HANDSHAKE_SIGNED,ZKP_ATTESTED,MULTI_ISSUER).§13): canonicalPENDING → RUNNING → COMPLETE | FAILED | CANCELLED.Day-0 cleanup (2026-07-04)
Two corrections to v1.1.0 applied before the public announcement. No
wire-format change.
aip-attest-v1circuit shipped. v1.1.0 originally bundleda
circom_runtimepolynomial-iteration test circuit under thefilename
aip-attest-v1.{wasm,zkey}. The filename promised onething and the bytes delivered another. v1.1.0 cleanup replaces
these with a real
aip-attest-v1Poseidon-Merkle-in-circuit(
circuits/aip-attest-v1.circomsource committed, verificationkey SHA-256 pinned in
src/attestation.js). The single-partyaip-pots-v1trusted-setup transcript is committed atcircuits/aip-attest-v1.pots-transcript.txt.AIP_ERR_051andAIP_ERR_052allocated. v1.1.0 originallyreused
AIP_ERR_020(registered asCAPABILITY_EXPIRED) foraipVersionmismatch andAIP_ERR_013(registered asTASK_PAYLOAD_TOO_LARGE) forissuedAtclock-skew. The legacycodes retain their original semantics; the new codes are the only
ones used for envelope-version and envelope-freshness failures
going forward.
The protocol used to claim itself:
dev-logs/AIP is shipped with a reference implementation of its own
selective-disclosure pattern under
dev-logs/. The pattern: asingle Ed25519 key signs two independent hash-chained audit logs -
one private (the source of truth, kept off-disk from the public
repo), one public (a curated projection of the private log, committed
to the repo). The two logs share a key but have no cryptographic
link to each other. Projection, not redaction: a public entry is a
fresh signed entry, with its own
entryHashandsignature, thatreferences the source entry by
entryIdinpayload.reissuedFrom.This is AIP used to claim priority for AIP - without depending on
any third party (no arXiv endorsement, no institutional sign-off).
The v1.1.0 release artifacts are OpenTimestamps-anchored to the
Bitcoin blockchain; the OTS proofs are committed at
dev-logs/ots/. The whitepaper is atdocs/AIP-whitepaper.md; thearXiv-submission-length concise version is at
docs/AIP-whitepaper-concise.mdanddocs/AIP-whitepaper-concise.pdf.See
dev-logs/SELECTIVE-DISCLOSURE.mdfor the design pattern anddev-logs/OPS.mdfor the priority-proof and distribution playbook.Quickstart
For a full end-to-end example, see
examples/and the concisewhitepaper.
Test results
npm test- 24/24 passing (8 envelope + 5 audit + 5handshake + 6 attestation)
npm run smoke- 14/14 passing (brand-neutrality, publicAPI surface, circuit artifacts)
dev-logs/verify- green (private + public chains signed, nodrift)
What's deferred to v1.2
currently the permitted variant per
§5.3.7)aip-pots-v1transcript is committed; the upgrade to amulti-party ceremony is mechanical)
LIGHTWEIGHT_HANDSHAKEinterop mode body (§6.5- the flagis plumbed; the JWT issuance/verification is the v1.2 work)
§11)surface until v1.2)
See
docs/AIP-LAUNCH.mdfor the full v1.2 roadmap.License
(
LICENSE)Commons Attribution 4.0 International (
CC-BY-4.0)Attribution
AIP v1.1.0 is released by Isaac Liem
(ORCID 0009-0006-2476-1615).
AIP is brand-neutral at the contract level: the module refuses to
construct a DID, sign an envelope, or write an audit entry until
the host application supplies its own
DIDProvider. The brand-neutrality of the implementation is what makes the open-source
nature of the protocol credible - any host, any deployment, any
founder can use these primitives without leaking their identity.
Security
Vulnerability disclosure: see
SECURITY.md. Please do not filepublic issues for security-relevant findings.
Links
docs/aip-v1.0-spec.mddocs/AIP-whitepaper.mddocs/AIP-whitepaper-concise.mdand
docs/AIP-whitepaper-concise.pdfdocs/AIP-LAUNCH.mdCHANGELOG.mdKNOWN-LIMITS.mddev-logs/README.mddev-logs/SELECTIVE-DISCLOSURE.mddev-logs/OPS.mdThis discussion was created from the release v1.1.0 - AIP for AIP.
All reactions