什么是 PayLock？

PayLock 为 Openclaw Skills 生态系统内的代理间以及代理与人类之间的商业活动提供了一个强大的框架。通过利用 Solana (SOL)，它允许代理处理复杂的交易，而无需手动基于 Web 的干预或托管中间机构。该技能专注于消除自主财务交互中的摩擦，为服务交付和支付提供安全的桥梁。

PayLock 专为需要其代理雇用其他代理或完成付费任务的开发者而构建，确保每笔交易都有可验证的证据支持。作为 Openclaw Skills 库的一部分，它意味着代理可以使用标准 REST API 调用或基于 Python 的 CLI 工具，以编程方式管理合约的整个生命周期，从初始创建到最终资金释放。

下载入口:https://github.com/openclaw/skills/tree/main/skills/kgnvsk/paylock

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

PayLock 应用场景

• 在提供服务的 AI 代理和客户代理之间实现支付自动化。
• 确保数字资产交付安全，在文件哈希通过验证前锁定资金。
• 为使用 AI 编程助手的开发者实施无须信任的自由职业工作流。
• 通过自动超时释放机制防止数字交易中的“失踪”现象。

1. 代理通过指定付款人、收款人、SOL 金额和工作描述来启动合约。
2. 付款人将所需的 SOL 转移到托管地址，并提供交易哈希以资助合约。
3. 收款人执行工作并提交交付负载以及作为不可变工作证明的 SHA-256 哈希。
4. 付款人审查交付并触发验证端点以向收款人释放资金。
5. 如果付款人在 48 小时内未能验证，系统可以触发自动超时释放以保护收款人。

PayLock 配置指南

要将 PayLock 集成到您的 Openclaw Skills 环境中，请通过环境变量配置您的 API 端点和身份验证令牌：

export PAYLOCK_API_BASE="http://localhost:8767"
export PAYLOCK_PAYER_TOKEN="your-payer-token"
export PAYLOCK_PAYEE_TOKEN="your-payee-token"

确保您拥有 Python 标准库，以便运行 scripts/ 目录中提供的脚本。

PayLock 数据架构与分类体系

PayLock 使用结构化架构管理合约数据和状态转换。以下属性定义了核心合约对象：

name: paylock
description: Non-custodial SOL escrow for AI agent deals. Create, fund, deliver, verify contracts from ch@t. No browser needed.
version: 1.1.0

PayLock — SOL Escrow for AI Agents

Non-custodial escrow infrastructure. Your agent handles deals from ch@t — no websites, no manual steps.

Setup

Set your PayLock API endpoint:

export PAYLOCK_API_BASE="http://localhost:8767"

Agents running their own PayLock instance use localhost. For hosted PayLock, set the URL provided by your PayLock operator.

Authentication: Tokens are passed via environment variables, never CLI arguments:

export PAYLOCK_PAYER_TOKEN="your-payer-token"
export PAYLOCK_PAYEE_TOKEN="your-payee-token"

Fee Structure

Endpoints

Quick Start

Create contract

python3 scripts/paylock.py create r
  --payer "agent-alpha" r
  --payee "agent-beta" r
  --amount 1.25 r
  --currency SOL r
  --description "Build KPI dashboard" r
  --payer-address "PAYER_SOL_WALLET" r
  --payee-address "PAYEE_SOL_WALLET"

Fund contract

python3 scripts/paylock.py fund r
  --contract-id "ctr_123" r
  --tx-hash "5j3...solana_tx_hash"

Deliver work

python3 scripts/paylock.py deliver r
  --id "ctr_123" r
  --delivery-payload "https://example.com/deliverable.zip" r
  --delivery-hash "sha256:abc123..."

Payee token is read from PAYLOCK_PAYEE_TOKEN env var automatically.

Verify delivery

python3 scripts/paylock.py verify --id "ctr_123"

Payer token is read from PAYLOCK_PAYER_TOKEN env var automatically.

Check status / List

python3 scripts/paylock.py status --id "ctr_123"
python3 scripts/paylock.py list

Safety Features

• 48h auto-release: If buyer doesn't verify within 48h, funds release to seller automatically
• Delivery hash: SHA-256 proof of work delivered, immutable once submitted
• HMAC authentication: All sensitive endpoints authenticated via HMAC tokens
• On-chain jury (v2): 3/5 quorum dispute resolution on Solana devnet
• Audit logging: Every action logged with timestamp and agent ID

Architecture

• v1 (Production): REST API, custodial escrow, SOL transfers
• v2 (Devnet): Solana Anchor program, non-custodial PDA escrow
  • Program ID: Dr6fD8fyN4vpBSnVpLC9kMd49g1GSSqFwzDCoGA5CbXp

Agent Workflow

1. Create contract with payer/payee/amount/description
2. Payer transfers SOL and provides tx hash → Fund
3. Seller completes work → Deliver with payload + hash
4. Buyer reviews → Verify → funds released to seller
5. Buyer ghosts? → 48h auto-release protects seller

Scripts

All in scripts/ — pure Python stdlib, no dependencies:

• paylock.py — unified CLI
• paylock_api.py — shared API client
• create_contract.py, fund_contract.py, deliver_contract.py, verify_contract.py, get_contract.py, list_contracts.py

Links

• Landing: https://kgnvsk.github.io/paylock/
• GitHub: https://github.com/kgnvsk/paylock
• ClawHub: https://clawhub.ai/kgnvsk/paylock