VNP-20 - Change `transfer.minTransferQuantumMultiple` to `10`

🗳️ Governance Proposals Network Parameter Proposals
1

VNP-20 - Change transfer.minTransferQuantumMultiple to 10
Change parameter transfer.minTransferQuantumMultiple to 10

At launch all the parameters relating to spam protection were set at very conservative level and the ongoing suggestion is to relax them as we see more about how the Vega software behaves in mainnet.

This allows smaller internal transfers which helps with various user scenarios.

Summary:
Parameter transfer.minTransferQuantumMultiple
Change in value from 100 to 10
Rationale

Full Proposal JSON:

{
    "rationale": {
      "title": "VNP-020 Change `transfer.minTransferQuantumMultiple` to `10`",
      "description": "Change `transfer.minTransferQuantumMultiple` from `100` to `10` as set out in [VNP-020], discussed in the [Vega Community Forum](https://community.vega.xyz/t/vnp-20-change-transfer-mintransferquantummultiple-to-10/4393)"
    },
    "terms": {
      "updateNetworkParameter": {
        "changes": {
          "key": "transfer.minTransferQuantumMultiple",
          "value": "10"
        }
      },
      "closingTimestamp": 1701684000,
      "enactmentTimestamp": 1701684000
    }
  }
3 Likes
2

Sounds good. Will vote in support.

3

It’s now on-chain for voting: https://governance.vega.xyz/proposals/042bd60d0110d3bb27aa0aa472bf0acc6ac0f3467bc59f2530d7d1c4349d3771 .

4

Note that while this is true, if this proposal passes the system will probably be at the limit for transfers until a more sophisticated underlying DOS protection mechanism is in place, and the minimum transfer size shouldn’t be reduced below this level until then.