Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 14 additions & 30 deletions ERCS/erc-8329.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,8 @@ title: Subject-Linked Impact Snapshot Log
description: Defines append-only subject-linked impact snapshots with correction provenance, methodology versioning, and attestations
author: Chris Turner <c.turner@kula.com>, David Hay (@david-hay), Reagan Simpson (@krumg111), Collins Musyimi (@Musyimi97)
discussions-to: https://ethereum-magicians.org/t/erc-8329-subject-linked-impact-snapshot-log/28938
status: Review
status: Last Call
last-call-deadline: 2026-10-19
type: Standards Track
category: ERC
created: 2026-07-05
Expand All @@ -13,7 +14,8 @@ requires: 165

## Abstract

This ERC defines an append-only interface for reporting quantitative impact
This Ethereum Request for Comments (ERC) defines an append-only interface for
reporting quantitative impact
indicator snapshots against application-defined subjects. Each snapshot records
a signed value, decimal precision, unit, completed measurement period,
methodology commitment and location, reporter, recording time, and correction
Expand Down Expand Up @@ -111,6 +113,8 @@ is greater than the snapshot it corrects and therefore cannot be zero.
A compliant log MUST implement:

```solidity
pragma solidity ^0.8.20;

interface IImpactSnapshotLog {
struct IndicatorSnapshot {
bytes32 subjectId;
Expand Down Expand Up @@ -203,10 +207,10 @@ MUST handle the declared precision safely and MUST NOT assume the value is
nonnegative.

`unit` SHOULD be the `keccak256` hash of a documented canonical unit string.
Applications SHOULD use SI or Unified Code for Units of Measure
(UCUM)-compatible representations when available and MUST document exact case,
spelling, pluralization, and conversion rules for custom or zero-valued unit
identifiers.
Applications SHOULD use International System of Units (SI) or Unified Code for
Units of Measure (UCUM)-compatible representations when available and MUST
document exact case, spelling, pluralization, and conversion rules for custom
or zero-valued unit identifiers.

This ERC does not require a nonzero `subjectId`, `indicatorId`, or `unit`.
Applications requiring stricter namespaces MUST enforce and document them.
Expand Down Expand Up @@ -369,6 +373,8 @@ unit from `indicatorId` alone.
Attestation is OPTIONAL. An implementation supporting it MUST implement:

```solidity
pragma solidity ^0.8.20;

interface IImpactAttestation {
struct Attestation {
address attestor;
Expand Down Expand Up @@ -440,6 +446,8 @@ Methodology versioning is OPTIONAL. An implementation supporting it MUST
implement:

```solidity
pragma solidity ^0.8.20;

interface IMethodologyVersioning {
event MethodologySuperseded(
bytes32 indexed subjectId,
Expand Down Expand Up @@ -606,30 +614,6 @@ An attestor's changed view is itself relevant history. Appending the later
assessment preserves both statements and lets consumers apply their own
recency and credential policies.

### Prior Art

The Onchain Representation for Audits proposal defines on-chain audit-report
representation. This ERC defines quantitative, period-bounded indicator time
series with corrections and methodology lifecycle semantics.

The On-Chain Verifiable Credentials proposal defines on-chain verifiable
credentials. Credentials can support reporter or attestor authorization but do
not define this snapshot model.

Generic attestation systems can represent impact claims through custom schemas.
This ERC defines a dedicated storage and query interface for indicator periods,
correction chains, methodology transitions, and snapshot-specific assessment
histories.

Impact-certificate systems can represent broad claims, evaluations, or funding
relationships. This ERC is narrower: it standardizes subject-linked
quantitative snapshots and their lifecycle rather than ownership of an impact
claim.

Carbon-credit token systems represent issuance, transfer, and retirement of
specific environmental assets. This ERC does not tokenize credits or prevent a
reported measurement from being claimed elsewhere.

## Backwards Compatibility

This ERC introduces new interfaces and does not modify existing token,
Expand Down
Loading