Hi all, following a great exchange with @bransdotcom about versioning, we’ve posted a proposal for the layer beneath registries like ASR: an ERC-721 extension binding a token to a byte-precise executable skill package — a deterministic object graph with per-file verification, a plaintext primary-document commitment that survives encryption, a closed version chain, and publication authority separate from ownership.
It is explicitly not a registry, and not a competitor to one. ASR answers where a skill is registered, how it’s discovered, installed, and attested. Ours answers what exact bytes, package version, and publication history a token commits to. They compose: a SkillRegistry token could optionally implement the interface on the same tokenId, and usage/installation attestations could pin packageHash + version — so when a skill moves on, a historical attestation still resolves to exactly the bytes that were used, rather than to a moving head.
Thread: Token-Bound Executable Skills — the artifact identity & integrity layer under skill registries (ERC-721 extension) . Spec is frozen, reference implementation is CC0 and public, and it’s live on Sepolia, and happy to run a joint interop test whenever it’s useful on your side.