Replies: 2 comments
-
What could help you is pinned contract. A contract you pin is always compiled and kept in an in-memory storage for quick instantiation. I just wonder if it is better to read this static data from a contract or from a database (i.e. blockchain state). You probably want to benchmark this. The max Wasm size can be configured with a variable in wasmd. I don't have much practical experience but a 3MB contract does not sound too scary to me in a permissioned setup. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks @webmaster128 - I'll evaluate and update my findings here. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm currently working on a custom application using cosmos-sdk/cosmwasm and would like to know if there is a way to pre-compile certain contracts? And are there any size restrictions to the precompiled contracts?
Here is a usecase:
I want to compile a contract with a set of static lookup data (~100 million 32 byte records). We do not need this many for the start and can also be ok with 100k to begin with. And this needs to be deployed in the custom cosmos-sdk based application.
And this contract will then be used to lookup certain information in other cosmwasm contracts.
An alternative to this would be to have the static data exposed through a custom cosmos-sdk module and have the contract call the custom module to get the data. I'm not sure which one is feasible and gas efficient.
Beta Was this translation helpful? Give feedback.
All reactions