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

Increase RPC limit of contract deployment size #3231

Closed
MaksymZavershynskyi opened this issue Aug 21, 2020 · 1 comment · Fixed by #3237
Closed

Increase RPC limit of contract deployment size #3231

MaksymZavershynskyi opened this issue Aug 21, 2020 · 1 comment · Fixed by #3237
Assignees
Labels
A-RPC Area: rpc P-low Priority: low

Comments

@MaksymZavershynskyi
Copy link
Contributor

Currently RPC prevents contract deployments of the size that it allowed by the runtime. We should increase this limit and make it configurable without code recompilation.

@frol
Copy link
Collaborator

frol commented Aug 24, 2020

@nearmax @evgenykuzyakov what is the runtime limit of contract size? The current RPC limit is 2MB of JSON data where contract is base64-encoded (which is 33% overhead), so given the metadata size in the payload and base64 encoding overhead, I estimate the current max contract size is ~1MB.

nearprotocol-bulldozer bot pushed a commit that referenced this issue Aug 25, 2020
*Resolves #3231.*

The limit has been changed from 2MB to 10MB, and it is now configurable via `config.json`. This limit affects the size of the transaction, and it was hit when users deploy big contracts; with this change, we should enable deployment of contracts of up to ~6.5MB.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-RPC Area: rpc P-low Priority: low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants