how to verify transaction faster?

[aihuawu]

I am a newcomer to smartweave.

According to the tutorial,
https://cedriking.medium.com/lets-buidl-smartweave-contracts-6353d22c4561

Since the SW contract itself is updated on the client, to get the latest state of a contract, the client needs to go through each interaction to find its latest valid state.

If I create a PST token, it may have millions of actions, I have to verify it whenever I do a transfer.
Is there any better way to do it?

Thanks.

George Wu

[AndreVallestero]

I'm aware of 3 different ways to tackle this problem:

• Submit your transactions in batches using some type of bundler middleware. This will reduce the amount of transactions that need to be processed when computing the state
• Regularly create snapshots of your state and only compute the changes since the snapshot block
• Regularly redeploy a new contract using the last computed state as the new initial state

[ppedziwiatr]

Redeploying contract is good solution, the only issue here is the constantly changing txId, that must be updated in all the client apps.
To tackle this issue, we've created a "contracts-registry" contract, that allows to get the most current contract txid by its "logical" name: https://github.com/redstone-finance/redstone-smartweave-contracts/tree/main/src/contracts-registry
https://viewblock.io/arweave/address/XQkGzXG6YknJyy-YbakEZvQKAWkW2_aPRhc3ShC8lyA?tab=state
The example API for getting current txId from the contract source code is here https://github.com/redstone-finance/redstone-smartweave-contracts/blob/main/src/common/ContractInteractions.ts#L48

It also allows to deploy contract's upgrades.

Re. caching - please consider switching to https://github.com/redstone-finance/redstone-smartcontracts - it allows to easily plugin different type of caches.