skills.rest
zama-ai
zama-aiOFFICIAL
Explore all skills by this author →
Website𝕏@zamaGitHub

fhe-payment-unwrap

Burn confidential cUSDC and finalize unwrap to plain USDC via KMS decryption.

Updated Aug 27, 2026
Search Tags:#kms#unwrap#USDC#openclaw#confidential#cUSDC
One-click install
npx skills add https://github.com/zama-ai/confidential-agentic-payment-stack --skill fhe-payment-unwrap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fhe-payment-unwrap
Source: https://github.com/zama-ai/confidential-agentic-payment-stack/tree/main/claude-code-plugin/skills/fhe-payment-unwrap
Command: npx skills add https://github.com/zama-ai/confidential-agentic-payment-stack --skill fhe-payment-unwrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the two-stage unwrap of confidential cUSDC back into plain USDC using Zama's KMS gateway. It handles both the unwrap and finalize-unwrap commands, enabling users to reclaim their underlying USDC after burning.

Core Features & Use Cases

  • Two-stage unwrap workflow: burn cUSDC and request decryption, then finalize with a proof or KMS response.
  • Handles auto-finalize when KMS is ready and supports a manual resume with a burnHandle.
  • Includes a robust retry and escalation strategy for slow KMS responses and stub mode fallback.

Quick Start

Unwrap 2 cUSDC to reclaim plain USDC using the unwrap command.

Frequently Asked Questions about fhe-payment-unwrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I unwrap confidential cUSDC back to plain USDC?▼

Unwrapping confidential cUSDC to plain USDC requires a two-stage workflow using Zama's KMS gateway. You first burn the cUSDC tokens to request decryption, then finalize the unwrap once the KMS provides the decryption proof or response.

What happens if the KMS is slow during the cUSDC unwrap process?▼

If the KMS is slow during the cUSDC unwrap process, the workflow supports a manual resume using a burnHandle. It also includes a retry and escalation strategy with a stub mode fallback to handle delayed responses.

Can I resume an interrupted cUSDC unwrap finalization later?▼

Yes, you can resume an interrupted cUSDC unwrap finalization later using a burnHandle. This allows you to manually complete the token recovery and reclaim your underlying USDC after the KMS finishes processing.

Does the cUSDC unwrap workflow support auto-finalization?▼

Yes, the cUSDC unwrap workflow supports auto-finalize when the KMS is ready. It handles the finalize-unwrap command automatically to reclaim your underlying USDC without requiring a manual resume.

When do I need to unwrap cUSDC for agentic payments?▼

You need to unwrap cUSDC for agentic payments during on-chain-to-off-chain reconciliation and confidential token recovery. This workflow converts burned wrapped tokens back into plain USDC using KMS decryption.

Related Skills

Explore More Software Engineering Skills→
b-open-iob-open-io
7

wallet-encrypt-decrypt

Encrypt and decrypt messages using BSV keys and ECDH.

Official
Advanced
AetherCore-DevAetherCore-Dev
9

buy

Pay for API calls on Solana with USDC via the x402 protocol.

Official
Advanced
l3wil3wi
11

circle-cctp

Implement Circle CCTP to bridge USDC across chains with attestation and finality.

Community
Advanced
devrelaicomdevrelaicom
37

core-concepts:protocols

Explain Midnight's Kachina and Zswap protocols for private smart contracts and shielded token transfers.

Official
Advanced