Deprecate ropsten

docs/ens_overview.rst

@@ -233,28 +233,5 @@ Wildcard Resolution Support
 The ``ENS`` module supports Wildcard Resolution for resolvers that implement the ``ExtendedResolver`` interface
 as described in `ENSIP-10 <https://docs.ens.domains/ens-improvement-proposals/ensip-10-wildcard-resolution>`_.
 Resolvers that implement the extended resolver interface should return ``True`` when calling the
-``supportsInterface()`` function with the extended resolver interface id ``0x9061b923`` and should resolve subdomains
+``supportsInterface()`` function with the extended resolver interface id ``"0x9061b923"`` and should resolve subdomains
 to a unique address.
-
-A working example of a resolver that supports wildcard resolution is the resolver for the ``hatch.eth`` record on the
-Ropsten testnet.
-
-.. code-block:: python
-
-    # connect to the Ropsten testnet
-    >>> w3 = Web3(WebsocketProvider("wss://{ropsten_provider}"))
-    >>> ns = ENS.fromWeb3(w3)
-
-    # get the resolver for `hatch.eth`
-    >>> resolver = ns.resolver('hatch.eth')
-    >>> resolver.address
-    '0x8fc4C380c5d539aE631daF3Ca9182b40FB21D1ae'
-
-    # verify extended resolver interface support
-    >>> resolver.caller.supportsInterface('0x9061b923')
-    True
-
-    >>> ns.address('random-subdomain.hatch.eth')
-    '0x49D4c4ff230688e4A357bc057e7E35e64d271939'
-    >>> ns.address('another-random-subdomain.hatch.eth')
-    '0xb35359B6450B0CbC9BE15A4eE6bcb8c5b0d9fC4A'

docs/ethpm.rst

@@ -234,7 +234,6 @@ way through the EIP process)
 -  ``chain_id``: Chain ID of the chain on which the registry lives. Defaults to Mainnet. Supported chains include...
 
   - 1: Mainnet
-  - 3: Ropsten
   - 4: Rinkeby
   - 5: Goerli
 

docs/node.rst

@@ -94,9 +94,7 @@ then you connect to the main Ethereum network.
 
 If you want to test these things without using real ether, though, then you
 need to connect to a test network. There are several test networks to
-choose from. One test network, Ropsten, is the most similar to the production network.
-However, spam and mining attacks have happened,
-which is disruptive when you want to test out a contract.
+choose from, Rinkeby and Goerli being the longest running.
 
 There are some alternative networks that limit the damage of spam attacks, but
 they are not standardized across node software. Geth runs their own (Rinkeby).

docs/providers.rst

@@ -106,7 +106,7 @@ successful connection it can make:
 2. :class:`~web3.providers.ipc.IPCProvider`, which looks for several IPC file locations.
    ``IPCProvider`` will not automatically detect a testnet connection, it is suggested that the
    user instead uses a ``w3`` instance from ``web3.auto.infura`` (e.g.
-   ``from web3.auto.infura.ropsten import w3``) if they want to auto-detect a testnet.
+   ``from web3.auto.infura.goerli import w3``) if they want to auto-detect a testnet.
 3. :class:`~web3.providers.rpc.HTTPProvider`, which attempts to connect to "http://localhost:8545"
 4. ``None`` - if no providers are successful, you can still use Web3 APIs
    that do not require a connection, like:

docs/troubleshooting.rst

@@ -111,10 +111,9 @@ Faucet mechanisms tend to come and go, so if any information here is
 out of date, try the `Ethereum Stackexchange <https://ethereum.stackexchange.com/>`_.
 Here are some links to testnet ether instructions (in no particular order):
 
-- `Kovan <https://github.com/kovan-testnet/faucet>`_
 - `Rinkeby <https://www.rinkeby.io/#faucet>`_
-- `Ropsten <https://www.reddit.com/r/ethdev/comments/72ltwj/the_new_if_you_need_some_ropsten_testnet_ethers/>`_
-
+- `Goerli <https://goerli.net>`_ (different faucet links on top menu bar)
+- `Sepolia <https://faucet.sepolia.dev>`_
 
 .. _account_troubleshooting:
 

ethpm/constants.py

@@ -12,7 +12,6 @@
 
 SUPPORTED_CHAIN_IDS = {
     1: "mainnet",
-    3: "ropsten",
     4: "rinkeby",
     5: "goerli",
     11155111: "sepolia",

ethpm/validation/uri.py

@@ -103,7 +103,7 @@ def validate_registry_uri_authority(auth: str) -> None:
     if not is_supported_chain_id(to_int(text=chain_id)):
         raise EthPMValidationError(
             f"Chain ID: {chain_id} is not supported. Supported chain ids include: "
-            "1 (mainnet), 3 (ropsten), 4 (rinkeby), 5 (goerli), and 11155111 (sepolia)."
+            "1 (mainnet), 4 (rinkeby), 5 (goerli), and 11155111 (sepolia)."
             "Please try again with a valid registry URI."
         )
 

newsfragments/2672.removal.rst

@@ -0,0 +1 @@
+Remove Ropsten auto provider and the relevant references to Ropsten across the repo

tests/ethpm/_utils/test_chain_utils.py

@@ -46,7 +46,6 @@ def test_parse_BIP122_uri(value, expected_resource_type):
     "chain_id,expected",
     (
         (1, True),
-        (3, True),
         (4, True),
         (5, True),
         (11155111, True),

tests/ethpm/test_uri.py

@@ -77,10 +77,6 @@ def test_create_github_uri():
             "erc1319://0x6b5DA3cA4286Baa7fBaf64EEEE1834C7d430B729",
             ["0x6b5DA3cA4286Baa7fBaf64EEEE1834C7d430B729", "1", None, None, None, None],
         ),
-        (
-            "erc1319://0x6b5DA3cA4286Baa7fBaf64EEEE1834C7d430B729:3",
-            ["0x6b5DA3cA4286Baa7fBaf64EEEE1834C7d430B729", "3", None, None, None, None],
-        ),
         (
             "erc1319://0x6b5DA3cA4286Baa7fBaf64EEEE1834C7d430B729:5/owned",
             [

web3/_utils/contract_sources/SimpleResolver.sol

@@ -1,8 +1,6 @@
 pragma solidity ^0.8.13;
 
 contract SimpleResolver {
-    // deployed on ropsten at address = 0xD4D522c96111679bF86220deFE75e0aA1df890b4
-
     function supportsInterface(bytes4 interfaceID) public returns (bool) {
         return interfaceID == 0x3b3b57de;
     }

web3/auto/infura/endpoints.py

@@ -17,7 +17,6 @@
 )
 
 INFURA_MAINNET_DOMAIN = "mainnet.infura.io"
-INFURA_ROPSTEN_DOMAIN = "ropsten.infura.io"
 INFURA_GOERLI_DOMAIN = "goerli.infura.io"
 INFURA_RINKEBY_DOMAIN = "rinkeby.infura.io"
 INFURA_SEPOLIA_DOMAIN = "sepolia.infura.io"