Samourai Wallet official account — the project’s public engineering and product voice on privacy features (Whirlpool, Dojo, atomic‑swap work) and policy responses. Important primary source for understanding Samourai’s technical choices and public statements (note: project and founders were the subject of DOJ action in 2024, see linked sources for context). citeturn14search3turn7search3

Adam (nopara73) — Wasabi co‑founder and lead author of much of Wasabi/ WabiSabi research and technical commentary. Primary source for design rationale, technical threads, and research-level discussion about coinjoin and privacy tradeoffs. Follow for direct developer insight. citeturn5search0turn0search3

Liquid Network (Liquid_BTC) is the practical, in‑production Bitcoin sidechain (Elements-based). Its X account shares technical docs, release notes, integrations and real‑world usage metrics — directly relevant for evaluating sidechain tradeoffs and infrastructure decisions. Verified references to the handle and technical announcements. citeturn9search4turn9search5

Samourai developer account (SamouraiDev / TDevD) — developer‑level posts and technical commentary attributed to Samourai engineers (implementation notes, feature previews such as atomic swaps / Whirlpool internals). Valuable for low‑level technical signals and code/feature discussion. citeturn16search4turn16search10

NVK (Co‑founder/CEO of Coinkite) — veteran wallet/hardware developer and frequent technical commentator on wallet design, UTXO management, and privacy‑by‑design tradeoffs. Not a Wasabi/Samourai team member but a high‑signal developer voice on practical privacy, wallet UX, and infrastructure decisions relevant to protocol and deployment. citeturn15search2turn15search4

Official Wasabi Wallet project account — primary channel for announcements, technical posts (coinjoin/WabiSabi development, coordinator changes) and links to Wasabi blog posts. Essential for tracking developer comments and project decisions that affect Bitcoin privacy tooling. citeturn3search0turn0search1

Spiral's official organization account — primary channel for Spiral's grant announcements, progress reports, and technical commentary on Bitcoin/Lightning projects; directly supports the agent goal of following Spiral's technical signals and proposals. Verified on Spiral's site and in media coverage referencing @spiralbtc. citeturn6view0turn2search0

Official corporate account for Blockstream — primary source for company announcements, product releases (Green/Greenlight/Jade/Liquid), and links to engineering/blog posts relevant to Bitcoin protocol and infrastructure discussions. Use this to track high-level technical roadmaps and public statements from Blockstream. citeturn8search5turn3search4

Greenlight (Blockstream’s Lightning-as-a-Service) account — useful for operational announcements, API/Greenlight release notes, and developer-focused updates that affect Lightning integrations and enterprise deployments. Tracks practical infra changes that matter to protocol participation and infrastructure decisions. citeturn6search2turn13search2

Jeremy Rubin (author of BIP‑119 / CheckTemplateVerify and other covenant-related BIP work) is an active BIP proposer and researcher — his X account and personal site publish primary proposals, security analyses, and BIP drafts useful for technical policy and upgrade debate. citeturn14search9turn17view3

Jonas Nick (handle n1ckler) is a Blockstream cryptography researcher and co-author of BIPs including Schnorr/Taproot and MuSig2; his X presence and Blockstream posts provide primary author insights into cryptographic BIP design and reference implementations. citeturn11search9turn9search1turn17view2

Tadge Dryja (tdryja) — co‑author of the original Lightning whitepaper and long‑running researcher (MIT DCI / Utreexo, Lightning Labs alumnus); primary source for protocol design rationale, historic context and research‑grade proposals. Follow for high‑level protocol changes and research threads. citeturn9search0turn9search1

Olaoluwa “roasbeef” Osuntokun — CTO / lead LND engineer who publishes code, release signatures and technical commentary about LND, MPP/Blinded Paths, releases and protocol work; primary source for LND implementation decisions and developer-level detail. citeturn1search6turn0search5

Christian Decker (Snyke) — lead Core Lightning / Blockstream Lightning engineer and researcher who contributes to BOLTs, CLN/Greenlight and protocol research; frequently appears in technical talks/podcasts and posts developer‑level insights on X. Good source for spec discussions and CLN engineering tradeoffs. citeturn7search3turn7search8

Core Lightning (official) — the official account for the Core Lightning implementation (formerly c-lightning). It posts release notes, dev updates, and implementation‑level discussion from CLN contributors (useful to track engineering changes, plugin work, and BOLT‑level features). Primary org account aggregating engineer announcements. citeturn10search1turn10search5

Paul “Rusty” Russell (@rusty_twit) — long‑time Lightning protocol engineer and major author/maintainer of Core Lightning (formerly c-lightning) and a primary spec contributor (BOLT author). His X account is a first‑hand source for spec proposals, CLN dev commentary and protocol design discussion. citeturn1search12turn10search3

Marco Falke (@MarcoFalke) — long‑time prolific Bitcoin Core contributor and former maintainer who led testing, QA and release-review efforts; his X posts and linked threads often contain test results, review rationale and security/QA analysis relevant to protocol stability. citeturn14search3turn14search10

Luke Dashjr (@LukeDashjr) — early Bitcoin Core developer who posts on protocol-level issues, mempool/relay policy, and consensus-relevant vulnerabilities; useful for spotting edge-case attacks, policy discussions and low-level design tradeoffs. citeturn8search4