bitcoin-privacy-dandelion
Dandelion++ (BIP156): tx broadcast privacy. Stem phase (forward to one peer) → fluff phase (gossip to all). Hides origin IP. USE WHEN: evaluating tx-broadcast privacy, implementing Dandelion- aware relay logic.
What this skill does
# Dandelion++ (BIP156) A tx broadcast privacy enhancement. Without Dandelion, tx broadcast to all your peers immediately = first peer with chain analytics can infer your IP. ## Mechanism Two phases: ### Stem phase (anonymity) When you create a new tx: - With probability p (default 0.9), forward to **one** randomly selected peer (the "stem peer"). - That peer also forwards to one of their peers, with probability p. - The "stem path" continues for ~3-10 hops on average (depends on p). During stem, only the chain of forwarders sees the tx. ### Fluff phase (broadcast) - With probability 1-p, the current stem peer "fluffs" — broadcasts to all its peers normally. - From there, the tx propagates network-wide via standard gossip. ## Privacy benefit - Original sender IP hidden among the stem hop pool. - Chain analyst sees the tx first arrive from a "fluffer", not the origin. - Coordinated chain-analytics nodes have to guess which fluff position was the source. ## Implementation status - BIP156 proposed in 2018. - **Not yet implemented in Bitcoin Core** as of late 2025. - Some niche impls (Dandelion++ in btcd was experimental, removed). ## Why slow adoption - Adds latency to broadcast (10-30 seconds typical). - Requires coordinated stem peers; if attacker controls many peers, can defeat. - Limited measured privacy gain (still some attribution possible via timing). ## Workarounds in production Without Dandelion++, current best practice for broadcast privacy: - **Broadcast over Tor** (`onlynet=onion`) — defeats IP correlation. - **Use a relay service** (mempool.space "submit" via Tor). - **Run your own node** — eliminates third-party attribution. Tor-only setups achieve stronger broadcast privacy than Dandelion++ in practice. ## See also - [tor/SKILL.md](../tor/SKILL.md) - [../../protocol/p2p/SKILL.md](../../protocol/p2p/SKILL.md)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.