contracts VS widgets

The matic.network website is down, which hosted a bunch of services different projects rely on. If you are using the API for obtaining current gas / market data then your systems will not have the latest gas estimates from the gasstation service.

I am not a pro. But I am guessing you are asking for this - https://github.com/maticnetwork/contracts

Merch is a good idea for sure, but most projects don’t know how to properly brand their NFT project. You’ll need to create a culture around your NFT first (check Milady for example). If, as you say, you have a vibrant community that will support your project, you’ll need to think of the easiest way for them to pay for merch. For example, assume your NFT is on Polygon. You should be able to accept Matic, bridged USDC, or your own token (if you have any). You’ll need a gateway/plugin that supports L2 stables, no KYC, etc. We are using Sprintcheckout for this, but I’ve heard that Depay is also a good option. Next, depending on the chain you are building on, you’ll need to do A LOT of ecosystem-specific BD, and then expand beyond your ecosystem. Most of the time you’ll find relevant services and products that you can get referral fees on. Great way to capitalize on the community, but don’t overdo it. Web3 games are quite hard to build, so you’d have to sell the perceived value and raise money in the meantime. I am sure there are easier ways to do it. Just don’t go launch another collection for more $$ like Azuki did.