New version of sway std results in ABI changes

General
1

I rebuilt the project after some time (probably my testnet toolchain has changed a bit) and it resulted in a slightly different ABI.

  1. Is that ok? Not sure if a different abi will work for already deployed contracts
  2. Is it possible to set a specific sway-std version for the project to avoid ABI changes?

Here’s the commit with the changes ABI: link. You can see that std library version was updated in Forc.lock. My guess is that this update resulted in the ABI change

1 Like
2

Sorry, false alarm. It seems that the offset has changed due to changes in the contract. I just didn’t expect them to impact the ABI (just inner function logic)

1 Like