Skip to content

Rough High-assurance documentation wrt attacks #14

@holyfuchs

Description

@holyfuchs

Scrappy but complete first draft of "what can go wrong, what do we do if it goes wrong". Must cover at minimum:

  • Rounding as an attack vector / failure source — and an initial dust strategy listing where rounding errors occur and how they are managed.
  • Donation attacks.
  • Reentrancy.

Identify mitigations and ensure the current design is compatible with adding more later.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions