Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Batch calls can be used to circumvent the limits of spend tracks #13167

@paradox-tt

Description

@paradox-tt

Is there an existing issue?

  • I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

  • This is not a support question.

Description of bug

Good day,

With reference to the subjected matter, batch calls can be used to circumvent the total spend limits of a track. This is evident by the successful outcome of referendum 62.

I appreciate that security is the first priority and a simple fix would be to remove batch functionality for spend proposals. Batch calls do provide flexibility to spend proposals which I would like to see retained. Please give this some consideration as a solution is designed.

Please find further context here on how this was discovered.

Steps to reproduce

https://kusama.polkassembly.io/referenda/62

Metadata

Metadata

Assignees

No one assigned

    Labels

    J2-unconfirmedIssue might be valid, but it’s not yet known.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions