Connector Aware Estimation

[danielbate]

TLDR

Connector Aware Estimation is the process of giving the SDK more awareness of the account level semantics earlier in the transaction flow to reduce round trips to the network.

Problem

Let's imagine the following transaction flow for non-native wallets:

In the first stage, the SDK estimates the transaction as normal.

Once it hands off to the connector, and we introduce the non-native account, we must add the predicate to the transaction. Therefore meaning the transaction must be re-prepared.

This is obvious redundancy that could be mitigated by giving the SDK the context earlier in the flow:

Potential Solution

1. Introduce a prepareTransaction function to the connector interface, that can alter a transaction request with any of it's own specifics, such as adding the non-native predicate.

  /**
   * Modifies a transaction request with anything connector specific.
   * 
   * @param transaction - The tx to prepare.
   *
   * @returns The prepared tx request
   */
  async prepareTransaction(transaction: TransactionRequestLike): Promise<TransactionRequest>;

2. Introduce connector.prepareTransaction() at the estimation and funding SDK entry points.
3. Remove connector level estimation and funding from within the connector.sendTransaction() calls.

Notes

• Must be additive, allowing for gradual upgrade by the connectors
• Must work with conjunction with prepareForSend - Inverted Submission Flow #3665

[danielbate]

I have not done a proof of concept here yet, so this may evolve.

[danielbate]

@petertonysmith94 I think I was overdoing it in our previous discussion, something simple like this would work by moving the connector level logic from submission -> preparation.

But have a look and see what you think, I will pick up any progress made next week :)

[danielbate]

Blocked until #3669 and #3737 are complete.

[danielbate]

We will now be working on this in tandem with #3669.

[danielbate]

Okay, I'm now blocked on this until 0.42.0 is available on testnet.

The WIP PR is looking pretty solid and includes e2e tests using an associated predicate account that requires an external signer (very similar to the EVM/SVM predicates).

I'm having trouble testing solana locally with the connectors repo (phantom doesn't support localnet + the predicate bytecode I'm deploying locally doesn't seem to be matching up). My preference is to wait for [email protected] (so we have assembleTx) to be deployed to testnet where I know I have a working associated account, and I'll have greater confidence testing the feature there.

I've asked the fuel-core guys to expedite deploying it to testnet, I expect it'll be delivered within the day.

[arboleya]

Testnet only? Devnet is already there.

[danielbate]

When I wrote that message both of them were on 0.41.9, I'll try devnet. Phantom does only support eth sepolia testnet but I should still be able to sign, somethings might not just appear as expected.