List of Flash News about blocksonly mode
Time | Details |
---|---|
2025-09-28 07:18 |
Bitcoin nodes: filters vs blocksonly mode explained with 5 trading implications for BTC fees and liquidity
According to @BitMEXResearch, the post contrasts spam-deterrent relay filters with running blocksonly mode on Bitcoin nodes and asks whether blocksonly would deter all transactions, highlighting how node policy affects propagation and fee dynamics, source: BitMEX Research on X, Sep 28, 2025. In Bitcoin Core, blocksonly mode disables inbound transaction relay from peers while still receiving and validating blocks, and locally created transactions can still be broadcast via other nodes, so it does not stop transactions from being mined network-wide, source: Bitcoin Core documentation. Bitcoin’s standardness and relay filters are designed to reduce spam and DoS risk by not relaying non-standard or too-low-fee transactions, which is a mempool policy layer distinct from blocksonly mode, source: Bitcoin Core policy documentation. For traders, relay policy and filtering primarily affect the fee market and confirmation latency, which change on-chain settlement costs and arbitrage timing for BTC, impacting spreads and execution risk during congestion, source: Bitcoin Core documentation; Kaiko research. Historical episodes of elevated mempool congestion and rising feerates have coincided with more volatile BTC basis and funding as settlement frictions increase, informing risk management for derivatives and spot-perp strategies, source: Glassnode research 2023–2024; Kaiko market reports. Actionably, monitor mempool size, median feerate and average confirmations as leading indicators of short-term BTC liquidity and withdrawal or deposit latency rather than assuming blocksonly adoption suppresses transactions across the network, source: Bitcoin Core documentation; mempool.space data. |
2025-09-02 12:07 |
BTC Network Risk Management: Farside Investors Outlines 4 Bitcoin Node Precautions for Trading Uptime - Firewall, Blocksonly, Upload Cap, Mempool Limits
According to Farside Investors (@FarsideUK), Bitcoin node operators can cut exposure to bandwidth and resource exhaustion by using a firewall, running blocksonly mode, setting a data upload cap, and restricting mempool size, which are practical steps to keep nodes online during high-load events, source: Farside Investors on X. Bitcoin Core documentation explains that -blocksonly disables transaction relay, -maxuploadtarget caps daily outbound bandwidth, and -maxmempool limits memory usage, reducing the risk of node outages during traffic spikes that can disrupt market connectivity, source: Bitcoin Core documentation. Bitcoin Core documentation also indicates that blocksonly mode reduces visibility into unconfirmed transactions, a trade-off trading desks relying on mempool data should evaluate when configuring nodes, source: Bitcoin Core documentation. |