You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/stellar-contracts/tokens/rwa/rwa.mdx
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -506,6 +506,8 @@ When implementing RWA tokens, consider the following security aspects:
506
506
2.**Identity Verification**: Always verify identities before allowing token operations
507
507
3.**Compliance Validation**: Ensure compliance rules are properly configured before enabling transfers
508
508
4.**Freezing**: Use freezing mechanisms carefully as they lock user funds
509
-
5.**Recovery**: Recovery operations should have strict authorization and verification
509
+
5.**Recovery**: There are two distinct recovery flows, both requiring strict authorization:
510
+
-**Identity Recovery**: Managed by the Identity Registry Storage, transfers the identity contract reference and profile (including country data) from old wallet to new wallet, and creates a recovery mapping
511
+
-**Balance Recovery**: Managed by the RWA Token, transfers tokens from old to new account after verifying the identity recovery mapping exists (via `recovery_target()`)
510
512
6.**Pausability**: The pause mechanism should only be accessible to authorized administrators
511
513
7.**Contract Upgrades**: Consider following a secure upgrade strategy for your contracts. See: [Contract Upgrades](/stellar-contracts/utils/upgradeable)
0 commit comments