Skip to content
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.

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

Contract's monitoring #172

Open
AuHau opened this issue Sep 12, 2024 · 0 comments
Open

Contract's monitoring #172

AuHau opened this issue Sep 12, 2024 · 0 comments
Labels
Marketplace See https://miro.com/app/board/uXjVNZ03E-c=/ for details

Comments

@AuHau
Copy link
Member

AuHau commented Sep 12, 2024

As part of the contract's deployment work, I ran into a question. We might have the capability to upgrade the contract's logic to fix a bug/exploit. One case is if the problem is reported to us or discovered by us, then we can act on it. What of a case if the logic is being exploited? It could be that somebody in the community notices and might report it to us, but it could be that it goes undetected for quite some time before someone reports it. This is mainly related to the business logic part as disappearing funds is fairly easy to detect. I am thinking cases like:

  • unintended prolonging of requests
  • modifying all sorts of counters (missed proof counters etc)

Should we monitor the contracts in some way? What metrics should be tracked?

@AuHau AuHau added the Marketplace See https://miro.com/app/board/uXjVNZ03E-c=/ for details label Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Marketplace See https://miro.com/app/board/uXjVNZ03E-c=/ for details
Projects
None yet
Development

No branches or pull requests

1 participant