feat(concepts): add section for Ethereum signed processes, modules, a…

…nd messages

src/concepts/messages.md

@@ -35,6 +35,13 @@ When sending a message, here is a visual diagram of how the messages travels thr
 
 The message workflow initiates with the MU (Messenger Unit), where the message's signature is authenticated. Following this, the SU (Scheduler Unit) allocates an Epoch and Nonce to the message, bundles the message with an Assignment Type, and dispatches it to Arweave. Subsequently, the `aoconnect` library retrieves the outcome from the CU (Compute Unit). The CU then calls for all preceding messages leading up to the current Message Id from the SU (Scheduler Unit), processes them to deduce the result. Upon completion, the computed result is conveyed back to `aoconnect`, which is integrated within client interfaces such as `aos`.
 
+## Ethereum Signed Message
+
+If the Message [ANS-104 DataItem](https://specs.g8way.io/?tx=xwOgX-MmqN5_-Ny_zNu2A8o-PnTGsoRb_3FrtiMAkuw) was signed using Ethereum keys,
+then the value in the `Owner` and `From` fields will be the
+[EIP-55](https://github.com/ethereum/ercs/blob/master/ERCS/erc-55.md) Ethereum address of the signer.
+For example: `0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359`.
+
 ## Summary
 
 Messages serve as the primary data protocol type for the ao network, leveraging ANS-104 Data-Items native to Arweave. Messages contain several fields including data content, origin, target, and cryptographic elements like signatures and nonces. They follow a journey starting at the Messenger Unit (MU), which ensures they are signed, through the Scheduler Unit (SU) that timestamps and sequences them, before being bundled and published to Arweave. The `aoconnect` library then reads the result from the Compute Unit (CU), which processes messages to calculate results and sends responses back through `aoconnect`, utilized by clients such as `aos`. The CU is the execution environment for these processes.

src/concepts/processes.md

@@ -37,6 +37,13 @@ The main functions to look at in this `ao` helper is
 - ao.send(Message) - sends a message to a process
 - ao.spawn(Module, Message) - creates a new process
 
+## Ethereum Signed Process or Module
+
+For an `ao` `Process` or `Module`, if the [ANS-104 DataItem](https://specs.g8way.io/?tx=xwOgX-MmqN5_-Ny_zNu2A8o-PnTGsoRb_3FrtiMAkuw) was signed using Ethereum keys,
+then the value in the `env.Process.Owner` or `env.Module.Owner` field, respectively, will be the
+[EIP-55](https://github.com/ethereum/ercs/blob/master/ERCS/erc-55.md) Ethereum address of the signer.
+For example: `0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359`
+
 ## ao.send Example
 
 ```lua