TL;DR: Alongside the ERC-8415 proposal (Asynchronous Register Projection for NFTs, ethereum/ERCs#2149), we’ve made ERC8415-Kit publicly available under CC0 1.0 Universal. It is one implementation of the spec — adopting ERC-8415 does not require using it, and independent implementations are welcome.
- Repository: GitHub - GiraffeJP/ERC8415-Kit · GitHub
- License: CC0 1.0 (public domain dedication)
- Status: Reference infrastructure for development & integration testing; production deployment is separate work.
What the Kit provides
The Kit is a practical starting point for building and testing ERC-8415 integrations:
- An append-only projection engine for the register-confirmed holder record, with a durable append-only journal
- Proof-profile verification and atomic admission
- Solidity projection and settlement components with a local-EVM test suite
- Temporal query APIs (
holderAsOf,isFinalAsOf,openGapOf,entryAt, …) - JavaScript and Python SDKs
- A shared conformance test suite: 169 Node tests (including the 20 mandatory conformance tests) and 32 local-EVM tests
- A record-date payout example that reads and acts within one transaction
npm run verify runs the full suite locally — no wallet, external RPC endpoint, testnet funds or private key needed.
The core distinction
The central design choice of ERC-8415 is unchanged, and the Kit preserves it exactly:
The tradeable token position (
ownerOf) and the register-confirmed holder are separate records.
These two sequences can diverge in flight and must be queried separately:
| Question | Answered by |
|---|---|
| Historical holder resolution | The projection (holderAsOf) |
| Whether that answer is final | Finality (isFinalAsOf) |
| Whether a settlement is in flight | Open gaps (openGapOf, openedAt) |
The Kit records what happened; it does not adjudicate legal title, guarantee eventual alignment, or prescribe remedies such as cancellation, escrow, or refunds. Those are matters for the transaction terms between parties.
Scope and limitations
To set expectations clearly:
- The specification defines conformance; the Kit is one implementation. Interoperability is determined by the conformance tests, not by this codebase.
- Adopting ERC-8415 does not require using our software or services. Independent implementations are explicitly welcome.
- The current code is reference infrastructure for development and integration testing. Local on-chain deployment (Stage 3) and durable storage are now in place, and public Hoodi testnet results are published in the repo (
docs/testing/). A production proof-verifier, independent registrar operation and production deployment remain outstanding — see the repo’s README andDELIVERY-EVIDENCE.md.
Why we’re publishing it
We’re publishing the Kit to lower the cost of adoption and to make implementation choices open to inspection, testing, and improvement. Conformance should be demonstrable from shared tests, not assumed from a single codebase.
Feedback & contributions
We welcome:
- Technical review of the projection model and verification engine
- Integration feedback from teams building against ERC-8415
- Contributions, particularly around developer interfaces and cross-implementation conformance
If you’re working on an independent implementation, we’d especially like to compare notes on the conformance suite so implementations can interoperate.
Related: see the ERC-8415 proposal thread for the normative specification and semantic model.