Summary
When a creator registration is attempted with a wallet address that is already registered, the error is returned to the client but not logged. A warn-level structured log at the duplicate detection point helps identify whether duplicates are accidental retries or deliberate attempts.
Scope
- identify where duplicate wallet address detection occurs during creator registration
- add a warn-level structured log with the duplicate address and request ID
- ensure the address is not logged in plain text if masking is required by policy
Acceptance Criteria
- a duplicate wallet address registration emits a warn-level log
- the log includes sufficient context to identify the request
- the client error response is unchanged
Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg
Summary
When a creator registration is attempted with a wallet address that is already registered, the error is returned to the client but not logged. A warn-level structured log at the duplicate detection point helps identify whether duplicates are accidental retries or deliberate attempts.
Scope
Acceptance Criteria
Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg