How jacobcreech/anchor-escrow-2024 works
Project type and purpose
• This is a Solana smart-contract (on-chain program) built with the Anchor framework (“anchor-escrow”).
• It implements an escrow service: makers lock Token A in a PDA vault and takers deposit Token B; once a threshold is met, tokens swap or maker can refund.
Main components
a. Off-chain clients
• Maker wallet (Signer)
• Taker wallet (Signer)
• Anchor CLI / JS test harness (tests/anchor-escrow.ts)
• Migration script (migrations/deploy.ts)
b. On-chain program & accounts
• Anchor Escrow Program (programs/anchor-escrow)
• Escrow state account (PDA)
• Vault token account (PDA)
• Maker ATA_A (associated token account for Token A)
• Maker ATA_B (for Token B)
• Taker ATA_A, Taker ATA_B
c. External Solana system programs
• System Program (account creation, funding)
• SPL Token Program (transfer_checked, close_account)
• Associated Token Program (init_if_needed, ATA creation)
Relationships & data flows
• Deployment: Migration script → Anchor Program → Solana Cluster
• Initialization (“Make”): Maker wallet → Anchor Program →
• create escrow PDA (Escrow state)
• create vault PDA (holds Token A)
• transfer Token A from Maker ATA_A → Vault PDA
• Refund (“Refund”): Maker wallet → Anchor Program →
• transfer all Token A from Vault PDA → Maker ATA_A
• close Vault PDA (lamports returned to maker)
• close Escrow state account
• Take (“Take”): Taker wallet → Anchor Program →
• transfer “receive” amount of Token B from Taker ATA_B → Maker ATA_B
• transfer all Token A from Vault PDA → Taker ATA_A
• close Vault PDA & Escrow state account
Architectural patterns & design principles
• PDA-based accounts for Escrow state & Vault (deterministic addresses via seeds: “escrow” + maker pubkey + seed)
• Anchor’s Account Contexts (Make, Refund, Take) separating concerns per instruction
• CPI calls to Token Program & AssociatedToken Program for token transfers and account closures
• Strong typing of accounts via Anchor’s InterfaceAccount and Account<…> generics