I currently have a geth node that isn't being used for very much that I don't mind donating to the cause - I can do an update this week to set the provider to that if metamascara is on the wrong network.
So the flow would be:
1. Default to injected Web3.
2. If no injected Web3, try Metamascara.
3. If Metamascara is on "network 4", switch to the geth node.
My one note is that if option 3 were to explode with popularity, I don't think I'll be able to afford crazy scaling for option 3 :P
Thanks! It looks like the only "right now" option given the metamascara api is to detect if the user is on metamask's "network 4" and ask the user to go to wallet.metamask.io and switch to the mainnet. Annoying, but at least it gives use to users without the extension. Feel free to keep extending this as well, I'll happily do any updates, especially if the metamask team includes functionality to change to the mainnet.
Thanks! It looks like the only "right now" option given the metamascara api is to detect if the user is on metamask's "network 4" and ask the user to go to wallet.metamask.io and switch to the mainnet. Annoying, but at least it gives use to users without the extension. Feel free to keep extending this as well, I'll happily do any updates, especially if the metamask team includes functionality to change to the mainnet.
I just realized why. It's probably because wallet.metamask.io has a setting to switch the network, and the default isn't the mainnet (can't remember what the default was.) I'm at aws re:invent this week, so I probably wont have time to look into the issue until this weekend. There's likely a way to default the provider to the mainnet unless the user has specified another network on wallet.metamask.io
In response to a comment on the pull request on Github, note that you do **not** need to sign-into metamascara to browse/view all the BPs, the Web3 provider exists whether or not the user has ever even been to wallet.metamask.io. Setting up a wallet at wallet.metamask.io does allow the user to fully use the site without the Metamask extension though.
Pull request created: https://github.com/coinop-logan/coinop-logan.github.io/pull/4 Metamascara works. To use, disable the Metamask extension and create a wallet at wallet.metamask.io.
I'm primarily a software developer, however my interest in blockchain/crypto is fairly broad over all aspects of the space. I have high proficiency in Ethereum, including DAOs/on chain governance, and understand the technical side highly. That may not be necessary for writing nontechnical documentation, but it certainly can't hurt.
Nate Welchnathanielawelch@gmail.comflygoingnathaniel-welch-474b15127Software DeveloperI'm a mainly back end software developer that's passionate about cryptocurrency, blockchains, and smart contract development. I have an AWS Developer - Associate level certification.