Support prepareForSend Transaction Flow

[danielbate]

Within the TS SDK, we are introducing an inverted transaction flow. Currently, the dApp hands off a transaction request to the connector, the connector submits it and passes back the transaction ID. If the dApp remains responsible for submission, we reduce the number of round trips from submission to summary by 2 requests.

The following SDK PR:

• TS SDK(#3689) - feat: inverted submission flow

Introduces the following properties to the FuelConnector interface:

• usePrepareForSend - a boolean flag to signal to Account.sendTransaction that of the submission flow
• prepareForSend - the implementation to prepare a transaction for submission via the connector (eg. for EVM/SVM this would be the addition of the predicate account)

Note

This is not a breaking change, the original flow is still supported but we should gradually move to this approach due to it's performance benefits.

As proof of concept, I implemented prepareForSend in the EVM/SVM/burner wallet connectors:

• feat: add prepareForSend for EVM and SVM connector #477

For the completion of this issue:

• Finalise the EVM/SVM/Burner PR
• Introduce this flow to the native Fuel Wallet (this will need changes in the Fuel Wallet)
• Notify external teams of the connector changes (Bako, Arcana etc)

[Uyoxy]

I'd be happy to do this."Hi, I'm a TypeScript and Web3 developer with experience in NestJS and blockchain integrations. I understand the inverted transaction flow and its benefits, and I’d love to contribute. My approach includes implementing prepareForSend in the Fuel Wallet and optimizing submission efficiency.. Looking forward to collaborating!"