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

Investigate other Value=0 cases for events in TxOpsFromLogs #161

Open
eelanagaraj opened this issue Apr 26, 2021 · 3 comments
Open

Investigate other Value=0 cases for events in TxOpsFromLogs #161

eelanagaraj opened this issue Apr 26, 2021 · 3 comments

Comments

@eelanagaraj
Copy link
Contributor

eelanagaraj commented Apr 26, 2021

There have been two edge cases identified thus far (GoldLocked and GoldWithdrawn). Take time to investigate whether it's possible to skip transfer creation for all Value=0 transactions in this function, or if there is a more robust solution here to prevent future issues with this.

Need to add for GoldWithdrawn, GoldLocked, GoldRelocked, GoldUnlocked ( + Election events as well)

Solution may be as simple as adding a check (Value==0, exclude those transfers), but double check that this does not break anything for the other events. (+ run full CLI checks if possible).

@aslawson
Copy link

Seems like remaining work here from DevX is to add this to checks to all the methods:GoldWithdrawn, GoldLocked, GoldRelocked, GoldUnlocked

Contract Changes are here: celo-org/celo-monorepo#7758

@barbaraliau
Copy link

Related to #7758

@AlexBHarley
Copy link
Contributor

Some findings here. Logs are only matched with transfer if they are one of

  • lockGold
  • unlockGold
  • slash.

This logic can be seen here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants