fix(globe-wallet): emit distinct recovery_executed event alongside admin_transferred (#91) - #103
Closed
s6pa1rta3n-lab wants to merge 1 commit into
Closed
fix(globe-wallet): emit distinct recovery_executed event alongside admin_transferred (#91)#103s6pa1rta3n-lab wants to merge 1 commit into
s6pa1rta3n-lab wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of Changes
Closes #91
This PR distinguishes emergency guardian recovery events from routine admin key rotations while preserving full backward compatibility for existing indexers and client applications.
Design Decision & Rationale
GlobeWallet::execute_recoveryandGlobeWallet::accept_adminboth published the identicaladmin_transferredevent with payload(old_admin, new_admin). Off-chain security monitoring and user alert pipelines could not distinguish routine key maintenance from an emergency wallet seizure without fragile out-of-band correlation against preceding approval events.execute_recoverycontinues to publishadmin_transferredwith(old_admin, new_admin)unchanged so existing mobile apps and indexers relying on this event continue operating seamlessly.execute_recoverypublishes a distinctrecovery_executedevent carrying(old_admin, new_admin, approvals: Vec<Address>).(Symbol::new(&env, "recovery_executed"),)— adheres to the established contract lifecycle naming pattern (recovery_initiated,recovery_approved,recovery_cancelled, andupgrade_executed).(old_admin: Address, new_admin: Address, approvals: Vec<Address>)— provides the full security context to alerting systems, explicitly identifying the prior admin, the new admin, and the specific quorum of guardians who approved the recovery.GlobeWallet::accept_admincontinues to publish onlyadmin_transferred, ensuring routine key rotations do not trigger emergency recovery alerts.Checklist & Definition of Done
execute_recoveryemits both the existingadmin_transferredevent (unchanged) and the newrecovery_executedevent.recovery_executedpayload contains(old_admin, new_admin, approvals).test_execute_recovery_emits_both_admin_transferred_and_recovery_executed_eventstesting both events and payloads upon recovery execution.test_accept_admin_routine_transfer_emits_only_admin_transferred_eventproving routine transfer only emitsadmin_transferredwithout anyrecovery_executedevent.cargo test --workspace).Test Verification
Payout Routing
0xF46C9F6d70C50BF81ef3588AB523a90a594a2F89GCL6OXAMLD75BMTINA6EMRUDWK5THQUSHMYNLSNBCJAPZJHNYJTUNIBC