Implement get_config_param
and Fix issue with masterchain addresses
#14
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.
This PR introduces the following modifications to the library:
get_config_param
function, enabling the retrieval of config cells and the reading of data from them.This code should ideally run without errors for both addresses. However, it fails for the second one, with unexpected changes in constructor and anycast flag values, as seen in the log:
A deeper look at the code reveals that the problem possibly arises from how
wc
is masked with0xff
but then stored as ani8
, potentially causing issues due to sign bits. Adjusting the code to usestore_u8
instead seems to fix the issue: