Skip to content

feat(contract_manager): more support for starknet contract #1716

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

Merged
merged 2 commits into from
Jun 21, 2024

Conversation

Riateche
Copy link
Contributor

No description provided.

Copy link

vercel bot commented Jun 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
api-reference ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 20, 2024 2:58pm
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
xc-admin-frontend ⬜️ Ignored (Inspect) Visit Preview Jun 20, 2024 2:58pm

senderPrivateKey: PrivateKey,
vaas: Buffer[]
): Promise<TxResult> {
throw new Error("Method not implemented.");
// We need the account address to send transactions.
throw new Error("Use executeUpdatePriceFeedWithAddress instead");
Copy link
Collaborator

@ali-behjati ali-behjati Jun 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't there any way to fetch the address from private key? this (and the executeGovernance) will break some generic things that we can do. (like update price feed script)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's possible to derive it but it depends on the wallet application used to create the account and on the constructor arguments. Looks like the mainstream way of handling it is just to pass the account address explicitly.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since it's our own tooling, can't we just rely on that one?
if we had time, a better option would've been refactoring this code to have better interfaces.

Copy link
Collaborator

@ali-behjati ali-behjati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm approving this but I think if we go back and revisit it later. This is a sign of bad interface design for us and not a problem in this PR specifically.

@Riateche Riateche merged commit ce1e0c0 into main Jun 21, 2024
@Riateche Riateche deleted the starknet-manager2 branch June 21, 2024 09:32
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

Successfully merging this pull request may close these issues.

2 participants