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

Atlas Mine incorrectly reports StakedToken owner for MagicDragonDAO staking contract #107

Open
ohmoy opened this issue Mar 24, 2022 · 2 comments

Comments

@ohmoy
Copy link

ohmoy commented Mar 24, 2022

Hi Treasure team,

I'm one of the devs working on MagicDragonDAO. We noticed that the bridgeworld subgraph is incorrectly reporting who staked Dreamwinder (and our other nfts) into the Atlas Mine. Our staking contract has the correct amount of deposits reflected but shows no StakedToken ownership. Digging further we found that the StakedTokens are being attributed to our Multisig.

We suspect this is because the Staked event in the Atlas Mine contract doesn't emit who initiated the stake so you have to figure it out from transaction.to / transaction.from.

An additional step that could right this is to watch the Transfer events where to is the Atlas Mine and there is already a StakedToken for that token. You could update StakedToken.user = Transfer.params.from.

@wyze
Copy link
Contributor

wyze commented Mar 24, 2022

Can you provide a link to a transaction so I can take a look? We do have users using a multisig to execute transactions so thats why it is setup this way.

@ohmoy
Copy link
Author

ohmoy commented Mar 24, 2022

Here is a tx where our multisig executed a stake through our contract:

https://arbiscan.io/tx/0x9424b37b7eec56243ba52042c8367f8d9cf1f6482513cb9048c12116cd92620d

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

No branches or pull requests

2 participants