Claim params updated via contract call not reflected in the manifold front end

creator contract: 0xAabC150144094ef4acD2D41E5434F761be756ac9
mint page: fear | Manifold

i’m updating a claim via a contract call to update the mint start/end times and the token uri. the tx succeeds and getClaim() and tokenURI() both return as expected (with the new params) but the manifold page doesn’t reflect them.

for example, i updated the start time to a time in the past to turn off minting, but the frontend page still shows the mint button as if it was active, but the timer is 0.

the new metadata/image also isn’t reflected on the front-end after the change

going through the mint flow ends in a failed estimate, so the contract seems to be correct it’s just the frontend issue.

1 Like

Hi Ripe!

This use case is actually something we don’t currently support, but we’re very interested in it and would love to see if we can figure out a solution that works.

A couple of questions that would help us move forward:

  • Why do you need to perform on-chain transactions rather than handling it through Studio?
  • How frequently are you updating the metadata via contract calls?

If it’s easier, we also reached out to you via DMs — feel free to message us there as well!

1 Like

thanks @dongqtm

i’m handing the changes programmatically so it needs to be done outside the studio

when i change the claim details through the studio it sends a tx, so i figured i’d be able to send the same tx myself and have the front end update based on the new claim params

update frequency varies, but in this scenario it can be every few minutes

1 Like

Gotcha, I am discussing this matter internally to see if we can figure out a solution that work for you. Please hang tight!

1 Like

Hey Ripe,

We’ve identified the issue and are currently working on a fix. Thank you so much for reporting this — we’ll follow up here once the fix is live.

1 Like