Setting a new secret doesn't provide distinguishable information for off-chain tools

Description

• Events should provide useful information for off-chain tools

• Event for setting new secret is empty struct

Risk

Likelihood:

• It occurs when setting a new secret

Impact:

• Since the struct has no fields, every emission of SetNewSecret {} is identical. If the set_secret function is called multiple times (e.g., updating the secret repeatedly), off-chain tools (like indexers, explorers, or dApps) can't differentiate between events.

• Events are stored on-chain (via the store ability) and contribute to the global state. Empty events clutter the event stream without adding meaningful history, potentially increasing query times for tools scanning the event handle.

Recommended Mitigation

Adding owner and timestamp sections provides a lot of useful information for off-chain tools