The protocol emits events to signal that a person has been checked once or twice, including the address involved and the resulting status. These events are intended to be consumed by off-chain services such as indexers, monitoring tools, or analytics systems.
The CheckedOnce and CheckedTwice events do not mark any parameters as indexed, which prevents efficient filtering by address or status at the log topic level and forces off-chain consumers to scan and decode all emitted events.
Likelihood:
Off-chain consumers query event logs by person address during routine indexing, monitoring, or analytics workflows
Event volume grows over time, increasing the cost and complexity of full log scans
Impact:
Reduced efficiency and higher operational cost for off-chain indexing and monitoring systems
Degraded developer experience and more complex integration logic for downstream consumers
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.