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.

Sign up for GitHub

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

Jump to bottom

Adjust the fees for new hardware requirements #3329

Closed
MaksymZavershynskyi opened this issue Sep 18, 2020 · 3 comments
Closed

Adjust the fees for new hardware requirements #3329

MaksymZavershynskyi opened this issue Sep 18, 2020 · 3 comments
Assignees
@olonho
Labels
A-contract-runtime Area: contract compilation and execution, virtual machines, etc T-contract-runtime Team: issues relevant to the contract runtime team

Comments

@MaksymZavershynskyi
Copy link
Contributor

We have bumped hardware requirements for our validators: https://docs.near.org/docs/roles/validator/hardware#machine-specifications

This does not change how many CPU instructions each runtime operation takes, however it might change how many CPU instructions fit into 1 second of computation. As the result all fees need to be rescaled proportionally.

Assigning to @olonho to triage and reassign to someone in Contract Runtime team.
@MaksymZavershynskyi MaksymZavershynskyi added the A-transaction-runtime Area: transaction runtime (transaction and receipts processing, state transition, etc) label Sep 18, 2020
@stale
Copy link

stale bot commented Jul 1, 2021

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Jul 1, 2021
@bowenwang1996
Copy link
Collaborator

@olonho what is the status of this issue?

@stale stale bot removed the S-stale label Jul 1, 2021
@bowenwang1996 bowenwang1996 added A-contract-runtime Area: contract compilation and execution, virtual machines, etc T-contract-runtime Team: issues relevant to the contract runtime team and removed A-transaction-runtime Area: transaction runtime (transaction and receipts processing, state transition, etc) labels Jul 1, 2021
@bowenwang1996 bowenwang1996 mentioned this issue Jul 23, 2021
Closed
@bowenwang1996
Copy link
Collaborator

Superseded by #4461 and #4561

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olonho olonho

Labels
A-contract-runtime Area: contract compilation and execution, virtual machines, etc T-contract-runtime Team: issues relevant to the contract runtime team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@olonho @bowenwang1996 @MaksymZavershynskyi