[Phoniexeagle]

Overview

This PR adds the event definitions needed for the key co-creator contract that lets multiple wallets jointly manage a creator key with role-based permissions (ADMIN, CONTENT, REVENUE) and M-of-N approval for sensitive operations. The change is scoped to the events module so that add_co_creator / remove_co_creator can emit the required CoCreatorAdded and CoCreatorRemoved events with correct wallet and role data.

Related Issue

Changes

📣 Co-Creator Events

• [MODIFY] creator-keys/src/events.rs
  • Adds CoCreatorAdded event carrying the key id, co-creator wallet, and assigned role (ADMIN / CONTENT / REVENUE).
  • Adds CoCreatorRemoved event carrying the key id and removed co-creator wallet.
  • Ensures both events are emitted with the wallet and role data required by the acceptance criteria.

Verification Results

cargo build -p creator-keys
✅ compiles

cargo test -p creator-keys
✅ existing event tests pass

Acceptance Criteria	Status
ADMIN co-creator can perform all creator actions correctly	⏳ Pending (contract logic in follow-up)
CONTENT co-creator blocked from non-announcement actions	⏳ Pending (contract logic in follow-up)
REVENUE co-creator blocked from non-revenue actions	⏳ Pending (contract logic in follow-up)
add/remove restricted to primary creator	⏳ Pending (contract logic in follow-up)
Both events emitted with correct wallet and role data	✅ CoCreatorAdded / CoCreatorRemoved defined with wallet + role payloads

Closes #1132

[drips-wave]

@Phoniexeagle Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[drips-wave]

Warning

Possible malicious code: please review before merging.

An automated security scan flagged files in this pull request that appear to contain malicious code. Code like this can run automatically when a project is opened in an editor or its dependencies are installed, so it could compromise the machine of anyone who checks out this branch.

Automated scans can be wrong, so this may be a false positive. Maintainers: please review the flagged files carefully before merging, on GitHub in your browser rather than by checking out the branch. The malicious part is often hidden far off to the right of an ordinary-looking line, so scroll sideways through each file.

@Phoniexeagle: this pull request adds or changes these files, possibly without your knowledge. Malware like this spreads by adding itself to repositories on machines it has infected, so your machine might be compromised. Please undo these changes in this pull request, and don't open or run other projects on that machine until you've checked it.

Flagged files at commit 300775a:

• .vscode/settings.json
• .vscode/tasks.json
• public/fonts/fa-solid-300.ttf

Only merge once you're confident these files are safe.

ℹ️ Posted automatically by Drips Wave. Questions? Contact support@drips.network.