nla-fulfill
Fulfill an existing NLA escrow and collect tokens. Use when the user wants to submit fulfillment text for an on-chain escrow, check arbitration results, and collect approved funds. Covers the full fulfill-arbitrate-collect lifecycle.
- License 许可
- MIT
- 最近更新
- 2026-06-10
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- nla-fulfill
- metadata
- { "author": "arkhai", "version": "1.0" }
- description
- Fulfill an existing NLA escrow and collect tokens. Use when the user wants to submit fulfillment text for an on-chain escrow, check arbitration results, and collect approved funds. Covers the full fulfill-arbitrate-collect lifecycle.
- allowed-tools
- Bash(nla:*) Read
- compatibility
- Requires nla CLI installed (npm install -g nla). Requires a funded Ethereum wallet and access to an EVM chain.
03 SKILL.md 正文
Fulfill NLA Escrow
Help the user fulfill an on-chain escrow by submitting text that satisfies the escrow's demand, then collect the tokens if approved.
Step-by-step instructions
1. Understand the escrow
Get the escrow UID from the user, then check what it demands:
nla escrow:status --escrow-uid <uid>
This shows:
- The demand text
- Arbitration model and provider
- Oracle address
- Any existing fulfillments and their arbitration status
2. Craft the fulfillment
Help the user write fulfillment text that satisfies the demand:
- Read the demand carefully
- The fulfillment text is what the AI arbitrator evaluates against the demand
- Be specific and directly address what the demand asks for
- The default arbitration prompt evaluates whether the "fulfillment" satisfies the "demand" and returns true/false
3. Submit the fulfillment
nla escrow:fulfill \
--escrow-uid <escrow_uid> \
--fulfillment "<fulfillment text>" \
--oracle <oracle_address>
This runs a multi-step on-chain commit-reveal flow:
- Computes a commitment hash
- Submits the commitment with a bond
- Waits for next block confirmation
- Reveals the fulfillment obligation
- Reclaims the bond
- Requests arbitration from the oracle
The command outputs a fulfillment UID - record this for collection.
4. Monitor arbitration
Check if the oracle has made a decision:
nla escrow:status --escrow-uid <escrow_uid>
The oracle typically responds within seconds if it's running. Look for "APPROVED" or "REJECTED" in the output.
5. Collect tokens (if approved)
Once the oracle approves:
nla escrow:collect \
--escrow-uid <escrow_uid> \
--fulfillment-uid <fulfillment_uid>
This transfers the escrowed tokens to the fulfiller.
Key details
- The fulfillment text is permanently recorded on-chain
- The commit-reveal process requires gas for multiple transactions
- If rejected, the tokens stay in escrow - another fulfillment attempt can be made by anyone
- The oracle address must match what was specified when the escrow was created (visible in status output)
- Collection only succeeds after the oracle records an approval
Prerequisites
nlaCLI installed and configured- Private key set via
nla wallet:set,--private-keyflag, orPRIVATE_KEYenv var - ETH in the fulfiller's account for gas
- The oracle must be running (or use the public demo on Sepolia)
Example full flow
# 1. Check what the escrow demands
nla escrow:status --escrow-uid 0xabc123...
# 2. Submit fulfillment
nla escrow:fulfill \
--escrow-uid 0xabc123... \
--fulfillment "The sky appears blue due to Rayleigh scattering" \
--oracle 0x70997970C51812dc3A010C7d01b50e0d17dc79C8
# 3. Check arbitration result
nla escrow:status --escrow-uid 0xabc123...
# 4. Collect if approved
nla escrow:collect \
--escrow-uid 0xabc123... \
--fulfillment-uid 0xdef456...
04 同仓库更多 Skills
youtube-content
YouTube transcripts to summaries, threads, blogs.
xurl
X/Twitter via xurl CLI: post, search, DM, media, v2 API.
touchdesigner-mcp
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
teams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.