bitcoin-privacy-stealth
Stealth addresses: ECDH-based derivation generating a unique output per payment. Pre-BIP47 / BIP352, conceptually similar. USE WHEN: understanding the family of stealth-address schemes, comparing with BIP47 / Silent Payments.
What this skill does
# Stealth Addresses
Generic concept of generating a unique receiving address per payment
via Diffie-Hellman key agreement between sender and receiver. Provides
on-chain unlinkability for payments to the same recipient.
## History
- 2014: original stealth-address proposals (Peter Todd, BIP63 draft).
- BIP63 was withdrawn; never widely adopted.
- BIP47 (2014) — concrete reusable payment codes (PayNyms).
- BIP352 (2024) — Silent Payments, the modern Schnorr-based variant.
## Concept
```
Receiver: scan key (s), spend key (b)
public form (S, B)
Sender: per-payment random e
compute: P = B + H(e * S) * G
send to: address(P)
Receiver scans all txs for outputs matching: P = B + H(s * eG) * G
(where eG is the sender's ephemeral pubkey)
knowing s, derive scalar t = H(s * eG)
spend key for output: b + t (mod n)
```
## Compared modern variants
- **BIP47**: uses notification tx + simpler derivation.
- **BIP352 Silent Payments**: stealth address concept refined for
Schnorr, no notification tx.
- **Monero stealth addresses**: same concept native to Monero
(cross-chain inspiration).
## Status
- Generic "stealth address" no longer common term in Bitcoin context.
- Modern Bitcoin equivalents = BIP47 (older) and BIP352 (newer).
## See also
- [bip47-paynyms/SKILL.md](../bip47-paynyms/SKILL.md)
- [silent-payments/SKILL.md](../silent-payments/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'.