Skip to content

chore: operator fee FMA remaining action items #210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2025
Merged

chore: operator fee FMA remaining action items #210

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions security/fma-operator-fee.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,8 +115,17 @@ Below are references for this project:
So, about 3,7 GB for 1 year.

- **Recovery Path(s):**
The decision has been made to not store operator fee parameters in the
receipts if their values hasn't been set. So updated database growth rate is the following:

```
(12 bytes / 2 seconds) x 365 days × 24 hours × 60 minutes × 60 seconds = 189,216,000 bytes in 1 year.
```

So, about 180 GB for 1 year. Therefore, we don't think the following recovery paths are necessary anymore:

- Use archive nodes to maintain historical data.
- Consider implementing receipt compression retroactively if needed.
- Consider implementing receipt compression retroactively.

### FM5: EVM incorrectly charges operator fee

Expand Down Expand Up @@ -192,7 +201,7 @@ Below is what needs to be done before launch to reduce the chances of the above
**Initial review**

- [ ] (NON-BLOCKING): Coordinate with wallet providers to update their fee estimation logic (assignee: TBD).
- [ ] (NON-BLOCKING): Implement automated monitoring on database growth rate (assignee: TBD).
- [x] (NON-BLOCKING): Implement automated monitoring on database growth rate (assignee: TBD).

**Testing**

Expand Down