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

chore: use owner account in engine authorizer #736

Merged
merged 1 commit into from
Apr 3, 2023

Conversation

aleksuss
Copy link
Member

Description

The PR allows using an owner account in the EngineAuthorizer rather than a hardcoded aurora account.

Performance / NEAR gas cost considerations

There should be no changes in the performance.

Copy link
Member

@birchmd birchmd left a comment

Choose a reason for hiding this comment

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

LGTM

@vimpunk
Copy link
Contributor

vimpunk commented Mar 31, 2023

There is no performance impact despite reading from storage because this is a read only method, correct?

@aleksuss
Copy link
Member Author

aleksuss commented Mar 31, 2023

I guess you mean increasing gas costs? I think it increases gas costs a bit, even if this is a read-only operation because read-only ops are not free. But we don't have to worry about that because it's a rare operation (pause_precompiles). What we do care about are submit and call and their inner functions, which work with storage.

@aleksuss aleksuss added this pull request to the merge queue Apr 3, 2023
Merged via the queue into develop with commit 9e672bc Apr 3, 2023
@aleksuss aleksuss deleted the chore/aleksuss/engine_authorizer branch April 3, 2023 09:13
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.

4 participants