Tokengate eligibility issue & missing attributes for tokengate rule

Hello Manifold Support,

We’ve been experiencing issues with token gating eligibility on our Shopify shop recently.

For a newly launched collection, we configured gating rules for all products based on “Filter by attribute” (as shown in the screenshot). However, token holders with matching metadata attributes are facing eligibility issues when trying to purchase the product.


For testing purposes, when we try using the gating rule with “Select individual token” and specify a particular token ID, it correctly shows the holder as eligible based on the matching token ID. However, this isn’t ideal, as we need to apply the gating rule using “Filter by attribute” (e.g., Card Name: XXXX).

We’ve already tried the same procedure on a different store, and the results were the same. It shows no eligibility for any rules configured with filter by attributes for that specific contract address.


Product URL:
https://shop.chimpers.com/products/mushashi

Contract address (Base):
0x3efaaf47312e65fc5b1ea139564712e7bf9dae2f

Holder wallet address:
0x5ca3502Ef31A75dC49cAad9d8C5C9A2b9730eB55

Token URL (opensea):
https://opensea.io/assets/base/0x3efaaf47312e65fc5b1ea139564712e7bf9dae2f/362



On another note, there are two specific token’s metadata attribute that still do not appear in the “Filter by attributes” list for configuring the token gate rule based on. We’ve already tried refreshing the metadata, but still, they’re not showing up in the list.


It would be really nice to have these issues sorted as soon as possible. Thank you!

Hi, looks like some tokens are missing metadata indexing/attributes. Have you tried to click the refresh metadata button for the collection on that shopify configuration page?

Note, we’re also investigating the lack of attribute indexing on our side atm.

Yes, I’ve already tried refreshing the metadata using that button, but two attributes are still missing for the following cards:

  • Card Name: Genoncamer
  • Card Name: Kiti

Note, we’re also investigating the lack of attribute indexing on our side atm.

Thank you.

It would also be helpful to look into the eligibility issues mentioned in the main post, as they’re affecting all other configured products in the same collection.

This collection’s metadata should be properly refreshed now (0x3efaaf47312e65fc5b1ea139564712e7bf9dae2f)

Are you able to confirm it works properly?

Are there any other contracts or collections you were having issues with?

Hmm, looks like things didn’t properly refresh, due to a likely rate limit on your api server.

Ok, looks like it’s refreshed all these tokens.

It seems both the missing attributes and gating issues have been resolved. Thank you!

Is there a way to prevent the API rate limit issue from happening in the future, or was it just a rare occurrence?

We were being rate limited by the chimpers metadata server so I’m not sure what’s set up on that end.