What problem does your feature solve?
The Wallet Backend currently indexes state changes for transactions included in closed ledgers, but many wallets including Freighter want to know the state changes for transactions prior to signing them.
What would you like to see?
A GraphQL query that accepts a transaction, simulates it using RPC's simulationTransaction method, and then uses the data provided in the response in addition to the transaction itself to derive and return the state changes that would have been indexed by the wallet backend if the transaction had been submitted to the network and included in a ledger.
What alternatives are there?
N/A.
What problem does your feature solve?
The Wallet Backend currently indexes state changes for transactions included in closed ledgers, but many wallets including Freighter want to know the state changes for transactions prior to signing them.
What would you like to see?
A GraphQL query that accepts a transaction, simulates it using RPC's simulationTransaction method, and then uses the data provided in the response in addition to the transaction itself to derive and return the state changes that would have been indexed by the wallet backend if the transaction had been submitted to the network and included in a ledger.
What alternatives are there?
N/A.