Hi ryanio, we’ve posted a proposal that may be complementary to ERC-8257: an ERC-721 extension binding a token to a self-contained, byte-precise executable artifact (deterministic object graph, per-file verification, closed version chain).
The distinction we see: 8257 registers live tool endpoints and their access conditions; some “tools” in the agent world are instead self-contained packages an agent fetches and runs locally. For those, an 8257 manifest could reference a token-bound artifact externally by content hash, the registry keeps its role, the artifact gains a verifiable identity. We deliberately have not defined any field names for this, since that’s yours to shape.
Thread: Token-Bound Executable Skills — the artifact identity & integrity layer under skill registries (ERC-721 extension) . Would genuinely value your view on whether an external artifact-reference profile fits the manifest model, and what it should look like.