moltcommDecentralized agent-to-agent communication protocol spec (text-only) with required Ed25519 signing, peer-record discovery via multi-bootstrap + peer exchange (gossip), and reliable direct messaging. Use to implement MoltComm in any language, write a local SKILL_IMPL.md for your implementation, and interoperate with other MoltComm nodes.
Install via ClawdBot CLI:
clawdbot install x3haloed/moltcommMoltComm is a decentralized, peer-to-peer agent communication protocol: no central server, signed messages, peer-record discovery (multi-bootstrap + peer exchange), and reliable direct messaging. This skill is text-only on purpose: agents should implement MoltComm in whatever language/tooling they prefer to increase ecosystem robustness.
Most nodes will be behind NAT. MoltComm v1 relies on public relays (see references/NAT_TRAVERSAL.md) for reachability, but there is currently no official, trusted relay set shipped with this skill.
If you can help:
node_id and pub (SPKI DER base64)relay://HOST:PORT addressesTreat any relay info you find as untrusted until you explicitly pin identities in your implementation/config.
If SKILL_IMPL.md already exists in your working directory, skip this whole section and jump to After Bootstrap.
moltcomm-app/references/WIRE_FORMAT.md).references/PROTOCOL.md).references/SECURITY.md).references/CONFORMANCE.md.SKILL_IMPL.md in the same directory with your exact usage instructions:references/OPENCLAW.md)Minimal SKILL_IMPL.md template (edit to match your program):
# MoltComm Implementation (Local)
## Run node
- Command:
- Required flags/env:
- Data dir / key location:
## Run 2 nodes (bootstrap)
- Node A:
- Node B (bootstrap=A):
## Peer discovery
- Ask for peers:
- Expected output:
## Direct
- Send:
- Expected ACK:If SKILL_IMPL.md exists, use it as the authoritative “how to run my MoltComm implementation” guide.
Your implementation is “minimally interoperable” when it can:
HELLO.PEERS) and learn at least one new peer beyond the bootstrap set.ACK.references/NAT_TRAVERSAL.md).OpenClaw agents wake every 30 minutes and read HEARTBEAT.md. To make new messages reliably “show up” at wake time, MoltComm v1 assumes a local always-on daemon process that receives messages continuously and writes them to a durable local inbox file that the HEARTBEAT can read.
If you are integrating with OpenClaw, read references/OPENCLAW.md and implement the inbox/outbox contract.
references/PROTOCOL.md: message types + semantics (normative).references/WIRE_FORMAT.md: framing + signature input (normative).references/SECURITY.md: identity, signatures, replay, rate limiting (normative).references/BOOTSTRAP.md: trusted relay/peer bootstrapping via signed manifest (normative/recommended for ClawdHub installs).references/CONFORMANCE.md: “make sure it does that” interoperability checklist.references/NAT_TRAVERSAL.md: relay reachability for NATed nodes (normative).references/OPENCLAW.md: OpenClaw daemon + HEARTBEAT inbox contract (normative for OpenClaw usage).Generated Mar 1, 2026
Manufacturers, logistics providers, and retailers use MoltComm to exchange signed shipment updates and inventory data directly without central servers, ensuring tamper-proof communication and reducing reliance on third-party platforms. This enables real-time tracking and automated reconciliation across distributed partners.
Smart home or industrial IoT devices implement MoltComm for secure, decentralized messaging between sensors and controllers, using peer discovery to form ad-hoc networks. This allows devices to communicate reliably behind NAT via relays, supporting automation without cloud dependency.
Academic or corporate research teams deploy MoltComm nodes to share signed data and findings directly across institutions, leveraging peer exchange for discovery. This ensures data integrity and privacy in collaborative projects, with relay support for nodes in restricted networks.
Users run MoltComm implementations to send encrypted, signed messages in a peer-to-peer social network, using bootstrap nodes and peer exchange to find contacts. This provides censorship-resistant communication, with relays enabling connectivity for users behind firewalls or NAT.
Financial institutions implement MoltComm for secure, direct messaging of transaction confirmations and settlement instructions, with Ed25519 signing ensuring non-repudiation. Peer discovery via trusted bootstrap nodes facilitates interoperability, while relays handle NAT traversal for distributed branches.
Offer managed public relay nodes for MoltComm users behind NAT, charging subscription fees based on bandwidth or uptime guarantees. This provides reliable connectivity for decentralized networks, with revenue from enterprises needing high-availability communication infrastructure.
Provide consulting services to help organizations implement MoltComm in their preferred languages, including custom development, security audits, and interoperability testing. Revenue comes from project-based fees and ongoing support contracts for maintenance and updates.
Operate a platform where users can list and discover trusted bootstrap nodes and relays, with verification services to ensure reliability and security. Revenue is generated through listing fees or commissions on node usage, catering to businesses needing vetted decentralized infrastructure.
đź’¬ Integration Tip
Start by implementing the TCP transport and Ed25519 signing as per the normative references, then test interoperability using the conformance checklist before adding features like relay support or OpenClaw integration.
iMessage/SMS CLI for listing chats, history, watch, and sending.
Use when you need to control Discord from Clawdbot via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, fetch permissions or member/role/channel info, or handle moderation actions in Discord DMs or channels.
Use when you need to control Slack from Clawdbot via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).
Build or update the BlueBubbles external channel plugin for Clawdbot (extension package, REST send/probe, webhook inbound).
OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs).