
    E#i\)                         S SK Jr  S SKJrJrJr  S SKrSSKJr  SSKJ	r	  SSK
Jr  SS	KJrJr   " S
 S\5      r    SS\\\4   S\\\4   S\\\4   S\\\4   S\4
S jjrg)    )Mapping)AnyDict
NamedTupleN   )Address)ValidationError)HexBytes   )hash_domainhash_eip712_messagec                   8    \ rS rSr% Sr\\S'   \\S'   \\S'   Srg)SignableMessage   aD  
A message compatible with EIP-191_ that is ready to be signed.

The properties are components of an EIP-191_ signable message. Other message formats
can be encoded into this format for easy signing. This data structure doesn't need
to know about the original message format. For example, you can think of
EIP-712 as compiling down to an EIP-191 message.

In typical usage, you should never need to create these by hand. Instead, use
one of the available encode_* methods in this module, like:

    - :meth:`encode_typed_data`

.. _EIP-191: https://eips.ethereum.org/EIPS/eip-191
versionheaderbody N)__name__
__module____qualname____firstlineno____doc__bytes__annotations____static_attributes__r       l/home/james-whalen/.local/lib/python3.13/site-packages/ccxt/static_dependencies/ethereum/account/messages.pyr   r      s      NM
Kr   r   domain_datamessage_typesmessage_datafull_messagereturnc                 4   Ub  U c  Uc  Ub  [        S5      eUS   R                  5       nUS   R                  5       nSU;   aZ  [        UR                  5       5      nUS    Vs/ s H  owS   PM	     nn[	        U5      [	        U5      :w  a  [        SU SU S	35      eUR                  SS5        S
U;   a'  [        U5      n	US
   n
X:w  a  [        SU
 SU	 S	35      eUnUnUS   nOU nUnUn[        [        S5      [        U5      [        X5      5      $ s  snf )a  
Encode an EIP-712_ message in a manner compatible with other implementations
in use, such as the Metamask and Ethers ``signTypedData`` functions.

See the `EIP-712 spec <https://eips.ethereum.org/EIPS/eip-712>`_ for more information.

You may supply the information to be encoded in one of two ways:

As exactly three arguments:

    - ``domain_data``, a dict of the EIP-712 domain data
    - ``message_types``, a dict of custom types (do not include a ``EIP712Domain``
      key)
    - ``message_data``, a dict of the data to be signed

Or as a single argument:

    - ``full_message``, a dict containing the following keys:
        - ``types``, a dict of custom types (may include a ``EIP712Domain`` key)
        - ``primaryType``, (optional) a string of the primary type of the message
        - ``domain``, a dict of the EIP-712 domain data
        - ``message``, a dict of the data to be signed

.. WARNING:: Note that this code has not gone through an external audit, and
    the test cases are incomplete.

Type Coercion:
    - For fixed-size bytes types, smaller values will be padded to fit in larger
      types, but values larger than the type will raise ``ValueOutOfBounds``.
      e.g., an 8-byte value will be padded to fit a ``bytes16`` type, but 16-byte
      value provided for a ``bytes8`` type will raise an error.
    - Fixed-size and dynamic ``bytes`` types will accept ``int``s. Any negative
      values will be converted to ``0`` before being converted to ``bytes``
    - ``int`` and ``uint`` types will also accept strings. If prefixed with ``"0x"``
      , the string will be interpreted as hex. Otherwise, it will be interpreted as
      decimal.

Noteable differences from ``signTypedData``:
    - Custom types that are not alphanumeric will encode differently.
    - Custom types that are used but not defined in ``types`` will not encode.

:param domain_data: EIP712 domain data
:param message_types: custom types used by the `value` data
:param message_data: data to be signed
:param full_message: a dict containing all data and types
:returns: a ``SignableMessage``, an encoded message ready to be signed


.. doctest:: python

    >>> # examples of basic usage
    >>> from eth_account import Account
    >>> from .messages import encode_typed_data
    >>> # 3-argument usage

    >>> # all domain properties are optional
    >>> domain_data = {
    ...     "name": "Ether Mail",
    ...     "version": "1",
    ...     "chainId": 1,
    ...     "verifyingContract": "0xCcCCccccCCCCcCCCCCCcCcCccCcCCCcCcccccccC",
    ...     "salt": b"decafbeef",
    ... }
    >>> # custom types
    >>> message_types = {
    ...     "Person": [
    ...         {"name": "name", "type": "string"},
    ...         {"name": "wallet", "type": "address"},
    ...     ],
    ...     "Mail": [
    ...         {"name": "from", "type": "Person"},
    ...         {"name": "to", "type": "Person"},
    ...         {"name": "contents", "type": "string"},
    ...     ],
    ... }
    >>> # the data to be signed
    >>> message_data = {
    ...     "from": {
    ...         "name": "Cow",
    ...         "wallet": "0xCD2a3d9F938E13CD947Ec05AbC7FE734Df8DD826",
    ...     },
    ...     "to": {
    ...         "name": "Bob",
    ...         "wallet": "0xbBbBBBBbbBBBbbbBbbBbbbbBBbBbbbbBbBbbBBbB",
    ...     },
    ...     "contents": "Hello, Bob!",
    ... }
    >>> key = "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
    >>> signable_message = encode_typed_data(domain_data, message_types, message_data)
    >>> signed_message = Account.sign_message(signable_message, key)
    >>> signed_message.messageHash
    HexBytes('0xc5bb16ccc59ae9a3ad1cb8343d4e3351f057c994a97656e1aff8c134e56f7530')
    >>> # the message can be signed in one step using Account.sign_typed_data
    >>> signed_typed_data = Account.sign_typed_data(key, domain_data, message_types, message_data)
    >>> signed_typed_data == signed_message
    True

    >>> # 1-argument usage

    >>> # all domain properties are optional
    >>> full_message = {
    ...     "types": {
    ...         "EIP712Domain": [
    ...             {"name": "name", "type": "string"},
    ...             {"name": "version", "type": "string"},
    ...             {"name": "chainId", "type": "uint256"},
    ...             {"name": "verifyingContract", "type": "address"},
    ...             {"name": "salt", "type": "bytes32"},
    ...         ],
    ...         "Person": [
    ...             {"name": "name", "type": "string"},
    ...             {"name": "wallet", "type": "address"},
    ...         ],
    ...         "Mail": [
    ...             {"name": "from", "type": "Person"},
    ...             {"name": "to", "type": "Person"},
    ...             {"name": "contents", "type": "string"},
    ...         ],
    ...     },
    ...     "primaryType": "Mail",
    ...     "domain": {
    ...         "name": "Ether Mail",
    ...         "version": "1",
    ...         "chainId": 1,
    ...         "verifyingContract": "0xCcCCccccCCCCcCCCCCCcCcCccCcCCCcCcccccccC",
    ...         "salt": b"decafbeef"
    ...     },
    ...     "message": {
    ...         "from": {
    ...             "name": "Cow",
    ...             "wallet": "0xCD2a3d9F938E13CD947Ec05AbC7FE734Df8DD826"
    ...         },
    ...         "to": {
    ...             "name": "Bob",
    ...             "wallet": "0xbBbBBBBbbBBBbbbBbbBbbbbBBbBbbbbBbBbbBBbB"
    ...         },
    ...         "contents": "Hello, Bob!",
    ...     },
    ... }
    >>> signable_message_2 = encode_typed_data(full_message=full_message)
    >>> signed_message_2 = Account.sign_message(signable_message_2, key)
    >>> signed_message_2.messageHash
    HexBytes('0xc5bb16ccc59ae9a3ad1cb8343d4e3351f057c994a97656e1aff8c134e56f7530')
    >>> signed_message_2 == signed_message
    True
    >>> # the full_message can be signed in one step using Account.sign_typed_data
    >>> signed_typed_data_2 = Account.sign_typed_data(key, domain_data, message_types, message_data)
    >>> signed_typed_data_2 == signed_message_2
    True

.. _EIP-712: https://eips.ethereum.org/EIPS/eip-712
NzYou may supply either `full_message` as a single argument or `domain_data`, `message_types`, and `message_data` as three arguments, but not both.typesdomainEIP712DomainnamezThe fields provided in `domain` do not match the fields provided in `types.EIP712Domain`. The fields provided in `domain` were `z9`, but the fields provided in `types.EIP712Domain` were `z`.primaryTypezeThe provided `primaryType` does not match the derived `primaryType`. The provided `primaryType` was `z&`, but the derived `primaryType` was `message   )
ValueErrorcopylistkeyssetr	   popget_primary_typer   r
   r   r   )r   r    r!   r"   full_message_typesfull_message_domaindomain_data_keysfielddomain_types_keysderived_primary_typeprovided_primary_typeparsed_domain_dataparsed_message_typesparsed_message_datas                 r   encode_typed_datar=   0   s   | #('!  *'2779*8499; //#$7$<$<$>?+=n+M!+M%f+M  ! #$->)?@%)* +22C1DBH  	~t4 L(#34F#G $0$?!#<%-. /,-R1  11*95 ),*&'0F G!s   $D)NNNN)collections.abcr   typingr   r   r   warningsr   utils.curriedr	   hexbytesr
   &encode_typed_data.encoding_and_hashingr   r   r   strr=   r   r   r   <module>rE      s    
 j , #'$(#'#'	Wc3hWS>W sCx.W sCx.	W
 Wr   