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/developers/relayed-transactions.md
+16-4Lines changed: 16 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,10 @@ Once all applications will completely transition to relayed v3 model, v1 and v2
30
30
31
31
## Relayed transactions version 1
32
32
33
+
:::note
34
+
Legacy version. Please use [version 3](#relayed-transactions-version-3), instead.
35
+
:::
36
+
33
37
A relayed transaction version 1 relies on having the inner transaction JSON serialized and given as an argument to the `relayedTx` protocol function.
34
38
35
39
It would look like:
@@ -165,6 +169,10 @@ gasLimit = 61040000 // just like the gas limit set in the relayed transaction
165
169
166
170
## Relayed transactions version 2
167
171
172
+
:::note
173
+
Legacy version. Please use [version 3](#relayed-transactions-version-3), instead.
174
+
:::
175
+
168
176
In contrast with version 1, relayed transactions version 2 have only certain fields of the inner transaction included
169
177
in the data field, making the payload smaller, therefore the tx fee smaller. It also eliminates the need of calculating
170
178
the matching gas limit values between the relayed and inner transactions.
@@ -249,10 +257,6 @@ Decoding the arguments ([useful resources here](/developers/sc-calls-format/)) w
249
257
250
258
## Relayed transactions version 3
251
259
252
-
:::note
253
-
This feature is not yet available on **Mainnet**. See [Spica Protocol Upgrade](https://governance.multiversx.com/proposal/erd1qqqqqqqqqqqqqpgq4qvrwlr2e6ld50f3qfc94am38p8298kthg4s3f0vfn/1).
254
-
:::
255
-
256
260
Relayed transactions v3 feature comes with a change on the entire transaction structure, adding two new optional fields:
257
261
-`relayer`, which is the relayer address that will pay the fees.
258
262
-`relayerSignature`, the signature of the relayer that proves the agreement of the relayer.
@@ -316,3 +320,11 @@ Here's an example of a relayed v3 transaction. Its intent is to call the `add` m
316
320
"relayerSignature": "..."
317
321
}
318
322
```
323
+
324
+
### Preparing relayed transactions using the SDKs
325
+
326
+
The SDKs have built-in support for relayed transactions. Please follow:
0 commit comments