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

Bump lanes config #5060

Merged
merged 1 commit into from
Jan 17, 2025

Conversation

mpapierski
Copy link
Collaborator

@mpapierski mpapierski commented Jan 15, 2025

This PR bumps lane config based on mainnet data activity
Impact:

  • Install/upgrade lane and lane no.3 (aka biggest wasm lane) from 100CSPR to 1000CSPR -> this should cover 98% of all Wasm interactions (session & stored).
  • Lane 4 already covers 58% of session code and 0.5% of smart contract interactions
  • Lane (no.5) is bumped from 3CSPR to 5CSPR -> will now cover about 40% of all session codes (up from 30%) and 99.5% of smart contracts (up from 99.1%)

Busy wasms were validated with new settings.

Wasm saturated block will consume about 1600CSPR of gas (increased from 500CSPR), leaving 25CSPR worth of computation for native contract calls (e.g., transfers, and auction contracts). Current mainnet usage data suggests 70% of chain interactions are session/smart contracts and 30% are native transfers.

@mpapierski
Copy link
Collaborator Author

bors r+

Copy link
Contributor

Build succeeded:

@casperlabs-bors-ng casperlabs-bors-ng bot merged commit 2785b71 into casper-network:dev Jan 17, 2025
4 checks passed
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.

5 participants