piqrypt-openclaw-integration
Standard: AISS v2.0 · Full stack: piqrypt.com
Verifiable AI Agent Memory_Cryptographic audit trail for OpenClaw autonomous agents.
Every reasoning step, tool execution (bash, Python, file ops), and task result — signed, hash-chained, tamper-proof.
pip install piqrypt-openclaw
The problem
OpenClaw has OS-level access — it can run bash, write files, execute Python. When an autonomous agent has this much power, you need to know exactly what it did and when. PiQrypt makes every action cryptographically irrefutable.
Quickstart
from openclaw import Agent
from piqrypt_openclaw import AuditableOpenClaw
# Wrap your existing OpenClaw agent
base_agent = Agent(config)
agent = AuditableOpenClaw(base_agent, identity_file="openclaw.json")
# Execute tasks — every step is stamped automatically
result = agent.execute_task(task)
# Export tamper-proof audit trail
agent.export_audit("openclaw-audit.json")
# $ piqrypt verify openclaw-audit.json
Granular tool stamping
# Stamp each tool call individually for full traceability
agent = AuditableOpenClaw(base_agent, identity_file="openclaw.json")
# After planning
prev = agent.stamp_reasoning(task.description, plan, model="llama-3.2")
# After each tool call
prev = agent.stamp_tool_call("bash", "ls -la /reports", output, prev)
prev = agent.stamp_tool_call("python", analysis_code, result, prev)
prev = agent.stamp_tool_call("file_write", "report.pdf", "written", prev)
Security monitoring
# Detect suspicious bash patterns (rm -rf, curl | bash, etc.)
suspicious = agent.get_suspicious_events()
for event in suspicious:
print(f"⚠️ Suspicious action stamped:")
print(f" Tool: {event['payload']['tool']}")
print(f" Hash: {event['payload']['input_hash'][:16]}...")
print(f" Timestamp: {event['timestamp']}")
Suspicious patterns are stamped and flagged, not blocked — the audit trail proves what happened.
Decorator pattern
from piqrypt_openclaw import stamp_action
@stamp_action("file_analysis", identity_file="my-agent.json")
def analyze_sales_data(path: str) -> dict:
return your_analysis_logic(path)
@stamp_action("report_generation", identity_file="my-agent.json")
def generate_report(data: dict) -> str:
return your_report_logic(data)
What gets stamped
| Event | When |
|---|---|
agent_initialized |
Agent creation |
task_start |
Before task execution |
task_reasoning |
After LLM planning phase |
tool_execution |
Each tool call (bash, Python, file ops) |
task_complete |
After task finishes |
task_failed |
On exception (with error hash) |
All events are Ed25519-signed, SHA-256 hash-chained.
Raw commands and outputs are never stored — only their SHA-256 hashes.
Verify
piqrypt verify openclaw-audit.json
# ✅ Chain integrity verified — 24 events, 0 forks
piqrypt search --type tool_execution --limit 10
# Lists last 10 tool calls with timestamps
Full integration guide
→ docs/OPENCLAW_INTEGRATION.md
Links
- PiQrypt core: github.com/piqrypt/piqrypt
- Issues: github.com/piqrypt/piqrypt/issues
- Support: piqrypt@gmail.com
Metadata
Release files for piqrypt-openclaw-integration 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| piqrypt_openclaw_integration-1.1.0.tar.gz | 3.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| piqrypt_openclaw_integration-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.3 kB
Release files / piqrypt_openclaw_integration-1.1.0.tar.gz
| Download URL | piqrypt_openclaw_integration-1.1.0.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa4b5fd30c10fefc05eda00ca3203cf89d5777d4cac777e168f831868e157e4e
|
|
BLAKE2b-256 checksum How to use checksums |
7e9e41f1f4a4c935ffd41d1cdbda86b0fad40036a9802707f780091b537c4c4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 19, 2026.
Transparency logRelease files / piqrypt_openclaw_integration-1.1.0-py3-none-any.whl
| Download URL | piqrypt_openclaw_integration-1.1.0-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c831168ca39ed5c6fde3b9f3a19b20215ee52e74264cb83078014fd5ff59c58e
|
|
BLAKE2b-256 checksum How to use checksums |
f9e6578fa4446678c565f1e3c41a640df41af68f03853e981bbc5cf9be45d4e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 19, 2026.
Transparency log