agicash-wallet-documentation

Summarize Agicash wallet transaction flows, entities, and state machines.

55|5|Updated Feb 1, 2024
One-click install
npx skills add https://github.com/MakePrisms/agicash --skill agicash-wallet-documentation-makeprisms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agicash-wallet-documentation
Source: https://github.com/MakePrisms/agicash/tree/main/.claude/skills/agicash-wallet-documentation
Command: npx skills add https://github.com/MakePrisms/agicash --skill agicash-wallet-documentation-makeprisms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Documentation that guides developers through Agicash wallet transaction flows, entity models, and state machines to enable safe, consistent implementation across UI and backend.

Core Features & Use Cases

  • Comprehensive overviews of Cashu and Spark send/receive flows, including quotes, swaps, and token handling
  • Detailed references to entity relationships, state transitions, invariants, and required server/client flows for Lightning Address routes
  • Quick-start guidance for onboarding new team members and accelerating feature work in app/features/send/ and app/features/receive/

Quick Start

Review the wallet documentation to understand end-to-end transaction flows, entities, and state machines

Frequently Asked Questions about agicash-wallet-documentation

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

FAQPage Schema
How do Cashu and Spark send and receive flows work in a wallet?

Wallet state machines enforce idempotent transitions, manage keyset counters, and handle encryption to ensure safe transaction flows. The documentation details these core invariants to prevent inconsistent state updates during send and receive operations.

How do I implement Lightning Address routes for wallet transactions?

Wallet entities define the data models and relationships required for transaction processing, such as tokens and quotes. The documentation provides detailed references to these entities to accelerate onboarding and ensure consistent implementation across UI and backend.

What are the core invariants for wallet state machines and transaction transitions?

Wallet state machines enforce idempotent transitions, manage keyset counters, and handle encryption to ensure safe transaction flows. The documentation details these core invariants to prevent inconsistent state updates during send and receive operations.

How do I onboard new developers to a Cashu wallet codebase?

Wallet documentation applies to development tasks touching send and receive flows, token wiring, and Lightning Address routes in both UI and backend. It covers entity definitions, references, and state machines to guide consistent implementation across the application stack.