updated getting-started with mitigated pitfalls

[PatrickAlphaC]

What 💻

1. Updated the recommended faucet -> Chainstack
2. Added a comment about private key use in a .env file
3. Removed broken atlas link

Why ✋

1. The learnweb3 faucet asks for very invasive GitHub authentication. See attached image below. I have informed the learnweb3 team to fix this.
2. We teach to always avoid private keys in .env files as it's one of the most common ways new web3 developers (experienced or not) lose funds. We even have students pledge to never put private keys with funds in them, and it's an anti-pattern that has been propagated across web3 hurting new people. pledge one and pledge 2
3. It's not a good idea to have students go to a potentially unmaintained example, see it not work, and then go "ah, f this. This chain just doesn't work." and move to another L2, or worse, out of web3 because of it. I left a comment about how this could be pretty easily fixed with a github actions that points to your templates folder. If you give me access to one I can make it for you and have atlas always paired with an up-to-date example.

Images

vidence 📷

Notes 📝

[MexicanAce]

For awareness, I've tried to validate the new repo would work with Atlas, but I'm getting Unable to Create Project: unhashable type: 'slice' error:

• https://app.atlaszk.com/projects?template=https://github.com/matter-labs/zksync-contract-templates/tree/main/templates/hardhat/solidity&open=Greeter.sol&chainId=300

I can follow-up with Atlas to troubleshoot and resolve

[MexicanAce]

LGTM, created open issue to close conversation and will follow-up in separate PR when received a fix from Atlas for new repo

[github-actions]

🎉 This PR is included in version 1.42.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀