You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we just accumulate all the contract data bumps in a vec and apply them one-by-one in Core. This may cause fees to be double-charged and bumps to be overridden. Instead, we should deduplicate bumps by key and only keep the max value.
This could be done either in the host or in core. Host is preferable as it ensures consistent behavior between core and preflight.
The text was updated successfully, but these errors were encountered:
There are some inconsistencies with how bump duration is computed in core and in host; I'll experiment with moving this logic completely to the host side to avoid such inconsistencies.
Currently we just accumulate all the contract data bumps in a vec and apply them one-by-one in Core. This may cause fees to be double-charged and bumps to be overridden. Instead, we should deduplicate bumps by key and only keep the max value.
This could be done either in the host or in core. Host is preferable as it ensures consistent behavior between core and preflight.
The text was updated successfully, but these errors were encountered: