@@ -64,16 +64,16 @@ to `eth_sendTransaction` and `eth_getTransactionReceipt` when they are not avail
64
64
65
65
Requests that the wallet deliver a group of function calls on-chain from the user's wallet.
66
66
67
- * The wallet MUST send these calls in the order specified in the request.
68
- * The wallet MAY send all the function calls as part of a single transaction, or multiple transactions.
69
- * Dapps MUST NOT rely on the calls being sent in an atomic transaction, i.e. other untrusted calls may be
67
+ - The wallet MUST send these calls in the order specified in the request.
68
+ - The wallet MAY send all the function calls as part of a single transaction, or multiple transactions.
69
+ - Dapps MUST NOT rely on the calls being sent in an atomic transaction, i.e. other untrusted calls may be
70
70
included between each of the requested function calls.
71
- * The wallet MUST attempt to deliver all calls if it returns a successful response to this method, and the wallet
71
+ - The wallet MUST attempt to deliver all calls if it returns a successful response to this method, and the wallet
72
72
MUST NOT deliver any calls if it returns an error response.
73
- * The wallet MAY reject the request if the request chain ID does not match the currently selected chain ID.
74
- * The wallet MUST send the calls on the request chain ID.
75
- * The wallet MAY reject the request if the ` from ` address does not match the enabled account.
76
- * The wallet MAY reject the request if one or more calls in the bundle will fail.
73
+ - The wallet MAY reject the request if the request chain ID does not match the currently selected chain ID.
74
+ - The wallet MUST send the calls on the request chain ID.
75
+ - The wallet MAY reject the request if the ` from ` address does not match the enabled account.
76
+ - The wallet MAY reject the request if one or more calls in the bundle will fail.
77
77
78
78
#### Parameters
79
79
@@ -121,11 +121,11 @@ The method takes an array containing one object element, with the following keys
121
121
122
122
DATA, String - an identifier that the wallet uses to represent the bundle of calls.
123
123
124
- * This identifier MUST persist between connections of the same Dapp and account
125
- * The dapp SHOULD track the returned identifier to check the status of the bundle in the future
126
- * The returned identifier value MUST be unique for the given ` from ` address
127
- * The length of the returned identifier MUST NOT exceed 66 characters
128
- * There are no other requirements on the pattern of the identifier
124
+ - This identifier MUST persist between connections of the same Dapp and account
125
+ - The dapp SHOULD track the returned identifier to check the status of the bundle in the future
126
+ - The returned identifier value MUST be unique for the given ` from ` address
127
+ - The length of the returned identifier MUST NOT exceed 66 characters
128
+ - There are no other requirements on the pattern of the identifier
129
129
130
130
##### Example
131
131
@@ -224,8 +224,8 @@ display of the function call status to the wallet, which can most accurately ren
224
224
This RPC is intended to replace the typical user experience of a dapp linking to a block explorer for a given
225
225
transaction hash.
226
226
227
- * The wallet MAY ignore the request, for example if the wallet is busy with other user actions.
228
- * The wallet MAY direct the user to a third party block explorer for more information.
227
+ - The wallet MAY ignore the request, for example if the wallet is busy with other user actions.
228
+ - The wallet MAY direct the user to a third party block explorer for more information.
229
229
230
230
#### Parameters
231
231
0 commit comments