kodadot / nft-gallery

Generative Art Marketplace
https://koda.art
MIT License
634 stars 361 forks source link

Nft shows listed, but it is not anymore due to Singular #1302

Closed mcfly12 closed 2 months ago

mcfly12 commented 2 years ago

What happened?

There are these two nfts listed on Kodadot, which are no longer available anymore due to Singular, but still listed on Kodadot. I am afraid that a buy will not work if I try and might lose my KSM. Unfortunately I am not that familiar to read on chain data in detail. 1st piece got already resold and is not listed anymore, due to Singular. 1st piece https://kodadot.xyz/rmrk/detail/9546415-b4d42c2aa369ee1f27-PREZT-THINKER-0000000000000118 https://singular.rmrk.app/collectibles/9546415-b4d42c2aa369ee1f27-PREZT-THINKER-0000000000000118

2nd piece https://kodadot.xyz/rmrk/detail/9811179-b4d42c2aa369ee1f27-PREZT-DZIKO-0000000000000182 https://singular.rmrk.app/collectibles/9811179-b4d42c2aa369ee1f27-PREZT-DZIKO-0000000000000182

Please reproduce in steps

Click on the Kodadot link of each piece and compare with the Singular link.

Expected Behavior

I expected that I can buy the piece on Kodadot. I did not try, because I am afraid to lose the KSM.

What browsers are you seeing the problem on?

Firefox

Are you logged in?

Yes

At which address did you encounter bug?

nft.kodadot.xyz / kodadot.xyz

Screenshots

kodadot_1st_piece singular_1st_piece

Relevant log output

No response

Code of Conduct

vikiival commented 2 years ago

Hey,

thanks for opening the issue. It's definitely a p1 to resolve

vikiival commented 2 years ago

reverse engineering

query failedById($id: String!) {
  failedEntities(filter: { value: { includesInsensitive: $id } }, orderBy: CREATED_AT_DESC) {
    nodes {
      interaction
      createdAt
      reason
      value
    }
  }
}

Looks like I need to reindex our Indexer again

yangwao commented 2 years ago

Is this resolved? I guess?

mcfly12 commented 2 years ago

Nothing resolved so far. The issue is still as described.

yangwao commented 10 months ago

Nothing resolved so far. The issue is still as described.

it's still issue? We've changed the endpoint a few times since then.