Add transfer restrictions management functionality - #335
Merged
Conversation
F-OBrien
requested review from
VictorVicente,
mpastecki and
quinndiggitypolymath
as code owners
November 7, 2025 20:23
F-OBrien
force-pushed
the
transfer-restrictions
branch
from
November 13, 2025 10:35
105c20f to
fa4e67a
Compare
🔒 SSH Commit Auth & Fast-Forward Merge ResultsExecution Time: 2025-11-14T12:07:40.154Z ✅ SSH Commit Authentication: SUCCESSSummary: 1/1 commits passed authentication (100.0%) ✅ Fast-Forward Merge: SUCCESSMerge Commit: Details: Successfully fast-forwarded develop to transfer-restrictions (no merge commit created) 📊 SummaryAuthentication: success • Merge: success • Commits Validated: 1
🤖 Generated by SSH Commit Auth & Fast-Forward Merge Action |
F-OBrien
force-pushed
the
transfer-restrictions
branch
from
November 13, 2025 10:39
fa4e67a to
f45d630
Compare
mpastecki
approved these changes
Nov 13, 2025
F-OBrien
force-pushed
the
transfer-restrictions
branch
from
November 13, 2025 18:30
f45d630 to
6a5c156
Compare
F-OBrien
force-pushed
the
transfer-restrictions
branch
from
November 14, 2025 11:52
6a5c156 to
09d480d
Compare
mpastecki
approved these changes
Nov 14, 2025
Collaborator
Author
|
/fast-forward |
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.
This pull request adds support for managing transfer restriction exemptions for fungible assets, including the ability to view, add, and remove exemptions for specific identities. It introduces new modal components to handle exemption management in the asset control center, updates the asset context and provider logic to fetch and expose exemption data, and extends asset action hooks to provide methods for modifying exemptions and transfer restrictions.
Transfer Restriction Exemptions Management:
AddExemptionsModalandEditTransferRestrictionModalfor adding and editing transfer restriction exemptions and restrictions in the asset manager UI. These modals handle user input, validation, and transaction execution for exemption management. [1] [2] [3]AssetContext/constants.tsandprovider.tsx) to fetch and expose exemption data (TransferRestrictionExemption) as part of asset details, allowing UI components to display current exemptions. [1] [2] [3] [4] [5]Asset Actions Extension:
useAssetActionshook to include methods for setting transfer restrictions, and adding/removing exemptions, with type safety and error handling for fungible assets. These methods are now available for use throughout the asset manager. [1] [2] [3]Type and Interface Improvements:
These changes collectively enable a more robust and user-friendly workflow for managing transfer restriction exemptions on fungible assets within the asset manager UI.