The following is a list of common issues encountered while using the Marketplace Widgets.

My Marketplace Widgets don't reload!

>= 3.0.0: Ensure that when you are adding an HTML element, the element has a valid data-widget property before being appended to the DOM.

< 3.0.0: If you added an HTML element with a data-widget property after the window.load event (dynamically, or client-side rendering), the widget will not be replaced. To replace it, you can manually dispatch a m-refresh-widget event through the window object.

My data-prop is not being picked up for my widget!

Make sure that all widgets injecting a same listing have the same data-props appended to it. Namely, if you use one of the the following data-props, make sure they appear on all widgets that refer to the same data-id/data-network or data-id/data-address combination:

  • data-allow-list-file;

  • data-allow-list-file-no-values;

  • data-max-per-purchase;

  • data-merkle-tree-campaign-id;

  • data-referral-address;

  • data-bidding-starts-at-override;

  • data-current-bid-text-override;

  • data-identity-verifier-message-override;

  • data-minimum-bid-text-override;

  • data-winning-bid-text-override.

RPC Error: execution reverted. Transaction reverted without a reason string.

Ensure that your listing ID and chosen network ID are correct. If those are correct, it's possible that your listing data-widget is being displayed with the wrong data-version.

The bid input shows "Minimum bid price: 0.0 ETH", but someone has already bid.

The text for the bid input may show 0.0 ETH if:

  • you have an Ethereum provider and are not on the same network as the auction;

  • you do not have an Ethereum provider.

To fix this, make sure you add a link to an Ethereum node on the same network as the auction to data-fallback-provider.

Example (for mainnet auctions):


Still encountering issues? Contact us and we'll gladly help!

Last updated