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

Extend the Gateway contract to store protocol contract addresses #227

Open
fadeev opened this issue Jul 15, 2024 · 3 comments
Open

Extend the Gateway contract to store protocol contract addresses #227

fadeev opened this issue Jul 15, 2024 · 3 comments

Comments

@fadeev
Copy link
Member

fadeev commented Jul 15, 2024

If we decide that the Gateway contract should stay minimal, then I propose we rename the current Gateway to GatewayInternal or something, and make the actual Gateway in front of it.

If we position the Gateway contract as the single entry point to ZetaChain, we need to make sure it can additional seemingly non-core functionality like storing contract addresses and reporting gas.

@lumtis
Copy link
Member

lumtis commented Jul 17, 2024

Can you provide the extended interface you would consider for the gateway on top of withdraw/deposit/call methods?
I would personally avoid having several gateway contract types.

@fadeev
Copy link
Member Author

fadeev commented Jul 26, 2024

@lumtis

_type would be zetaToken, tssUpdater or any other contract address:

function getAddress(string memory _type) external view returns (address);

This function is for when _type is zrc20, which also requires a symbol like "BTC":

function getAddress(string memory _type, string memory _symbol) external view returns (address);

@fadeev
Copy link
Member Author

fadeev commented Jul 26, 2024

Maybe this can be implemented as a precompiled contract instead: #259

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants