stellar-escrow-timelock – skill Khác cho agent AI

Stellar Escrow and Timelock Architecture

What it is: Provides an auditable framework for conditional asset locking, timelock boundary verifications, and multi-signature release triggers on Stellar.

Overview

Provides a standardized, auditable framework and data model for Stellar Escrow and Timelock Architecture operations across distributed engineering and decentralized application systems.

When to Use This Skill

• When formalizing architectural contracts, security invariants, or operational limits for Stellar Escrow and Timelock Architecture.
• When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
• When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.

How It Works

1. Define the parameters, thresholds, and identity bindings required for the target operational register.

2. Select appropriate boundary enforcement values from validated enum select sets.

3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.

Verification procedure

First choose the actual mechanism: classic claimable-balance predicates, preauthorized transactions/multisig or a deployed Soroban contract have different release/refund behavior. Record network, full asset issuer/contract ID, escrow identity and exact amount units. Define who may deposit/release/refund/arbitrate in each state and which ledger timestamp/bounds apply. Test before/at/after unlock, competing release/refund, double settlement, missing signer and asset trustline/authorization failures. A 14-day clawback field creates no protocol grace period; issuer clawback rights depend on actual asset flags/implementation. Verify deposited funds and final settlement transaction evidence separately; this register neither locks funds nor grants signing authority.

Field Reference

| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |

|---|------------|------|----------|------------------|----------------------|---------------|

| 1 | Escrow Agreement ID | id | VARCHAR(64) PRIMARY KEY | string | Text | ESC-001 |

| 2 | Depositor Account | text | VARCHAR(56) | string | Text | GDEP... |

| 3 | Beneficiary Account | text | VARCHAR(56) | string | Text | GBEN... |

| 4 | Arbitrator Account | text | VARCHAR(56) | string | Text | GARB... |

| 5 | Locked Asset Code | text | VARCHAR(12) | string | Text | USDC |

| 6 | Locked Principal Amount | currency | NUMERIC(24,7) | number | Number | 15000.0000000 |

| 7 | Unlock Timestamp Epoch | number | BIGINT | number | Number | 1790800000 |

| 8 | Dispute Resolution Pathway | select | VARCHAR(64) | string | Select | 2-of-3 Multi-Sig |

| 9 | Clawback Grace Period Days | number | INTEGER | number | Number | 14 |

| 10 | Settlement Status | select | VARCHAR(32) | string | Select | Locked in Escrow |

| 11 | Creation Date | date | DATE | string, format: date | Date | 2026-10-01 |

Select Options

Dispute Resolution Pathway

2-of-3 Multi-Sig | Automated Time Expiry | Arbitrator Sole Ruling

Settlement Status

Pending Deposit | Locked in Escrow | In Dispute | Released | Refunded

Relations

• Audit Reference -> links to the formal review documentation or test repository.
• Target Architecture -> links to the deployed contract or autonomous agent runtime component.

Examples

Prompt

How do I configure and track Stellar Escrow and Timelock Architecture for our production environment?

Recommended Next Step

> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.

>

> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.

Best Practices

• Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
• Re-run validation test suites on every state-altering commit or parameter change.
• Keep example data synthetic and isolated from production cryptographic keys or private endpoints.

Limitations

• Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
• Requires network connectivity and valid RPC credentials when querying on-chain states.

Security & Safety Notes

• All parameters declare risk: safe. No unauthorized state modification or privileged credential access is performed.
• Use synthetic dummy keys and mock addresses in test suites and local verification scripts.

Common Pitfalls

• Problem: Mismatched decimal precision between contract runtime and database register.

Solution: Always verify decimals using the explicit field mapping in this reference.

• Problem: Missing authorization checks prior to state update.

Solution: Cross-validate against the Security Audit register before deployment.

Related Skills

• @stellar-anchor-integration - covers SEP-10 and SEP-24 anchor compliance flows.
• @soroban-contract-audit - provides the security checklist and vulnerability categorization.
• @cross-chain-relayer-audit - covers message hashes, nonces and quorum proofs.

Reusable Prompt

I want to establish a verified Stellar Escrow and Timelock Architecture register for our production protocol.
Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.