BlaineHeffron
commented
4 months ago A couple of interesting things I found:
- At first I wanted to reuse the Account object so we don't query the server a second time for it. The problem I found was that the sequence number increments the first time the AssembledTransaction is built, and since that method call doesn't go through it is then off by 1 for the restoreFootprint operation. If I had a way to decrement the sequence number I could avoid this problem and reuse the Account object.
- I was having trouble testing the case where the actual contract wasm hash footprint / contract wasm was expired. The way I was testing was by setting the minimum expire ledgers to some low number (around 300) in the quickstart config. Since persistent and instance storage use this same number, it would seem that the persistent storage and instance storage (which would presumably include the wasm hash) would expire at the same time. It seemed that regardless of what had expired, using the
restorePreambleto construct therestoreFootprintoperation always worked. In other words, I never needed to perform the actual restore of the contract wasm hash / contract wasm footprints. I did write code to do that in case its needed, and I can add that as a method if it is needed. I just wasn't able to find a test case where it was.
Shaptic
chadoh
Adds the ability to set
restoreto true in contract method invocation options. This will utilize the signTransaction method to sign a restoreFootprint operation when found that it is needed during a simulation.