TransactionInput - A Transaction Bundling Input

[SilentCicero]

Abstract

This input allows you to specify a transaction ID as an input. This would be used for transaction bundling.
 The input is successfully spent when the transaction specified by the txID exists, is in the same block and has not reverted.

InputTransaction

name	type	description
txID	byte[32]	Hash of transaction.

Restrictions

• The transaction ID must be a valid ID which specifies a transaction in the current block

Cons

• This does not allow for the kind of bundling where transactions must all pass or fail, that should be covered in a bundle identifier of some kind.

Prior Art

Signed Bundles: https://github.com/FuelLabs/rfcs/pull/16/files

Note, this is merely a first pass at the idea, we will likely want to specify a bundle ID of some kind which would be used in our transactional design.

[SwayStar123]

If the transaction ID specified does not revert, the current transaction will not revert, otherwise the current transaction reverts.

Wording makes it sound like the given tx will never revert given the prev tx didn't revert. Is this intentional?

[SilentCicero]

@SwayStar123 fixed wording here.

[SwayStar123]

Will there be any guarentees about ordering of transactions? Ie, input tx is before the current tx, and or, input tx will be the very last tx before the current tx @SilentCicero