Audit `events.rs` topic naming for consistency with the contracts' event topics

[fejilaup-cloud]

Labels: bug, api-server
Priority: Medium
Estimated Time: 1 hour

Description:
api-server/src/events.rs presumably mirrors or consumes the contract-level event topics (REVOKE_TOPIC, TRANSFER_TOPIC, BATCH_VERIFY_TOPIC in ip_registry/src/types.rs, plus the swap contract's own topics). Confirm the API server's topic constants stay in lockstep with the contracts' rather than being hand-copied and prone to drift.

Tasks:

• Audit every topic string/symbol used in events.rs against the contracts' types.rs definitions
• Add a shared source of truth (generated constants or a shared crate) if currently duplicated by hand
• Add a test asserting the API server can parse every event topic the contracts actually emit, including the newer Fix: accept_swap does not transfer payment to escrow #5/Implement IP Delegation with Tiered Access  #427-Add IP Commitment Audit Trail Immutability  #436-style issue-tagged topics

[Peculiarr7]

Hi! I’m a full-stack developer with a strong blockchain background, and I’m confident I can resolve this issue quickly and effectively. I’ll deliver a clean, reliable solution with immediate attention to detail, ensuring it’s completed as soon as possible. Please assign it to me—I’m ready to get started right away.