From 1b4399cf7964ae01ef743f73a97c29a2214e51c8 Mon Sep 17 00:00:00 2001
From: zhanglangning <zln1905391059@163.com>
Date: Wed, 12 Aug 2026 05:02:06 +0800
Subject: [PATCH] docs: document exception hierarchy

---
 docs/exceptions.rst         | 95 +++++++++++++++++++++++++++++++++++++
 docs/toc.rst                |  1 +
 newsfragments/3442.docs.rst |  2 +
 3 files changed, 98 insertions(+)
 create mode 100644 docs/exceptions.rst
 create mode 100644 newsfragments/3442.docs.rst

diff --git a/docs/exceptions.rst b/docs/exceptions.rst
new file mode 100644
index 0000000000..7595c90b09
--- /dev/null
+++ b/docs/exceptions.rst
@@ -0,0 +1,95 @@
+.. _exceptions:
+
+Exceptions
+==========
+
+Public exceptions defined in ``web3.exceptions`` inherit from
+``Web3Exception``. This makes it possible to catch errors raised by the core
+web3.py API separately from exceptions raised by application code or other
+libraries.
+
+Catch the most specific exception that your application can handle, and use
+``Web3Exception`` when the same recovery applies to any web3.py error:
+
+.. code-block:: python
+
+    from web3.exceptions import (
+        TransactionNotFound,
+        Web3Exception,
+        Web3RPCError,
+    )
+
+    try:
+        receipt = w3.eth.get_transaction_receipt(transaction_hash)
+    except TransactionNotFound:
+        # The transaction is not available yet.
+        receipt = None
+    except Web3RPCError as exc:
+        # The node returned another JSON-RPC error.
+        logger.warning(exc.user_message)
+    except Web3Exception:
+        # A non-RPC web3.py error occurred.
+        raise
+
+``Web3Exception`` only covers exceptions defined in ``web3.exceptions``.
+Exceptions from third-party libraries or user callbacks are not necessarily
+wrapped by web3.py. The ENS API has a separate base exception,
+:class:`~ens.exceptions.ENSException`.
+
+
+Exception hierarchy
+-------------------
+
+The hierarchy groups exceptions by the operation that failed. Some commonly
+used branches are:
+
+* ``Web3RPCError`` for failures associated with JSON-RPC responses. More
+  specific subclasses include ``MethodUnavailable``, ``RequestTimedOut``,
+  ``TransactionNotFound``, ``TransactionIndexingInProgress``, and
+  ``BlockNotFound``.
+* ``Web3ValidationError`` for invalid values detected by web3.py.
+  ``ExtraDataLengthError`` is a more specific validation error.
+* ``MismatchedABI`` for an ABI that does not match the requested function,
+  event, or supplied arguments. Its subclasses include
+  ``ABIFunctionNotFound`` and ``ABIEventNotFound``.
+* ``ContractLogicError`` for contract reverts, with ``ContractCustomError``,
+  ``ContractPanicError``, and ``OffchainLookup`` providing more detail when the
+  revert data can be identified.
+* ``InvalidTransaction`` for an invalid combination of transaction arguments.
+* ``ProviderConnectionError``, ``BadResponseFormat``, and
+  ``PersistentConnectionError`` for provider and response handling failures.
+
+web3.py also provides exceptions compatible with common built-in exception
+types: ``Web3AssertionError``, ``Web3ValueError``, ``Web3AttributeError``, and
+``Web3TypeError``. Each can be caught through either ``Web3Exception`` or its
+corresponding built-in exception type.
+
+
+JSON-RPC errors
+---------------
+
+When a valid JSON-RPC response contains an ``error`` object, web3.py first
+applies any error formatter registered for that method. A formatter may raise
+another ``Web3Exception`` branch; for example, a contract revert from
+``eth_call`` raises ``ContractLogicError``. If no formatter raises an exception,
+the general validation path raises ``Web3RPCError`` or a recognized subclass.
+For example, JSON-RPC error code ``-32601`` raises ``MethodUnavailable``, while
+known timeout messages raise ``RequestTimedOut``.
+
+JSON-RPC does not standardize an error code for every failure. Client
+implementations can also use different messages for the same condition. Some
+specialized exceptions therefore depend on matching error messages returned by
+the node. If a client changes its message, web3.py may raise the general
+``Web3RPCError`` instead of a more specific subclass. Applications that need to
+handle both cases should catch the specific exception first and then
+``Web3RPCError``.
+
+``Web3RPCError`` exposes two useful attributes:
+
+``rpc_response``
+    The complete JSON-RPC response, when available.
+
+``user_message``
+    A concise explanation intended for application-level error reporting. It
+    defaults to a general RPC error message when no specific ``user_message``
+    is provided.
diff --git a/docs/toc.rst b/docs/toc.rst
index de894ec02a..cbf801d8be 100644
--- a/docs/toc.rst
+++ b/docs/toc.rst
@@ -23,6 +23,7 @@ Table of Contents
     formatters
     internals
     ens_overview
+    exceptions
     troubleshooting
     migration
 
diff --git a/newsfragments/3442.docs.rst b/newsfragments/3442.docs.rst
new file mode 100644
index 0000000000..d6b682f185
--- /dev/null
+++ b/newsfragments/3442.docs.rst
@@ -0,0 +1,2 @@
+Document the web3.py exception hierarchy and how JSON-RPC responses map to general
+or specialized exceptions.