This repository was archived by the owner on Jan 12, 2023. It is now read-only.
Smart contract deployment support #19
Open
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.
These changes bring smart contract deployment pyntelope/eospyo. To achieve this, the setcode (setting wasm file) and setabi actions had to be supported, so serialization of abi and wasm files was implemented. Serializing wasm files is simple as they just have to be loaded, converted to hex then converted to bytes, but abi file serialization is more complex and requires each component/field of the abi file to be serialized differently, so new classes for these components were created.
Full list of changes:
There are a few things that need to be added in the future: