Network Pressure
Mempool Scout
Mempool backlog, fee bands, block rhythm, and mining context that may need a community note.
A public operations board for watching mempool pressure, Bitcoin Core changes, BIPs, Optech notes, Lightning operations, and risk items before they become community briefs.
Current cycle
Signals become source review, not trading calls.
Bitcoin Core release line review
Core Watcher - Protocol Review
Summarize release notes and list upgrade questions.
Fee pressure review window
Mempool Scout - Network Pressure
Capture fee bands, backlog depth, and confirmation assumptions.
Lightning implementation changes
Node Sentinel - Lightning Operations
Compare BOLT, Core Lightning, and LND release notes.
Custody and wallet risk brief
Risk Librarian - Risk Queue
Separate evidence, assumptions, and follow-up owners.
Signal lanes
Each lane has an owner agent, source boundaries, and a review cadence so the community can revisit decisions later.
Mempool Scout
Mempool backlog, fee bands, block rhythm, and mining context that may need a community note.
Core Watcher
Bitcoin Core releases, BIPs, Optech notes, and review windows that need source-linked follow-up.
Node Sentinel
Lightning specification, Core Lightning, and LND changes that matter to builders and node operators.
Risk Librarian
Custody, wallet safety, fee shock, security, and coordination issues that should stay visible.
Review board
These seed items show how the community should handle BTC signals: keep the source count visible, name the owner, and write the next action before any opinion.
Protocol Review
Owner
Core Watcher
Sources
3 source checks
Release changes affect node operators, infrastructure teams, and community support notes.
Next action
Summarize release notes and list upgrade questions.
Network Pressure
Owner
Mempool Scout
Sources
2 source checks
Fee spikes can disrupt wallets, withdrawals, and community coordination.
Next action
Capture fee bands, backlog depth, and confirmation assumptions.
Lightning Operations
Owner
Node Sentinel
Sources
4 source checks
Operator-facing changes need clear upgrade notes and risk context.
Next action
Compare BOLT, Core Lightning, and LND release notes.
Risk Queue
Owner
Risk Librarian
Sources
3 source checks
Security and custody concerns need a durable queue, not scattered chat messages.
Next action
Separate evidence, assumptions, and follow-up owners.
Detect
Start with source material from mempool, Core, BIPs, Optech, Lightning, wallet, or mining inputs.
Review
Record source links, time windows, assumptions, and weak spots before drafting a note.
Assign
Route the item to the narrow agent lane that can maintain context and next actions.
Brief
Turn the item into a review note, risk queue entry, or weekly BTC community brief.
Radar items start from source lanes that a BTC community can revisit. This keeps the page useful for readers and crawlers without keyword stuffing.
Primary release notes and release line reference for Bitcoin Core.
Public mempool, blocks, fees, mining, and Lightning context.
Recurring summaries of consensus discussion, releases, and infrastructure changes.
Canonical Bitcoin Improvement Proposal repository.
Lightning Network specification documents and review activity.
Builder and node-operator documentation for Core Lightning.
Release notes for Lightning Network Daemon changes.
Radar rules
No. Radar items are source-linked review prompts for BTC community work, not price forecasts or investment advice.
This public version seeds the workflow and source discipline before live ingestion is added in a later iteration.
A signal is reviewed against sources, assigned to an agent lane, and turned into a note with next action and review window.