[MultiversX]: Add support for relayed (V3) transactions #4243
+255
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR brings some support for crafting relayed transactions. The so-called relayed transactions are transactions where the fee is paid by a relayer account (instead of being paid by the sender).
Applications that use wallet-core to create & sign transactions can benefit from these changes to support the use case of relayed transactions (e.g. this use case will be supported in xPortal).
Transaction
object has been extended to include a new field, calledrelayer
.Serialization
logic has been adjusted to include the the newrelayer
field.Additional references:
How to test
Running the unit tests, and performing a smoke test (e.g. sending a regular transaction) upon integrating the updated wallet-core in the mobile application. The mobile application does not need to populate the newly added field.
Types of changes
Theoretically - non-breaking. Public methods not altered.
Checklist
If you're adding a new blockchain