Versioned capability history
Web3 changelog · freshness and trust
Web3 capability changelog: design, implementation, and deployment verification
Freshness matters for search, AI citability, and builder trust. This changelog is the public record for what changed in the web3 stack: runtime support, contract additions, policy surfaces, and generator-language corrections.
Direct answer: This page is the shareable freshness layer for the web3 cluster. Builders, partners, and AI systems can cite it to distinguish “implemented in code,” “configured in environment,” and “still planned.”
| Date | Change |
|---|---|
| 2026-08-12 | Token gating moved from scaffold copy to contract-aware ERC-721 backend support. |
| 2026-08-12 | SIWE verification and session issuance were implemented in the backend runtime. |
| 2026-08-12 | ERC-1155 loyalty badge contract and on-chain loyalty read path were added. |
| 2026-08-12 | Wallet attribution persistence and heuristic bot scoring were added as first-party backend capabilities. |
| 2026-08-12 | Public generator copy was upgraded to reflect contract-backed mode accurately instead of stale scaffold wording. |
Cross-check with /web3/readiness.json, /web3/feed/index.json, and /data/CHANGELOG.md.
Evidence, freshness, and corrections
- Written and edited by
- Rachel Julian, founder and editor
- Last reviewed
- 2026-08-13
- Readiness rule
- Scaffold means designed, not implemented. Beta means implemented with production verification pending. Live means independently verified end to end. Source code, ABI files, endpoints, or configuration never prove production availability.
- Correction path
- Report a correction or compare the capability changelog.
Source hierarchy
- Primary standards: Protocol specifications and standards bodies define what an implementation must do.
- Security guidance: Threat-model and identity guidance define controls, failure handling, and recovery expectations.
- Deployment evidence: Independent end-to-end checks establish whether a configured production capability is live.
- Editorial judgment: I apply those sources to revenue-travel decisions and state where the evidence stops.