Consider ThirdWeb Release for SC deployment

[neatonk]

This solves a number of issues we faced during the hackathon. E.g. keeping track of deployments, copying ABIs, and avoiding the need to export a private key for contract deployment. ThirdWeb Release simplifies the process of deploying and building on our smart contracts for us and for other projects that choose to fork our UI or build a custom experience.

• https://blog.thirdweb.com/thirdweb-release
• https://blog.thirdweb.com/thirdweb-release#why-did-we-build-this
• https://portal.thirdweb.com/release

[josealonso]

This solves a number of issues we faced during the hackathon. E.g. keeping track of deployments, copying ABIs, and avoiding the need to export a private key for contract deployment. ThirdWeb Release simplifies the process of deploying and building on our smart contracts for us and for other projects that choose to fork our UI or build a custom experience.

* https://blog.thirdweb.com/thirdweb-release

* https://blog.thirdweb.com/thirdweb-release#why-did-we-build-this

* https://portal.thirdweb.com/release

I already knew thirdweb. We can use their template contracts. As far as I see, they have integrated the standard contracts (721, 721A, etc.) with an interesting dashboard. This dashboard allows to read and write to the contracts, like you do in etherscan but with a more friendly UI, as well as automating the deployments.
We might want to customize that dashboard to put the ReleaseClub logo and some other modifications. It's a React project. This part is quite similar to what Zora offers, I think.

I wanted to explain that the deployments automation is possible because they use proxies, which is what I implemented last week. Of course, their proxy implementation is better than mime, so I would use theirs. Quoting their docs,

When you deploy one, under the hood you are creating a proxy contract, which reduces the gas cost of deploying smart contracts by ~90% for you.

This works by having our smart contracts run the underlying logic, meaning you only deploy the code that is unique
 to your contract. This is possible since all of the contracts deployed using our pre-built contracts run the same logic
 for things like minting, transferring, and burning tokens.

[josealonso]

One possible disadvantage that I see is a client wanting to use an NFT contract he has written already.

[josealonso]

I hope I can deliver the proxy factory contract this week. I didn't use ThirdWeb contracts, because they are too complex. But I looked at them for reference, like I do with OpenZeppelin's and scaffold-eth's.

[neatonk]

What I'm suggesting above is that we consider using ThirdWeb to deploy our custom contracts. This would likely make #5 unnecessary.

It is interesting that ThirdWeb provides template contracts, but I am not suggesting that we use them.