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: delegation-toolkit/concepts/environment.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ export delegatorSmartAccount;
69
69
See the changelog of the toolkit version you are using (in the left sidebar) for supported chains.
70
70
:::
71
71
72
-
Alternatively, you can use the `getDelegatorEnvironment` function to resolve the environment.
72
+
Alternatively, you can use the [`getDelegatorEnvironment`](../reference/api/delegation.md#getdelegatorenvironment) function to resolve the environment.
73
73
This function is especially useful if your delegator is not a smart account when
74
74
[creating a redelegation](../how-to/create-delegation/index.md#create-a-redelegation).
You can deploy the contracts using any method, but the toolkit provides a convenient `deployDelegatorEnvironment` function. This function simplifies deploying the Delegation Framework contracts to your desired EVM chain.
88
+
You can deploy the contracts using any method, but the toolkit provides a convenient [`deployDelegatorEnvironment`](../reference/api/delegation.md#deploydelegatorenvironment) function. This function simplifies deploying the Delegation Framework contracts to your desired EVM chain.
89
89
90
90
This function requires a Viem [Public Client](https://viem.sh/docs/clients/public.html), [Wallet Client](https://viem.sh/docs/clients/wallet.html), and [Chain](https://viem.sh/docs/glossary/types#chain)
91
91
to deploy the contracts and resolve the `DeleGatorEnvironment`.
@@ -157,7 +157,7 @@ Once the contracts are deployed, you can use them to override the delegator envi
157
157
158
158
## Override delegator environment
159
159
160
-
To override the delegator environment, the toolkit provides a `overrideDeployedEnvironment` function to resolve
160
+
To override the delegator environment, the toolkit provides an [`overrideDeployedEnvironment`](../reference/api/delegation.md#overridedeployedenvironment) function to resolve
161
161
`DeleGatorEnvironment` with specified contracts for the given chain and contract version.
Copy file name to clipboardExpand all lines: delegation-toolkit/experimental/erc-7710-redeem-delegations.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ This data encodes the authority that lets the delegate redeem the permission.
66
66
### Security considerations for `accountMeta`
67
67
68
68
When a user grants a permission, they can provide `accountMeta` which is an array of `factory` and `factoryData` values.
69
-
These calls must be executed before redeeming the permission (this is handled for you in `sendUserOperationWithDelegation`).
69
+
These calls must be executed before redeeming the permission (this is handled for you in [`sendUserOperationWithDelegation`](../reference/api/experimental-actions/bundler-client.md#senduseroperationwithdelegation)).
70
70
71
71
Because each `accountMeta` is an arbitrary call specified by the granter, it is important that these are executed carefully.
72
72
We recommend taking the following precautions:
@@ -87,7 +87,7 @@ Redeem a delegation with a [smart account](#redeem-with-a-smart-account) or an [
87
87
To redeem a delegation with a smart account, create a [`MetaMaskSmartAccount`](../how-to/create-smart-account/index.md#create-a-metamasksmartaccount)
88
88
and a [Viem Bundler Client](https://viem.sh/account-abstraction/clients/bundler).
89
89
90
-
After setting up your Bundler Client, you can extend its functionality with `erc7710BundlerActions` actions to support ERC-7710. Once extended, use `sendUserOperationWithDelegation` to redeem the permission.
90
+
After setting up your Bundler Client, you can extend its functionality with `erc7710BundlerActions` actions to support ERC-7710. Once extended, use [`sendUserOperationWithDelegation`](../reference/api/experimental-actions/bundler-client.md#senduseroperationwithdelegation) to redeem the permission.
To redeem a delegation with an EOA, create a [Viem Wallet Client](https://viem.sh/docs/clients/wallet).
171
171
172
-
After creating your Wallet Client, you can extend its functionality with `erc7710WalletActions` actions to support ERC-7710. Once extended, use `sendTransactionWithDelegation` to redeem the permission.
172
+
After creating your Wallet Client, you can extend its functionality with `erc7710WalletActions` actions to support ERC-7710. Once extended, use [`sendTransactionWithDelegation`](../reference/api/experimental-actions/wallet-client.md#sendtransactionwithdelegation) to redeem the permission.
Copy file name to clipboardExpand all lines: delegation-toolkit/experimental/erc-7715-request-permissions.md
+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
@@ -166,7 +166,7 @@ You should always verify the granted permissions and adjust your dapp's behavior
166
166
## Security considerations for `accountMeta`
167
167
168
168
When a user grants a permission, they can provide [`accountMeta`](erc-7710-redeem-delegations.md#extract-relevant-data) which is an array of `factory` and `factoryData` values.
169
-
These calls must be executed before redeeming the permission (this is handled for you in `sendUserOperationWithDelegation`).
169
+
These calls must be executed before redeeming the permission (this is handled for you in [`sendUserOperationWithDelegation`](../reference/api/experimental-actions/bundler-client.md#senduseroperationwithdelegation)).
170
170
171
171
Because each `accountMeta` is an arbitrary call specified by the granter, it is important that these are executed carefully.
[Sign the delegation](../how-to/create-delegation/index.md#sign-a-delegation) using the `signDelegation` method from `MetaMaskSmartAccount`.
117
-
Alternatively, you can use the Delegation Toolkit's `signDelegation` utility.
116
+
[Sign the delegation](../how-to/create-delegation/index.md#sign-a-delegation) using the [`signDelegation`](../reference/api/smart-account.md#signdelegation) method from `MetaMaskSmartAccount`.
117
+
Alternatively, you can use the Delegation Toolkit's [`signDelegation`](../reference/api/delegation.md#signdelegation) utility.
118
118
The signed delegation will be used later to perform actions on behalf of the delegator.
119
119
120
120
```typescript
@@ -134,7 +134,7 @@ The delegate account can now [redeem the delegation](../how-to/redeem-delegation
134
134
The redeem transaction is sent to the `DelegationManager` contract, which validates the delegation and
135
135
executes actions on the delegator's behalf.
136
136
137
-
To prepare the calldata for the redeem transaction, use the `redeemDelegation` utility function from the Delegation Toolkit.
137
+
To prepare the calldata for the redeem transaction, use the [`redeemDelegation`](../reference/api/delegation.md#redeemdelegation) utility function from the Delegation Toolkit.
Copy file name to clipboardExpand all lines: delegation-toolkit/how-to/create-delegation/restrict-delegation.md
+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
@@ -28,7 +28,7 @@ Use the `CaveatBuilder` to easily ensure that your delegations grant only the ne
28
28
29
29
## Create the caveat builder
30
30
31
-
To create the caveat builder, call the `createCaveatBuilder()` function, passing an instance of `DeleGatorEnvironment`.
31
+
To create the caveat builder, call the [`createCaveatBuilder`](../../reference/api/delegation.md#createcaveatbuilder) function, passing an instance of `DeleGatorEnvironment`.
32
32
The environment can be accessed from the `MetaMaskSmartAccount`, as in this example:
0 commit comments