Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP
Write V2 Contract Events Spec for Ragekick, InternalTransfer, Deposit
Review V2 Contract Events Spec (@ameensol )
Actually emit new events
Write Tests
Tests Passing
V2 Contract Events
V2 Contract Events Tests
MolochV2 Events Spec Feedback
The Ragequit event in _ragequit emits msg.sender — which is wrong for ragekicks. This needs to be memberAddress (as has been pointed out by @sbetamc earlier), or maybe we would even want a separate Ragekick event?
Added the Ragekick event, will fixed the Ragequit param.
In general, is the "outside world" fine with the getters and events we currently have? For example, internal transfers don't emit events at all.
Added InternalTransfer and Deposit events for public visibility. (this adds significant overhead to some functions that fire multiple InternalTransfer events.