bitcoin-privacy-bip47
BIP47 PayNyms — reusable payment codes via notification tx + Diffie-Hellman derivation. See also the wallet-side reference at ../../wallets/payment-codes/. USE WHEN: integrating PayNyms, evaluating against Silent Payments.
What this skill does
# BIP47 PayNyms (privacy view) Privacy-oriented summary; full details in [../../wallets/payment-codes/SKILL.md](../../wallets/payment-codes/SKILL.md). ## Privacy properties - Sender has anonymity-of-1 — server can correlate "X paid Y" via notification tx. - Receiver public address never appears on chain. - Different sender pairs use different derivation chains → no cross-sender correlation. ## Compared to Silent Payments - BIP47 has **notification tx** that leaks the existence of sender ↔ receiver pairs. - Silent Payments has **no notification tx** — better privacy. - BIP47 has **lower scan cost** for receiver. ## Status - Sparrow + Stack Wallet maintain BIP47 support. - Samourai (formerly the dominant BIP47 wallet) shut down 2024. - Adoption in decline as Silent Payments matures. ## See also - [../wallets/payment-codes/SKILL.md](../../wallets/payment-codes/SKILL.md) - [silent-payments/SKILL.md](../silent-payments/SKILL.md) - [stealth/SKILL.md](../stealth/SKILL.md)
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.