Support account's execute about starknet-react

[fracek]

I like invokeMany but we would be diverging from the standard name for the function which (I believe) is confusing.

[tarrencev]

I like the proposed interface for execute. I'm wondering if we should deprecate invoke api in favor of a single execute api. It seems that is the direction the AccountInterface has taken:

public abstract execute(
    transactions: Call | Call[],
    abis?: Abi[],
    transactionsDetail?: InvocationsDetails
  ): Promise<AddTransactionResponse>;

[ponderingdemocritus]

Pulled from StarkNet fees - This is a huge potential saving if we batch transactions.

[fracek]

Since execute does not require changing any existing interface it can be added after v1.0.

What's your opininion on this interface @tarrencev @Pet3ris?

[Pet3ris]

Would be great to have this function, I'm already using multicall right now for Yagi.

Regarding naming, I wonder if having more aligned naming between the invoke and this would make sense, e.g., execute1 and execute or invoke1 and invoke or invoke and invokeMany.

[fracek]

Looks like the execute method only accepts RawCalldata, I wonder if there's a reason for that? If it's possible I would update that method to accept normal call data. We also need to figure out how to add typesafety to the hook, my impression is that it's enough to add a unknown[] type parameter, where each unknown is the type of the input of each call.

/cc @janek26

[janek26]

no particular reason, feel free to change that

would be nice to use RawCalldata as little as possible - it will always be needed for API responses

[ponderingdemocritus]

It would be a nice feature if the calls were view exposed so within a UI you could easily show a 'tx cart' style element. Think like a ecomm cart.

For games specifically, it might make sense to seriously batch transactions together, as if they are updating similar state values (erc20 transfer eg) in 10 transactions, then it is effectively 1 storage update. Extend this to an 1155 style and the savings stack up massively for the player.

[fracek]

It would be a nice feature if the calls were view exposed so within a UI you could easily show a 'tx cart' style element. Think like a ecomm cart.

For games specifically, it might make sense to seriously batch transactions together, as if they are updating similar state values (erc20 transfer eg) in 10 transactions, then it is effectively 1 storage update. Extend this to an 1155 style and the savings stack up massively for the player.

I agree this looks cool. To make it happen we need to figure out a good API for execute, then we can think about that type of component built on top.

[fracek]

Fixed in 9fb19b2