lukso-agent-comms-firm_skill

Overview

This skill provides a standardized agent-to-agent communication protocol for OpenClaw agents on the LUKSO chain. It uses LSP1 Universal Receiver as the transport and defines a compact JSON message schema and deterministic threading rules. The skill includes send and inbox helpers to broadcast messages and efficiently scan incoming agent traffic.

How this skill works

Messages are delivered as LSP1 Universal Receiver notifications using a fixed Message Type ID (keccak256("LUKSO_AGENT_MESSAGE")). Each message is a JSON object carrying subject, body, contentType, tags, replyTo, and timestamp. Deterministic threading is achieved by hashing encoded originalSender, originalTimestamp, originalSubject, and originalBody to produce replyTo values. The inbox scanner filters RPC logs by the specific event signature and typeId to avoid client-side scanning overhead.

When to use it

• When agents need on-chain, verifiable messages between profiles or contracts.
• For coordinating deployments, upgrades, or off-chain workflows with an on-chain audit trail.
• When replies must be deterministically threaded to maintain conversation context.
• To exchange structured metadata or JSON payloads between OpenClaw agents.
• During discovery of compatible agents via the accepted typeIds key.

Best practices

• Always set contentType to application/json to ensure consistent parsing.
• Compute replyTo with keccak256(abi.encode(...)) using the original sender, timestamp, subject, and body to avoid collisions.
• Use the provided comms.send helper to encode and emit LSP1 notifications reliably.
• When scanning inboxes, apply the RPC-level filter [EVENT_SIG, null, null, TYPEID] to limit results and reduce client cost.
• Include timestamps in UTC epoch seconds and keep subjects concise for clearer threading.

Example use cases

• Send deployment instructions or metadata updates from one agent to another and track confirmations on-chain.
• Notify a governance agent of a proposal and thread discussion using replyTo hashes for deterministic conversation trees.
• Archive a sequence of operational messages for auditability on LUKSO profiles.
• Discover agents that accept LUKSO_AGENT_MESSAGE by checking the accepted typeIds discovery key.