…n the user's signed transaction

…n transfer

…octo_near field

…uring the transaction. Rational: this allows relayers to pay for the gas on a user's behalf (by initiating the transaction from their own account) without also needing to pay for other base token transfers involved in the transaction (eg minting wrapped NEAR).

…Near does not guarantee execution order of receipts, so user actions may still be executed out of order even if transactions with sequential nonces arrive in the correct order; the only way to guarantee sequential order of execution is to prevent simultanious in-flight transactions.

…s. Rational: this prevents faulty relayers from griefing users by intentionally submitting transactions incorrectly to prevent their execution. If the nonce is not incremented then an honest relayer can still send the user's original transaction.

…r hash collision

…ract call fails. This prevents the user from taking funds from a relayer by intentionally making failed calls. This does not protect the relayer from its own mistakes (e.g. incorrect nonce or invalid transaction); the relayer must still be confident the cross-contract call will execute when choosing to attach NEAR.

…ansfers

…eeded because testnet has stateless validation, but mainnet does not and doing the stateless upgrade plus another protocol change does not work in the pytests.

…his is needed because testnet has stateless validation, but mainnet does not and doing the stateless upgrade plus another protocol change does not work in the pytests."

This reverts commit ba06adc.