Induce state and storage leaf removal for testing purposes #18

New Issue

i-norden · 2023-02-20T21:17:39Z

i-norden commented

2023-02-20 21:17:39 +00:00

This and https://github.com/cerc-io/tx-spammer/issues/17 are two edge case scenarios that often cause unexpected/confusing bugs/issues.

This is easy enough to induce at both the state and storage levels:

For state (and storage), we can write a contract that can self destruct.

For storage, we should be able to do this already by calling the Put method with empty values.

This and https://github.com/cerc-io/tx-spammer/issues/17 are two edge case scenarios that often cause unexpected/confusing bugs/issues. This is easy enough to induce at both the state and storage levels: For state (and storage), we can write a contract that can self destruct. For storage, we should be able to do this already by calling the `Put` method with empty values.

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/tx-spammer#18