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
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.
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.
The text was updated successfully, but these errors were encountered:
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.
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 whereto
is the Atlas Mine and there is already aStakedToken
for that token. You could updateStakedToken.user = Transfer.params.from
.The text was updated successfully, but these errors were encountered: