Release: Spica Patch 2 - v1.8.9

Relayed Transactions V3 Overview

The Relayed Transactions V3 introduces a change to the transaction structure similar to what guardians did with Altair Release, adding two new optional fields:

• relayer: The address of the relayer responsible for paying the fees.
• relayerSignature: A signature from the relayer, proving their agreement to process the transaction.

With these changes, relayed transactions V3 will look and behave very similarly to a regular transaction, with one key difference: gas consumption is handled by the relayer. Additionally, specifying the user transaction in the data field is no longer required.

Gas Limit Computation
An extra base cost of 50_000 will now be consumed for relayed transactions. For example, consider a relayed transaction with an inner transaction of type move balance, which includes a data field test of length 4. A normal move balance would have cost56_000

and making it relayed transaction would end up costing 106_000.

```

RelayedV3Transaction {
   Sender: <Sender address>
   Receiver: <Receiver address>
   Value: <value>
   GasLimit: <base_cost> + <base_cost> + <cost_per_byte> * length(txData)
   Relayer: <Relayer address>
   RelayerSignature: <Relayer signature>
   Signature: <Sender signature>
}

```

Setting a relayed transaction is quite simple, one has to follow the next steps:

• set the relayer field to the address that would pay the gas
• add the extra base cost for the relayed operation
• add sender's signature
• add relayer's signature

DONE!

We are incredibly grateful to everyone who tested the feature on Testnet and Devnet! To make relayed transactions easy to identify, we've added a special symbol. Have a look at it here—how cool is this?
‍View Transaction Example

Governance Vote

The Spica v1.8 Release has successfully passed its governance vote. The vote, which ran from August 8th to August 18th, resulted in a decisive 98.65% voting in favor of the upgrade, with 1.10% against and 0.25% abstaining. The entire discourse surrounding the release took place off-chain on Agora, and can be reviewed here.

Documentation

https://docs.multiversx.com/developers/relayed-transactions/#relayed-transactions-version-3

Activation epoch

Spica Patch 2 Release is scheduled to be activated starting with epoch 1650, anticipated on February 4th, 2025, around 15:30 UTC.

‍

Github Full binary release notes: https://github.com/multiversx/mx-chain-go/releases/tag/v1.8.9

Mainnet Config: https://github.com/multiversx/mx-chain-mainnet-config/releases/tag/v1.8.9.0

‍

‍

‍