Skip to content

Conversation

@pselle
Copy link
Member

@pselle pselle commented Sep 24, 2025

What

The argument to upgrade should be new_wasm_hash, not wasm_hash, as this is what we're standardizing on per https://developers.stellar.org/docs/build/guides/conventions/upgrading-contracts.

Why

Scaffold Stellar assumes new_wasm_hash when upgrading contracts, so this function should use that argument.

Copy link
Member

@chadoh chadoh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the right thing to do to me! @willemneal any comments here?

@willemneal willemneal merged commit 4f1e3f9 into main Sep 24, 2025
8 checks passed
@willemneal
Copy link
Member

An the low level contract invoke the name doesn't matter, since the args are just a vec. So we should update Scaffold stellar to just pass a the bytesN<32>. But completely agree we should use the same name in the official trait!!

@pselle pselle deleted the fix/new_wasm_hash branch September 24, 2025 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants