# Message type terminology

The architecture proposes components that communicate with each other by passing messages.

This document organizes the message types and gives them names.

## Components
### Daemon
- self-daemon
- counterparty-daemon

### Chain syncer
- syncer a
- syncer b

### Client
- client-cli

## Components interactions
### Intra-daemon
loopback messages

### Inter-daemon
price agreement messages
protocol messages

### Daemon -> Syncer a or b
job messages

### Syncer a or b to Daemon
event messages

### Client -> Daemon
instruction message

### Daemon -> Client
enabled-instruction message

## Message terminology table

| to/from | Self-Daemon | Client | Syncer | Counterparty-Daemon |
|---------------------|---------------------|-------------|----------|---------------------|
| Self-Daemon | loopback | instruction | event | protocol |
| Client | enabled-instruction | x | x | x |
| Syncer | job | x | x | x |
| Counterparty-Daemon | protocol | x | x | x |

x denotes no communication between components