Skip to content

Contract deployment price coefficient and minimum value #2001

@roman-khimov

Description

@roman-khimov

Summary or problem description
A lot of effort went into reducing system fees on Neo 3, one of which is contract creation and upgrade fee. There were various discussions around that topic, but the last actual change to that was made by #771 and even that originally intended to have a bit different approach (100/10 values). So at the moment we charge for storage size of contract's code and manifest, which is fair, there should be that proportion, but at the same time I think we have two problems with it:

  • contracts is not just about storage, their effect is much broader and maintaining them on-chain is a bit harder than just storing some bytes
  • it's not hard to deploy thousands of contracts with minimal GAS cost to doing so, one/two bytes contracts that do nothing are considered to be perfectly valid for the chain

At the same time having a limited set of contracts can be beneficial for the network as it allows for some additional optimizations.

Do you have any solution you want to propose?
Although contract deployment shouldn't cost a fortune, there should be some reasonable barrier to doing so, therefore I want to propose two changes:

  • apply a coefficient to current pricing (like 3), so that the price would be a little higher than now
  • more importantly, add some minimum policy value for these fees (30-50-100, I don't have any particular number of choice here) to prevent deploying useless contracts at scale

Neo Version

  • Neo 3

Where in the software does this update applies to?

  • Network Policy
  • Other: Economic model

Metadata

Metadata

Assignees

No one assigned

    Labels

    DiscussionInitial issue state - proposed but not yet accepted

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions