feat: lookup network in evmchains; plugin-less networks, adhoc networks w/ correct name

[antazoey]

What I did

• Make it so if you connect to a network Ape hasn't an installed plugin for, it will look it up in evmchains and "just work"
• Make it so if you use a custom network e.g. connecting using a URL only, and that network is found in evmchains, it will set the correct names for the network

How I did it

Use evmchains library.

How to verify it

First, I have no plugin for moonbeam installed, but yet i can do this:

ape console --network moonbeam

and it "just works"

Second, if I connect to a URL in the same fashion:

ape console --network "https://moonriver.unitedbloc.com"

Not only does it work (did before), but the network name and stuff is correct:

In [1]: provider.network.name
Out[1]: 'moonriver'

In [2]: provider.network.ecosystem.name
Out[2]: 'moonbeam'

taa daaaa

Checklist

• All changes are completed
• New test cases have been added
• Documentation has been updated

[antazoey]

Failing test only happens on Web3>=6.20.2 not on 6.20.1 (which is what i was using locally)

[antazoey]

:<

[fubuloubu]

I feel like this could do with a little extra testing from @bitwise-constructs

[bitwise-constructs]

This looks good, I confirmed that custom network names still take precedence over names in evmchains

[bitwise-constructs]

Although I was digging more into the custom network names and I'm not clear on how that works.

If I set up one in my yaml like this

networks:
  custom:
    - name: scroll                    
      chain_id: 109                   
      ecosystem: shibarium            
      base_ecosystem_plugin: ethereum  
      default_provider: node          

and then call ape console --network scroll then as it evaluates, first it will check if it exists in the ecosystems of the NetworkManager, where this custom network is present but it is under its ecosystem value shibarium, not its custom network name scroll

(Pdb) self.ecosystem_names
{'ethereum', 'shibarium'}

but if I change the call to ape console --network shibarium to target the correct custom network, then the value in there doesn't have chain_id from the custom network config, it only has it in _networks_from_evmchains

(Pdb) self.ecosystems["shibarium"].__dict__
{'name': 'shibarium', 'request_header': {'User-Agent': 'ape-ethereum ape-shibarium'}, 'fee_token_symbol': 'ETH', 'fee_token_decimals': 18, '_networks_from_plugins': {}, '_networks_from_evmchains': {'mainnet': <shibarium:mainnet chain_id=109>, 'puppynet': <shibarium:puppynet chain_id=157>}}

[antazoey]

@bitwise-constructs Networks are the middle value in --network triplet, so when you do --network scroll, you are actually saying scroll:: (treating it like an ecosystem). And since there isn't an ecosystem configured or installed named scroll, it will look it up in evm-chains.

To use your custom network shibarium:scroll, you would do --network shibarium:scroll.

note: scroll is not a network on shibarium so youd be a bit hacky here, also because of that you would have to configure a URI for it