Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
What happens if we verify the source code in the explorer, but the contract's code gets updated using set_code() instruction?

What happens if we verify the source code in the explorer, but the contract's code gets updated using set_code() instruction?

Does the verified source code disappears?

This question was imported from Telegram Chat: https://t.me/tondev_eng/23002

Votes Newest

Answers


When you verify a smart contract's source code on a blockchain explorer or website, the page generates a unique code hash for the contract. This code hash is essentially a digital fingerprint of the contract's bytecode. When someone views the verified source code on the explorer, the explorer looks up the code hash and retrieves the corresponding source code.

However, if the contract's bytecode is updated using the set_code() instruction, the code hash will change. This means that the verified source code will no longer be associated with the contract, and will disappear from the explorer.

To re-verify the source code, you would need to follow the verification process again, which typically involves submitting the source code and the new code hash to the explorer.

It's also worth noting that if you have multiple contracts with identical code hash, you only need to verify one of them to have all of them become verified. This is because the code hash is the same for all of the contracts, and the explorer only needs to associate the source code with the code hash once.

3
3
wiki
Posted one year ago
16K Views
1 Answer
one year ago
one year ago
Tags