staking badge not appearing

[Dikewalker]

Describe the bug Staking badge doesn't show under Near Address

To Reproduce Steps to reproduce the behavior:

1. Go to 'https://stats.gallery/mainnet/wimscot123.near/
2. Click on 'quests'
3. Scroll down to 'achievements.'
4. See staking badge showing up under achievements. But not showing on top

Expected behavior Staking badge should show on top under near address. Cause: Locked up contract since ICO

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10
• Browser Chrome
• Version latest

Additional context Add any other context about the problem here.

[Bexanderthebex]

@Dikewalker, I investigated the issue and seems like the NEAR team expects the pool name should be of the pattern %.poolv1.near but yours might be a special case that they weren't able to consider (yours was <hash>.lockup.near) I am still coordinating with them before opening a fix!

[encody]

Currently the staking badge implementation looks for a transaction from your account to an account with an id that matches %.poolv1.near. You can check if an account has any transactions that match requirement by running this query on the indexer:

select * from transactions where signer_account_id = 'wimscot123.near' and receiver_account_id like '%.poolv1.near'

and see if it returns any rows.

[encody]

I'm writing a new staking badge query that will target receipts instead of transactions, so your account actions will be eligible, as I assume you're talking about transactions like this one. Could you possibly demonstrate under what conditions this transaction occurred, @Dikewalker ? Thanks!

[Dikewalker]

@Jacob @bexanderthebex, thank you for your support. My only issue was that the ICO locked tokens that have been staked in september 2021 were not identified by the staking badge query. I am not that tech savvy.To be honest I can't recollect those transactions in August anymore. But I am only using google chrome and e-mail notification with my wallet, if that helps. Keep up the great work! Cheers

On Wed, 6 Oct 2021 at 17:28, Jacob @.***> wrote:

I'm writing a new staking badge query that will target receipts instead of transactions, so your account actions will be eligible, as I assume you're talking about transactions like this one https://explorer.near.org/transactions/9sWoZVjT38HougKSgtVLiibxp8K9rKDSfZxKnumUEWdU. Could you possibly demonstrate under what conditions this transaction occurred, @Dikewalker https://github.com/Dikewalker ? Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NEAR-Edu/stats.gallery/issues/61#issuecomment-936619741, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV47D5SF6FF6MKJREGIFAADUFR2JBANCNFSM5FI4VAWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[Dikewalker]

eeeh I mean september 2020! sorry

On Wed, 6 Oct 2021 at 17:49, William. G @.***> wrote:

@Jacob @bexanderthebex, thank you for your support. My only issue was that the ICO locked tokens that have been staked in september 2021 were not identified by the staking badge query. I am not that tech savvy.To be honest I can't recollect those transactions in August anymore. But I am only using google chrome and e-mail notification with my wallet, if that helps. Keep up the great work! Cheers

On Wed, 6 Oct 2021 at 17:28, Jacob @.***> wrote:

I'm writing a new staking badge query that will target receipts instead of transactions, so your account actions will be eligible, as I assume you're talking about transactions like this one https://explorer.near.org/transactions/9sWoZVjT38HougKSgtVLiibxp8K9rKDSfZxKnumUEWdU. Could you possibly demonstrate under what conditions this transaction occurred, @Dikewalker https://github.com/Dikewalker ? Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NEAR-Edu/stats.gallery/issues/61#issuecomment-936619741, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV47D5SF6FF6MKJREGIFAADUFR2JBANCNFSM5FI4VAWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[encody]

@Dikewalker Please check again, a fix has been deployed.

[Dikewalker]

Legends. Awesome, thanks!

On Wed, 6 Oct 2021 at 19:00, Jacob @.***> wrote:

Closed #61 https://github.com/NEAR-Edu/stats.gallery/issues/61.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NEAR-Edu/stats.gallery/issues/61#event-5422675855, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV47D5RXKHWSCUEPHZO74A3UFSFFRANCNFSM5FI4VAWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.