بحث موثق بالمصادر: Erc3643 VS Solana Transfer
يظهر نص المقال باللغة الإنجليزية الأصلية بعد التحقق. ستُضاف الترجمة بعد مراجعة المصادر.
Verified Fact Boundary
1. EIP-3643 describes a permissioned token standard whose transfer behavior differs from standard ERC-20 because of identity and compliance checks. 2. ERC-3643 documentation says its compliance framework can add rules for token offerings and transfers and relies on on-chain identity. 3. Solana Transfer Hook documentation says the interface can execute custom instruction logic on every transfer for a specific mint account. 4. Solana transfer documentation distinguishes standard transfer instructions and Token Extension transfer variants. 5. A transfer hook can enforce technical execution conditions without by itself proving legal ownership, investor status, redemption or secondary-market rights. 6. A regulated-token compliance standard can define transfer eligibility without proving that every wallet, custodian or marketplace client will support the route.
إظهار أقل
Decision Matrix
جدول المقال: مرّر أفقيًا أو انقل التركيز إلى منطقة الجدول واستخدم مفاتيح الأسهم.
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Control origin | the restriction may come from identity registry, compliance module or hook program | identify which component can approve, reject or fail a transfer | legal effect of a technical rejection |
| Client dependency | hook-enabled transfers may require clients to include additional accounts | test wallet, custodian and dapp support before assuming portability | whether every downstream venue resolves hook metadata correctly |
| Issuer boundary | tokenized assets may require issuer records beyond chain state | map issuer, transfer agent, identity issuer and token contract separately | offchain recordkeeping and investor recourse |
| Secondary transfer | permissioned transfer does not equal free secondary liquidity | check holder eligibility, rule modules and venue support before transfer | future market depth and jurisdictional limits |
| Stop condition | do not equate hook success with asset-rights completeness | pause when rights, identity status, client support or redemption path is unclear | tax, legal and custody treatment remain outside the technical docs |
Source Map
- Ethereum Improvement Proposals: ERC-3643: T-REX - Token for Regulated EXchanges (erc3643-eip)
- ERC3643 Association: Built-in Compliance Framework (erc3643-compliance)
- Solana: Token Extensions: Transfer Hook (solana-transfer-hook)
- Solana: Transfer Tokens (solana-token-transfer)
Control Notes
1. Control origin
Control origin is the point where public documentation must become an operating rule. In this package, it means the restriction may come from identity registry, compliance module or hook program. The practical action is to identify which component can approve, reject or fail a transfer. The unresolved edge is legal effect of a technical rejection, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
2. Client dependency
Client dependency is the point where public documentation must become an operating rule. In this package, it means hook-enabled transfers may require clients to include additional accounts. The practical action is to test wallet, custodian and dapp support before assuming portability. The unresolved edge is whether every downstream venue resolves hook metadata correctly, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
3. Issuer boundary
Issuer boundary is the point where public documentation must become an operating rule. In this package, it means tokenized assets may require issuer records beyond chain state. The practical action is to map issuer, transfer agent, identity issuer and token contract separately. The unresolved edge is offchain recordkeeping and investor recourse, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
4. Secondary transfer
Secondary transfer is the point where public documentation must become an operating rule. In this package, it means permissioned transfer does not equal free secondary liquidity. The practical action is to check holder eligibility, rule modules and venue support before transfer. The unresolved edge is future market depth and jurisdictional limits, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
5. Stop condition
Stop condition is the point where public documentation must become an operating rule. In this package, it means do not equate hook success with asset-rights completeness. The practical action is to pause when rights, identity status, client support or redemption path is unclear. The unresolved edge is tax, legal and custody treatment remain outside the technical docs, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.
The operating test is narrow.
Known Unknowns
- legal effect of a technical rejection
- whether every downstream venue resolves hook metadata correctly
- offchain recordkeeping and investor recourse
- future market depth and jurisdictional limits
- tax, legal and custody treatment remain outside the technical docs
Practical Takeaway
ERC-3643 and Solana Transfer Hook both affect token transfer control, but they are not interchangeable compliance proofs. ERC-3643 frames a regulated token standard where identity and compliance checks can gate token holders and transfers. Solana's Transfer Hook extension lets a Token-2022 mint require a CPI to a custom program on every transfer and may require extra accounts resolved by clients. The tokenized-asset decision is therefore to identify whether the control is identity-registry based, hook-program based, client-integration dependent, issuer-controlled or merely a technical transfer condition. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, API key, pool route, stablecoin balance, tokenized asset or policy framework will work under every future condition.
مواضيع وأدوات:قارن بين منصتين