VNP028 - Increase number of entries allowed in a batch transaction

VNP028 - Increase number of entries allowed in a batch transaction
Change parameter spam.protection.max.batchSize from 30 to 51.

Rationale

Having observer alpha mainnet performance for an extended period of time it seems that the network will cope with more orders per batch. Hence the recommendation to increase spam.protection.max.batchSize from 30 to 51.

The odd number is to include a possible cancelation and then this leaves an even number so same number of orders / amends on each side of the book.

If any validators are reading this and have performance concerns it would be good to hear those, in case other people have different data.

Full Proposal JSON:

{
    "rationale": {
      "title": "VNP-029 set `spam.protection.max.batchSize` to `51`",
      "description": "Change parameter `spam.protection.max.batchSize` from `30` to `51`."
    },
    "terms": {
      "updateNetworkParameter": {
        "changes": {
          "key": "spam.protection.max.batchSize",
          "value": "51"
        }
      },
      "closingTimestamp": TBD on submission but as soon as voting rules allow,
      "enactmentTimestamp": TBD on submission but as soon as voting rules allow
    }
  }
2 Likes