Content
@
0 reply
0 recast
2 reactions
Antoine
@antoinedc
To smart contract developers testing on public testnets (sepolia, etc...): Why aren't you setting up your own private testnet (anvil/hardhat with mainnet fork)? What are the benefits of public testnets over private ones?
2 replies
0 recast
1 reaction
Steve
@stevedylandev.eth
Primarily the ability to deploy a front end other can test, as well as making sure it works with marketplaces like OpenSea if working with NFTs. We have over 100 people testing cosmiccowboys.cloud which gives us very valuable feedback
1 reply
0 recast
1 reaction
Antoine
@antoinedc
By front-end, you mean the etherscan read/write contract interface? And how do you check if it's working with opensea? Do they have a testnet version? Thanks for your answers 🙏!
1 reply
0 recast
1 reaction
Steve
@stevedylandev.eth
Of course! 🫡 It could depend on your needs; for example you could do plenty of testing with hardhat or foundry, which you should, however there are some test cases you might miss unless someone else thinks of it. They will likely be people who are not writing test scripts and that FE will make it accessible
1 reply
0 recast
0 reaction
Steve
@stevedylandev.eth
OpenSea does have a test site which makes it soooo nice to make sure your NFTs are working! https://testnets.OpenSea.io
1 reply
0 recast
0 reaction
Steve
@stevedylandev.eth
Oh and to clarify, a front end would be something like a Next.js or another framework that’s wired up to the contract using libraries like Viem.sh so a user can interact with it. Also check out RainbowKit for connecting user wallets. In the end I guess it depends what you want your smart contract to do!
1 reply
0 recast
0 reaction
