ERC-8328 Subject-Linked Compliance Event Log
Defines append-only subject-linked compliance records with attribution, evidence, indexing, and correction provenance
ERC-165 interface ids
Computed here as the XOR of the selectors each interface defines.
| IComplianceEventLog | 0x67640da1 |
Functions this standard introduces (8)
0x648c3b52 | currentEventIndex(bytes32,uint256) | view |
0x2d1069b4 | eventByTypeAt(bytes32,bytes32,uint256) | view |
0xd671da21 | eventCount(bytes32) | view |
0xf76378f8 | eventCountByType(bytes32,bytes32) | view |
0xed098a5b | getEvent(bytes32,uint256) | view |
0x80c7f3b7 | isEventCurrent(bytes32,uint256) | view |
0x6ebf84b9 | lastRecordedEventByType(bytes32,bytes32) | view |
0x0c9b00cb | recordEvent(bytes32,bytes32,bytes32,bytes32,bytes32,(address,bytes32)[],bytes32,string,bytes32,bytes,bytes32,uint64,uint256) |
Events (1)
Topic0 is the keccak256 hash of the signature, which is what a log filter matches on.
0xc6d1a70e471929b8a0a33c113f12c7899c5d4b421d8fc96bc9191372b9a9fa11 | ComplianceEventRecorded(bytes32,bytes32,address,uint256,bytes32,bytes32,uint64,uint256) |
Depends on (1)
Proposals this one names in its requires field.
What the specification covers
Compare with
Parsed from the canonical specification · discussion