Skip to content

Commit 04b3830

Browse files
authored
Merge pull request #2709 from marcello33/mardizzone/remove-gh-links
remove invalid gh links
2 parents 69999f8 + d365f3a commit 04b3830

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

docs/pos/concepts/transactions/meta-transactions.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -91,8 +91,6 @@ For any action that requires blockchain interaction,
9191
2. Copy the API key to use for you dApp's frontend.
9292
3. And add function `executeMetaTransaction` in **Manage-Api** and make sure to enable meta-tx (Check **native-metatx** option).
9393

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-
9694
- Make sure that the contract you'd like to interact with inherits from `NativeMetaTransactions` - 👀 peep into `executeMetaTransaction` function in the contract.
9795
- Link: [https://github.com/maticnetwork/pos-portal/blob/34be03cfd227c25b49c5791ffba6a4ffc9b76036/flat/ChildERC20.sol#L1338](https://github.com/maticnetwork/pos-portal/blob/34be03cfd227c25b49c5791ffba6a4ffc9b76036/flat/ChildERC20.sol#L1338)
9896

@@ -133,8 +131,6 @@ let data = await web3.eth.abi.encodeFunctionCall({
133131

134132
- 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
135133

136-
ref: [https://github.com/angelagilhotra/ETHOnline-Workshop/blob/6b615b8a4ef00553c17729c721572529303c8e1b/2-network-agnostic-transfer/sign.js#L47](https://github.com/angelagilhotra/ETHOnline-Workshop/blob/6b615b8a4ef00553c17729c721572529303c8e1b/2-network-agnostic-transfer/sign.js#L47)
137-
138134
```jsx
139135

140136
let data = await web3.eth.abi.encodeFunctionCall({
@@ -168,7 +164,7 @@ let data = await web3.eth.abi.encodeFunctionCall({
168164
});
169165
```
170166

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
172168

173169
```jsx
174170
const response = await request.post(
@@ -223,8 +219,6 @@ where the `txObj` should look something like:
223219

224220
- If you use the custom API, it executes the `executeMetaTransaction` function on the contract:
225221

226-
(ref: [https://github.com/angelagilhotra/ETHOnline-Workshop/blob/6b615b8a4ef00553c17729c721572529303c8e1b/2-network-agnostic-transfer/server/index.js#L40](https://github.com/angelagilhotra/ETHOnline-Workshop/blob/6b615b8a4ef00553c17729c721572529303c8e1b/2-network-agnostic-transfer/server/index.js#L40))
227-
228222
```jsx
229223
try {
230224
let tx = await contract.methods.executeMetaTransaction(

0 commit comments

Comments
 (0)