Conversation
✅ Deploy Preview for teloscan-stage ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for dev-mainnet-teloscan ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for testnet-teloscan ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for zkevm-testnet ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
pmjanus
approved these changes
Mar 18, 2025
pmjanus
deleted the
995-wrappet-telos-contract-is-not-showing-all-write-functions-deposit-is-missing
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #995
Description
In the specific case of WTLOS on testnet we have a particular situation. The contract's ABI is stored in the indexer with fewer functions than the sourcefy registers. Therefore, for verified contracts, we are taking the abi directly from our copy of the sourcefy database and extracting the abi from the metadata file source.json.
Test scenarios
Currently in production:
https://testnet.teloscan.io/address/0xaE85Bf723A9e74d6c663dd226996AC1b8d075AA9?tab=contract&subtab=write
Using the this PR's deployment:
https://deploy-preview-998--testnet-teloscan.netlify.app/address/0xaE85Bf723A9e74d6c663dd226996AC1b8d075AA9?tab=contract&subtab=write