Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Uber EPIC] Improve HSCS System COntract Versioning DevEx #17343

Open
3 tasks
Nana-EC opened this issue Jan 13, 2025 · 0 comments
Open
3 tasks

[Uber EPIC] Improve HSCS System COntract Versioning DevEx #17343

Nana-EC opened this issue Jan 13, 2025 · 0 comments

Comments

@Nana-EC
Copy link
Contributor

Nana-EC commented Jan 13, 2025

Problem

System contracts assume a single address and utilize solidity logic to define their interfaces.
As such due to the limitation of overloading the emergent function hashes result in in a new function whenever there's a HAPI protobuf update for a message represented in a system contract function method param.

Additionally, hedera-smart-contracts contains reference to system contract interfaces as well as reference wrapper contracts that are not well known to all devs

Solution

Provide an improved development experience in which system contract addresses can be upgrade to a new address just as if it was a real contract. The new address will utilize the latest structs interface support.
Additionally the details of the address may be hidden by the packaging of the hedera-smart-contracts npm package.

Alternatives

No response

@Nana-EC Nana-EC changed the title [Uber EPIC] Productize hedera-smart-contracts [Uber EPIC] Improve HSCS System COntract Versioning DEX Jan 13, 2025
@Nana-EC Nana-EC moved this from Backlog to Epics In Progress in Smart Contract Sprint Board Jan 13, 2025
@Nana-EC Nana-EC changed the title [Uber EPIC] Improve HSCS System COntract Versioning DEX [Uber EPIC] Improve HSCS System COntract Versioning DevEx Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Epics In Progress
Development

No branches or pull requests

1 participant