Event Streams

Transaction status and event topics in the peaq ROS 2 workspace.

Blockchain event streaming is not implemented: events_node starts with core.launch.py but does not forward chain events, so peaq/events carries only messages that other ROS nodes publish to it.

Topics

Topic	Type	Description
peaq/tx_status	peaq_ros2_interfaces/msg/TxStatus	Transaction lifecycle updates (PENDING)
peaq/events	peaq_ros2_interfaces/msg/Event	Messages published by other ROS nodes (no chain events)

Monitor Transactions

ros2 topic echo /peaq/tx_status

Each message carries phase, tx_hash, block, and error. The message comments describe PENDING, IN_BLOCK, FINALIZED, FAILED, and DROPPED as phase strings (phase is a plain string), but the core node publishes PENDING only; use peaq/storage/status for the outcome of storage writes.

Subscribe to Events

ros2 topic echo /peaq/events --qos-reliability reliable

Each message carries source, type, and payload_json, filled in by the node that publishes it.

Integrate with Autonomy Stacks

• Use peaq/storage/status to trigger ROS actions, for example starting a follow-up task once a storage write reports its transaction hash.

Pair this with the Messaging Index and Verifiable Storage to cover every messaging pathway.