Param Change compile_cost for ShadeX

Hello Secret Community,

With the upcoming launch of ShadeX – Shade Protocol’s Money Market, we are requesting a network parameter adjustment to facilitate deploying our contracts to mainnet.

Proposed Parameter Change

  • Current: compile_cost = 0.8
  • Proposed: compile_cost = 0.4

This adjustment will allow us to deploy contracts on-chain with the existing block gas constraints. A similar proposal was successfully implemented on testnet without any notable issues:

:link: Testnet Reference: Proposal #46

Proposal Details

{
  "messages": [
    {
      "@type": "/secret.compute.v1beta1.MsgUpdateParams",
      "authority": "TBD",
      "params": {
        "compile_cost": "0.400000000000000000",
        "max_contract_size": "2097152"
      }
    }
  ],
  "metadata": "ipfs://CID",
  "deposit": "1000000susrc",
  "title": "Update Compile Cost Parameter For ShadeX Launch",
  "summary": "Lower compile cost to facilitate contract deployment.",
  "expedited": false
}

We appreciate the community’s support and look forward to advancing ShadeX on Secret Network.

Best,
Mo
Shade Protocol

4 Likes

Looking forward to the launch!

In the past we discussed temporarily adjusting params to launch bigger contracts, is this proposal also intended to be a temporary change?

1 Like

Hey pmuecke,

This is intended to be permanent change so that we can perform contract migration if needed in both emergency or regular cases moving forward.

This could be changed in the future when we can have higher gas cost allowed per block.

Ah that does make sense. Would be great to also hear from SLabs what their take is before voting starts.

Yea this definitely is preferable to increasing gas at this moment. When node requirements change everything needs to be recalibrated again anyway.

I support this proposal.

This functionality was developed in 1.15 specifically to make sure that large contracts can be deployed even with lower gas limit.

And, in order to prevent the risk of spamming the network, there is an additional safeguard - the maximum deployable contract size is set to 2MB (it’s also a parameter and can be updated if needed).

So, I don’t see any issue in keeping this at 0.4 indefinitely.

I am actually happy that this new gov parameter is now put to use, and helps us keep deploying contracts while keeping the max_gas at 5M

3 Likes