We want to start hosting the website in netlify because it makes deployments a non-issue, and we get the added super-nice benefit of previews in pull requests.
So, when you make a pull request in github, netlify will deploy your changes to a temporary URL that we will be able to try before approving it.
Before updating the ethernaut domain to point to this site, I would like to ask for your help to give it a few tries, and make sure that it works just the same as the one we are hosting on our server.
Hi @elopio Love hearing about making deployments easier for Ethernaut.
I ran through 0 Hello Ethernaut and 2 Fallout levels with Brave and MetaMask on Windows 10.
I got multiple messages for instance address when I first went to the site. I haven’t seen again.
When on a level, if I change networks, from Ropsten to Mainnet and then when I switch back to Ropsten I get a page not found error. I don’t get this with the current production site.
Thanks a lot for testing!
I think I’ve fixed the redirects that were affecting refresh and the network change:
About the multiple messages for instance address, I didn’t get that. I saw one popup asking for permission to access my address, and that’s it. If you get any more clues about this, please share them with a screenshot and the info of your browser.
Thanks, I am not getting a page not found error anymore when changing networks.
The first time I load Ethernaut https://openzeppelin-ethernaut.netlify.com/ and send a transaction to Get New Instance once the transaction is mined I get multiple Instance address messages (17 duplicates in this screenshot)
I am running on Brave on Windows 10. Let me know what other information would be useful.