-
Couldn't load subscription status.
- Fork 260
[ETHEREUM-CONTRACTS] emit Transfer event on flow create/delete and units changing from/to 0 #2114
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
base: dev
Are you sure you want to change the base?
Conversation
Changelog ReminderReminder to update the CHANGELOG.md for any of the modified packages in this PR.
|
Is it from the original OZ old code base of ERC777/ERC20 |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
packages/ethereum-contracts/contracts/agreements/ConstantFlowAgreementV1.sol
Outdated
Show resolved
Hide resolved
packages/ethereum-contracts/contracts/agreements/gdav1/SuperfluidPool.sol
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
|
to address #2115 too |
answered here |
What & Why
Many indexers (e.g. explorers) rely on the ERC20
Transfereventa) for managing the set of token holders,.
b) for triggering a balance calculation
With SuperTokens, that can lead to accounts receiving via flows or distributions to remain invisible, and for the balance to never be updated.
How
By emitting Transfer events, we shall be able to somewhat mitigate this issues:
a) by emitting a Transfer event when creating a flow or assigning pool units, the receiving account is included in the set of token holders to be considered
b) by emitting a Transfer event when deleting a flow or resetting pool units, some indexers may trigger a balance check and thereby update the account balance to the correct number
Other
Also bumped version to 1.14.0 as this may be the last PR before release.