Transfer#1031
Open
Dev-Zully wants to merge 3 commits into
Open
Conversation
|
@Dev-Zully is attempting to deploy a commit to the naijabuz's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
[FE-52] Build transfer restrictions management UI — accredited investor and geographic allowlists
Overview
The assetsup contract supports transfer restrictions — only accredited investors or users from specific geographic regions can receive tokens. This admin UI manages those allowlists. Depends on BE-60 and the transfer_restrictions module in the contract.
Context
Add a "Transfer Restrictions" section to the tokenized asset management page (admin only)
Contract source: contracts/assetsup/src/transfer_restrictions.rs — manages accredited investor list and geographic allowlist
Backend endpoints needed: GET/POST/DELETE /stellar/assets/:id/restrictions/investors and GET/POST/DELETE /stellar/assets/:id/restrictions/regions
Acceptance Criteria
"Transfer Restrictions" tab visible on tokenized assets (admin only)
Two sections: "Accredited Investors" and "Geographic Restrictions"
Accredited Investors: table of approved Stellar addresses (truncated display), add button (input for address), remove button per row
Geographic Restrictions: list of allowed country codes (ISO 3166-1 alpha-2), add button (country code input or dropdown), remove button per row
Toggle switch: "Restrictions Enabled" — when off, any address can receive tokens; when on, only allowlisted addresses can
Each add/remove operation submits a Stellar transaction — show confirmation with tx hash
Warning banner when restrictions are disabled: "Token transfers are currently unrestricted. Enable restrictions to control who can receive tokens."
closes #989
[FE-49] Build multi-signature transfer approval UI — pending approvals queue and sign flow
Overview
Some asset transfers require approval from multiple authorised signers before they execute — enforced by the multisig_transfer smart contract. This UI shows pending transfer requests and allows signers to review and approve or reject them. Depends on BE-61 and the multisig contract.
closes #986
Context
Route: frontend/app/(dashboard)/approvals/page.tsx
The multisig_transfer contract (contracts/multisig_transfer/) manages approval rules and transfer requests
Backend will need a GET /stellar/transfers/pending and POST /stellar/transfers/:id/approve endpoint (coordinate with BE-61)