You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue comes from this line in the subgraph mapping: request.requester = event.transaction.from; So essentially the tag-registry-rewards repo script tags the top-level address that led to the event, instead of the actual requester. Some people use sponsored callers, and currently the script would distribute the rewards to the sponsor addresses instead of to the actual correct addresses.
the month of april a workaround was made in order to generate that month's curate incentives:
The issue comes from this line in the subgraph mapping:
request.requester = event.transaction.from;
So essentially thetag-registry-rewards
repo script tags the top-level address that led to the event, instead of the actual requester. Some people use sponsored callers, and currently the script would distribute the rewards to the sponsor addresses instead of to the actual correct addresses.the month of april a workaround was made in order to generate that month's curate incentives:
https://github.com/y86993/tag-registry-rewards
https://github.com/y86993/gtcr-subgraph
Pls fix
Probably some change also necessary on the tag-registry-rewards repo. Can use the repos above as reference
The text was updated successfully, but these errors were encountered: