Feat/enforce authorized sweep destination#20
Merged
phertyameen merged 2 commits intobridgelet-org:mainfrom Jan 25, 2026
Merged
Conversation
…vents for enforcing authorized sweep destination
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.
Enforce Authorized Sweep Destination
Closes #7
Overview
This PR implements destination authorization for the sweep function, allowing the contract to enforce that funds can only be swept to a pre-authorized destination address set during initialization. The implementation supports both locked mode (destination required) and flexible mode (any destination allowed).
Changes
Core Functionality
Storage Updates (
storage.rs)DataKey::AuthorizedDestinationandDataKey::Creatorset_authorized_destination(),get_authorized_destination(),has_authorized_destination()set_creator(),get_creator()Initialization (
lib.rs)initialize()to accept optionalauthorized_destination: Option<Address>DestinationAuthorizedevent when destination is setSweep Validation (
lib.rs)execute_sweep()Error::UnauthorizedDestinationif destination doesn't match authorized destination (when set)Destination Management (
lib.rs)update_authorized_destination()functionDestinationUpdatedeventError Handling
errors.rs)UnauthorizedDestination = 13Events
lib.rs)DestinationAuthorized- emitted when destination is set during initializationDestinationUpdated- emitted when authorized destination is updatedTesting
tests/integration.rs)Build Fixes
#[contracttype]attribute toDataKeyenum (required for Soroban storage)BytesAPI usage in authorization moduleed25519_verifyto use correct parameter typesrlibcrate-type for test compatibilitySecurity Features
Testing
All tests pass and cover:
Breaking Changes
None - the
authorized_destinationparameter is optional, maintaining backward compatibility.Notes