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/contracts-sui/1.x/access.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ public fun wrap_admin_cap(
48
48
## Choosing a transfer policy
49
49
50
50
- Use `two_step_transfer` when the signer triggering transfer initiation is the same principal that should retain cancel authority.
51
-
- Use `delayed_transfer` when protocol safety requires on-chain lead time before transfer or unwrap execution.
51
+
- Use `delayed_transfer` when protocol safety requires on-chain lead time before transfer or unwrap execution, and when initial wrapper custody should be assigned explicitly at wrap time.
Copy file name to clipboardExpand all lines: content/contracts-sui/1.x/api/access.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -314,7 +314,7 @@ Raised when caller is not the designated prospective owner in `accept_transfer`.
314
314
use openzeppelin_access::delayed_transfer;
315
315
```
316
316
317
-
Time-locked ownership wrapper for `T: key + store`. Transfers and unwraps must be scheduled and can only execute after `min_delay_ms` elapses.
317
+
Time-locked ownership wrapper for `T: key + store`. The wrapped object is placed under a wrapper that is immediately transferred to a chosen recipient. After that, transfers and unwraps must be scheduled and can only execute after `min_delay_ms` elapses.
0 commit comments