Area
Project Registry / Documentation
Complexity
Easy
File(s)
EVENTS.md vs. project_registry/src/events.rs
Problem
EVENTS.md's Project Registry section documents 8 events. src/events.rs actually publishes at least these additional events with no EVENTS.md entry: CollateralLiquidated, RateUpdated, WhitelistSet, ProjectCertified, ProposalCreated, VoteCast, ProposalExecuted, CreditQualityUpdated, ReputationUpdated, RegistryPaused/RegistryUnpaused, EmergencyAdminChanged, WhitelisterChanged, OwnershipTransferred. Off-chain indexers built strictly from EVENTS.md will silently miss all governance, multisig, and admin-role-change activity. Separately, EVENTS.md documents project_created's data field as creator: Address while the actual struct field is named owner.
Scope
In:
- Add entries for each missing event (topics, data shape, emitting function) to EVENTS.md; fix the creator/owner field-name mismatch.
Out:
- Changing event schemas/topics themselves.
Acceptance Criteria
Area
Project Registry / Documentation
Complexity
Easy
File(s)
EVENTS.md vs. project_registry/src/events.rs
Problem
EVENTS.md's Project Registry section documents 8 events. src/events.rs actually publishes at least these additional events with no EVENTS.md entry: CollateralLiquidated, RateUpdated, WhitelistSet, ProjectCertified, ProposalCreated, VoteCast, ProposalExecuted, CreditQualityUpdated, ReputationUpdated, RegistryPaused/RegistryUnpaused, EmergencyAdminChanged, WhitelisterChanged, OwnershipTransferred. Off-chain indexers built strictly from EVENTS.md will silently miss all governance, multisig, and admin-role-change activity. Separately, EVENTS.md documents project_created's data field as
creator: Addresswhile the actual struct field is namedowner.Scope
In:
Out:
Acceptance Criteria