Prevent flooding #232

New Issue

2022-10-29T11:26:04Z

raucao commented

2022-10-29 11:26:04 +00:00

Reasoning: A rich actor could complete a couple of minor contributions in order to gain the permission to propose kredits, and then flood the contracts with pending kredits proposals (or reimbursements, or whatever else we might add), which would cost an equal amount of RBTC to veto for every entry.

Possible solutions (not mutually exclusive):

Veto multiple entries at once (also look at #233 for this)
Limit pending entries per sender (when migrationDone is true)
... ?

Reasoning: A rich actor could complete a couple of minor contributions in order to gain the permission to propose kredits, and then flood the contracts with pending kredits proposals (or reimbursements, or whatever else we might add), which would cost an equal amount of RBTC to veto for every entry. Possible solutions (not mutually exclusive): * Veto multiple entries at once (also look at #233 for this) * Limit pending entries per sender (when `migrationDone` is `true`) * ... ?

raucao added the security idea labels 2022-10-29 11:26:04 +00:00

raucao added the scaling label 2022-10-29 11:43:08 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kredits/contracts#232