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: docs/pos/concepts/transactions/meta-transactions.md
+1-7Lines changed: 1 addition & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,8 +91,6 @@ For any action that requires blockchain interaction,
91
91
2. Copy the API key to use for you dApp's frontend.
92
92
3. And add function `executeMetaTransaction` in **Manage-Api** and make sure to enable meta-tx (Check **native-metatx** option).
93
93
94
-
- If you'd like to use your own custom API that sends signed transactions on the blockchain, you can refer to the server code here: [https://github.com/angelagilhotra/ETHOnline-Workshop/tree/master/2-network-agnostic-transfer](https://github.com/angelagilhotra/ETHOnline-Workshop/tree/master/2-network-agnostic-transfer)
95
-
96
94
- Make sure that the contract you'd like to interact with inherits from `NativeMetaTransactions` - 👀 peep into `executeMetaTransaction` function in the contract.
@@ -133,8 +131,6 @@ let data = await web3.eth.abi.encodeFunctionCall({
133
131
134
132
- Once you have a relayer and the contracts set up, what is required is for the client to be able to fetch an EIP-712 formatted signature and simply call the API with the required parameters
@@ -168,7 +164,7 @@ let data = await web3.eth.abi.encodeFunctionCall({
168
164
});
169
165
```
170
166
171
-
Calling the API, ref: [https://github.com/angelagilhotra/ETHOnline-Workshop/blob/6b615b8a4ef00553c17729c721572529303c8e1b/2-network-agnostic-transfer/sign.js#L110](https://github.com/angelagilhotra/ETHOnline-Workshop/blob/6b615b8a4ef00553c17729c721572529303c8e1b/2-network-agnostic-transfer/sign.js#L110)
167
+
Calling the API
172
168
173
169
```jsx
174
170
constresponse=awaitrequest.post(
@@ -223,8 +219,6 @@ where the `txObj` should look something like:
223
219
224
220
- If you use the custom API, it executes the `executeMetaTransaction` function on the contract:
0 commit comments