EMP v1.0 Developer Specification

EMP turns a message into a verifiable blockchain/state-machine event. ECMTP remains the internal implementation engine; EMP is the public protocol standard.

Core Definition

RTC = delivery pipe
EMP = verifiable message protocol
Enumium = pulse/state anchor
EBV = final state/value commitment

E1 → E4 Event Model

Layer	Name	Purpose
E1	Pulse	Time anchor and temporal proof
E2	Event	Message payload, hash, sender/receiver context
E3	Value Layer	Optional economic weight, token/coin fee, payment attachment
E4	State Validation	Node/state confirmation and EBV readiness

Message Limits

Type	Limit	Use
standard	2,048 chars	Chat, commands, normal messages
extended	8,192 chars	Notes, structured payloads
hard limit	16,384 chars	Failsafe rejection limit
large payload	Offloaded	Files, documents, media using file_ref/hash

EMP Packet

{
  "protocol": "EMP",
  "version": "1.0",
  "sender_uid": "usr_sender",
  "recipient_uids": ["usr_receiver"],
  "message_type": "text",
  "message_tier": "standard",
  "payload": {
    "body": "Hello from EMP."
  },
  "chain": {
    "anchor_required": true,
    "validation_required": true,
    "economic_weight": 0
  }
}

API Alias Layer

EMP Endpoint	Internal Engine
`POST /api/emp/send-message.php`	`/api/enum-message-create.php`
`POST /api/emp/message-payment.php`	`/api/enum-message-payment.php`
`GET /api/emp/search-message.php`	`/api/enum-message-search.php`
`POST /api/emp/access-message.php`	`/api/enum-message-access.php`
`POST /api/emp/revoke-message.php`	`/api/enum-message-revoke.php`
`GET /api/emp/receipts.php`	`/api/enum-message-receipts.php`

Developer Rule

Never place private message body directly on public chain.
Always hash payload before anchoring.
EMP is the truth layer; RTC/WebSocket may be the delivery pipe.
A message may carry economic weight, but must still remain independently verifiable.