peaq_ros2_examples packages launch files that orchestrate the core services, storage bridge, and helper scripts. Use them to validate your setup or as templates for project-specific launches.
demo_core.launch.py
Launches the core node and events node together:
- Starts
core_nodeandevents_node - Suitable for identity, access, and storage service testing
- Publishes on
peaq/tx_status; the events node does not stream chain events topeaq/events
storage_bridge.launch.py
Included with peaq_ros2_core, this launch is often combined with demo_core to exercise storage flows:
- Subscribes to
peaq/storage/ingest - Publishes
peaq/storage/status - Retries a failed submission twice, five seconds apart
127.0.0.1:5001 and reports gateway URLs on ipfs.io; pass your own config to change either. The bridge also starts with robot.require_did: true: it exits at startup unless peaq_core_node is active and its wallet already has a DID (create it with /peaq_core_node/identity/create), or you set require_did: false under storage_bridge.robot in your config file. To point it at your config file, run the node directly instead:
e2e_test.launch.py
The package also ships e2e_test.launch.py, but it does not run from a clone: its test script is not installed as an executable, the bridge config it loads is not in the repository, and it never activates the core node.
demo_core.launch.py takes network, confirmation_mode, events_enabled, and log_level. Extend them with additional nodes or parameters as needed for your deployment.
Continue with the example scripts to trigger specific blockchain operations.
