bitcoin is built around a simple but critical design choice: on average, a new block is added to its blockchain roughly every 10 minutes. This “10‑minute block time” is more than just a technical parameter; it shapes how the network reaches consensus, how quickly transactions are confirmed, and how secure the system is against attacks. In bitcoin’s decentralized architecture, thousands of nodes maintain a shared, append‑only ledger of transactions-known as the blockchain-without relying on any central authority . Miners compete to bundle pending transactions into blocks and solve a computational puzzle; the first to succeed propagates their block to the network, extending the chain.
This article explains why bitcoin’s creator chose a 10‑minute target, how the protocol uses difficulty adjustments to keep block production near that interval despite fluctuating computing power, and what this means in practice for confirmation speeds, fees, and network security. By understanding the rationale and mechanics behind bitcoin’s block time, investors, developers, and everyday users can better interpret price movements, transaction delays, and the broader behavior of the bitcoin ecosystem as tracked by real‑time market and network data .
Origins and Rationale Behind Bitcoins 10 Minute Block Interval
Satoshi Nakamoto’s choice of a roughly ten-minute interval between blocks was not arbitrary; it emerged from balancing network reliability with usability. In the early days, when bitcoin nodes were few and globally dispersed, longer intervals gave transactions enough time to propagate across the network before the next block was mined, reducing the probability of competing chains and orphaned blocks.A shorter interval woudl have flooded this fledgling peer-to-peer system with frequent block races, while a much longer one would have made confirmation times impractical for everyday use, even as bitcoin evolved into a highly traded digital asset tracked in real time on major platforms.
The 10-minute target also reflects a intentional compromise between security and user experience. Every new block represents a fresh layer of proof-of-work,and waiting for several blocks considerably decreases the chance of double-spend attacks. Satoshi assumed that moast users and merchants could tolerate a few minutes of latency in exchange for strong settlement finality. In practice, this design underpins how exchanges and payment processors structure their confirmation policies, for example requiring a certain number of block confirmations before crediting deposits or allowing withdrawals, aligning commercial risk management with bitcoin’s underlying probabilistic security model.
From a broader systems outlook, the 10-minute cadence helps smooth out the randomness of mining while still allowing a steady stream of transaction inclusion. It supports predictable monetary issuance-new bitcoins entering circulation at a statistically stable rate-while making it easier for infrastructure providers, such as wallet services and trading platforms, to synchronize with the network and update balances. Key design trade-offs can be summarized as:
- Propagation vs. speed – Enough time for global propagation, without making confirmations excessively slow.
- Security vs. convenience – Strong probabilistic finality after several blocks, at the cost of short-term waiting.
- stability vs. variability – A stable issuance schedule despite the inherently random nature of mining.
| Design Goal | Impact of ~10 Minutes |
|---|---|
| Network Sync | Allows global node propagation before next block |
| Security | Reduces double-spend probability with each new block |
| User Experience | Confirms payments within a practical timeframe |
| Monetary Policy | Supports predictable issuance and halving schedule |
How block Time Influences Network Security and Attack Resistance
bitcoin’s roughly 10‑minute interval between blocks acts as a built‑in safety buffer for the network. By spacing out block creation, the protocol gives nodes time to propagate new blocks globally and agree on a single, canonical history of transactions. This reduces the chance of temporary forks where two valid blocks compete,a situation that can be exploited by attackers trying to double‑spend. in other words, longer block intervals raise the coordination window for honest nodes to reach consensus, making it more costly for an attacker to outpace the rest of the network with a secret chain.
From a security perspective, every additional block added after a transaction is like another lock on a vault door. A transaction with 1 confirmation is far easier to reverse than one buried under 6 or more blocks, because an attacker would need to reorganize a longer segment of the chain. This dynamic is closely tied to the 10‑minute rhythm: confirmations accumulate at a predictable pace, helping merchants and services choose appropriate security thresholds. Typical practices include:
- Low‑value payments: Frequently enough accepted after 1-2 confirmations.
- Medium‑value payments: Commonly require 3-6 confirmations.
- high‑value settlements: May wait for 6+ confirmations or use additional safeguards.
| Confirmations | Approx. Time | Security Level |
|---|---|---|
| 0 | Instant | Very low |
| 1-2 | 10-20 mins | Basic |
| 3-6 | 30-60 mins | Strong |
| 6+ | 60+ mins | High/Final‑like |
Attack resistance also depends on how block time interacts with network latency and the distribution of mining power. very short block times increase the rate of orphaned blocks and give well‑connected miners an edge, which can centralize mining and weaken security over time. at around 10 minutes, bitcoin strikes a trade‑off between responsiveness and robustness: blocks are not so frequent that the chain becomes unstable, yet not so infrequent that confirmations are unusably slow for most economic activity.This balance helps preserve a broad, geographically distributed mining ecosystem, raising the cost of a 51% attack and reinforcing the network’s long‑term resilience.
Impacts of 10 Minute Confirmation Delays on Everyday User Experience
The average 10-minute interval between bitcoin blocks means that everyday users often feel a gap between initiating a payment and having it treated as final on the network. Each block bundles recent transactions into the public ledger, known as the blockchain, and onc a transaction is included in a block and buried under subsequent blocks, it becomes increasingly difficult to reverse . For routine users, this architecture translates into a noticeable waiting period whenever a merchant or exchange requires at least one on-chain confirmation before releasing goods, services, or withdrawal rights.
In practice, people experience these delays differently depending on context and risk tolerance. For small, low-risk payments, such as a coffee or a micro-donation, some merchants may accept “zero-confirmation” transactions, trusting the network’s peer-to-peer relay and their own fraud checks . However, higher-value activities-like funding an exchange account or paying an invoice for professional services-tend to require one or more confirmations, each adding roughly another 10 minutes of expected wait time . This shapes user expectations around bitcoin as a settlement system rather than an instant point-of-sale replacement. Common user perceptions include:
- Perceived slowness compared with card networks and mobile wallets.
- Heightened anxiety during market volatility while waiting for funds to clear.
- More deliberate spending behavior, as each confirmed transaction feels weightier and harder to reverse.
To navigate these trade-offs, many services layer user experience improvements on top of the base protocol. Wallets and exchanges may display real-time status indicators, fee recommendations, or estimated confirmation times so users can decide whether to pay higher fees for faster inclusion in the next block. Payment flows often combine on-chain settlement with faster off-chain mechanisms, shifting the 10-minute delay to the background. The table below summarizes how different everyday scenarios typically interact with bitcoin’s confirmation dynamics:
| Use Case | Typical Confirmation Need | User experience |
|---|---|---|
| Coffee purchase | 0-1 confirmation | Near-instant if merchant accepts risk |
| Exchange deposit | 2-6 confirmations | Wait from ~20 to 60+ minutes |
| High-value payment | 6+ confirmations | Used more like bank settlement |
Transaction Finality How Many Confirmations Are Really Safe
In bitcoin, a transaction is never mathematically “final,” but it becomes increasingly impractical to reverse as more blocks are mined on top of it. Each confirmation represents your transaction being buried one block deeper in the blockchain, making any attempt to reorganize history exponentially more expensive. This escalating security is rooted in the proof-of-work model: an attacker would need to outpace the combined hash power of honest miners to rewrite the chain, a task that becomes prohibitively costly after just a handful of blocks in most real-world threat models.
The number of confirmations you should wait for depends on the value at risk, your risk tolerance, and the economic incentives of a potential attacker. For everyday users, bitcoin’s convention of 6 confirmations (about an hour) is often treated as a practical benchmark for very high-value transfers, while smaller amounts commonly settle with fewer. In practice, different use cases may adopt distinct policies, such as:
- low-value retail – 0-1 confirmations, often relying on additional risk checks.
- Medium-value payments – 1-3 confirmations as a balanced compromise.
- High-value or institutional transfers – 6+ confirmations for stronger assurance.
- Critical, one-off settlements – custom thresholds aligned with internal risk models.
| Confirmations | Approx. Time | Typical Use Case | Risk Level |
|---|---|---|---|
| 0 | < 10 minutes | Small in-person payments | High (double-spend possible) |
| 1-2 | 10-20 minutes | Online purchases, small exchanges | Moderate |
| 3-6 | 30-60 minutes | Standard exchange deposits, B2B | Low |
| 6+ | > 60 minutes | Large settlements, treasury moves | Very low (economically costly to attack) |
Fee Markets and Mempool Dynamics Under a 10 Minute Block Schedule
Every 10 minutes, miners get a fresh prospect to clear the backlog of pending transactions sitting in the mempool, the shared waiting room where users broadcast their payments before they are included in a block. Because space in each block is limited, a competitive fee market emerges: users attach fees to their transactions, and miners rationally prioritize those that pay the most per byte. When overall network activity spikes, the mempool thickens and the minimum fee required for fast confirmation rises, sometimes sharply, untill a series of higher-fee blocks gradually bring the backlog down.
This dynamic creates a constantly shifting balance between cost and speed. Users typically choose from a blend of fee strategies such as:
- High-fee, fast confirmation – favored during volatile price moves or time-sensitive trades.
- Moderate-fee, flexible timing – suitable for routine transfers where a delay of several blocks is acceptable.
- Low-fee, patient settlement – used for non-urgent value transfers that can wait through multiple 10-minute intervals.
As each new block can only include a finite number of transactions, these choices collectively shape the fee distribution in the mempool and influence how quickly it drains after periods of congestion.
| Mempool State | Typical Fee Level | Expected Confirmation |
|---|---|---|
| Low congestion | Low to medium | 1-3 blocks |
| Normal traffic | Medium | 3-6 blocks |
| High congestion | Medium to high | 6+ blocks |
Under a fixed 10-minute target, these states can persist for hours or resolve quickly, depending on the incoming transaction rate relative to the throughput of mined blocks. Over longer horizons, this cadence helps define bitcoin as a scarce blockspace market rather than a simple payment rail, with fee patterns and mempool depth reflecting broader adoption and usage trends across the network .
Comparing Bitcoins Block Time to Other Cryptocurrencies Tradeoffs and Lessons
bitcoin’s ~10-minute block interval is often contrasted with other cryptocurrencies that target far shorter confirmation times, sometimes aiming for seconds instead of minutes. While faster blocks may seem strictly better, they typically introduce tradeoffs in areas such as network propagation, orphan (stale) block rates, and overall security assumptions.bitcoin’s design intentionally prioritizes settlement finality and global decentralization over raw speed,aligning with its role as a base-layer,censorship-resistant money and settlement network rather than a high-frequency payments rail . This conservative cadence is one reason bitcoin remains a reference point for digital scarcity and long-term value storage .
| Network | Typical Block Time | Design Emphasis |
|---|---|---|
| bitcoin | ~10 minutes | security & decentralization |
| Faster chains | Seconds-1 minute | Throughput & UX |
| Layer-2 on bitcoin | Instant-seconds | Payments & scalability |
When comparing these designs, the key lesson is that no block time is “free”; every choice shifts weight between competing priorities.Shorter intervals can improve user experience for small, everyday transactions but often at the cost of higher bandwidth requirements, more frequent reorgs, and a higher operational burden on full nodes, which can subtly favor larger, more centralized operators. bitcoin’s slower rhythm, supported by its proof-of-work consensus mechanism and globally distributed node network , demonstrates that base-layer security can be deliberately conservative while speed is pushed into upper layers. Consequently, developers and investors often treat bitcoin as the benchmark for robust settlement, with alternative chains experimenting further out on the spectrum of speed and complexity . Ultimately, the ecosystem’s experience suggests that a secure, slower base layer combined with scalable off-chain or secondary solutions may offer a more durable path than simply chasing ever-faster block times.
Practical Strategies to Transact safely and Efficiently Within 10 Minute Blocks
Because new blocks are only added to the bitcoin blockchain roughly every 10 minutes, it is essential to align your transaction habits with this rhythm to reduce risk and delays. Start by matching confirmation requirements to the value and urgency of the payment: for small everyday purchases, many users accept 0-1 confirmation, while larger transfers typically wait for 3-6 confirmations as additional blocks make the transaction increasingly difficult to reverse on the distributed ledger that all nodes share.To avoid overpaying when the network is calm, use wallets that suggest dynamic fees based on current mempool conditions; when activity spikes-frequently enough following sharp price moves in the BTC/USD market-consider sending non-urgent transactions during off-peak hours to catch cheaper, less congested blocks.
Efficient use of each block also comes from optimizing how you construct transactions.Consolidate many small, unspent outputs into a single address when fees are low so that future payments consume fewer inputs and occupy less space in a block, improving your odds of timely inclusion. Prefer SegWit and native SegWit (bech32) addresses where possible, as they reduce the weight of your transaction and can lower the fee required to be competitive.You can further streamline your activity by batching multiple outgoing payments into a single transaction, which uses fewer bytes minimizing your per-recipient cost while still fitting neatly into the 10-minute confirmation rhythm.
For users who transact frequently or for businesses that depend on predictable settlement, combining on-chain discipline with higher-layer tools can make block intervals feel almost invisible. payment channels and other Layer 2 solutions are designed to route many small payments off-chain while still ultimately settling on the bitcoin base layer, allowing rapid, low-cost transfers that only occasionally touch the 10-minute cycle. Consider the following swift-reference overview:
| Goal | On-Chain Tactic | Timing Tip |
|---|---|---|
| Low fee | Use dynamic fees, SegWit | Send during low network activity |
| Fast confirmation | Increase sat/vByte | Target next 1-2 blocks |
| Business payouts | Batch many recipients | Schedule at predictable times |
| Frequent small payments | Use Layer 2 channels | Settle to chain periodically |
Best Practices for Businesses integrating bitcoin With 10 minute Settlement Cycles
To make effective use of bitcoin’s ~10-minute confirmation rhythm, businesses should first align their operational workflows with the settlement cadence of the blockchain ledger, where each block records and validates new transactions in a decentralized manner. This means defining clear internal policies on how many confirmations are required before goods are shipped, services are activated, or balances are credited to customer accounts. For low-value or low-risk payments, many merchants accept a single on-chain confirmation, while higher-value transactions often warrant multiple confirmations to reduce settlement risk on the open, peer-to-peer network. Embedding these thresholds in your payment gateway, CRM, and accounting tools ensures that staff follow consistent, auditable rules without manual intervention.
Risk management should be built directly into your bitcoin payment flow,using the settlement window as an opportunity for automated checks rather than viewing it as a delay. Practical safeguards include:
- Tiered confirmation policies based on ticket size, customer history, and chargeback exposure.
- Dynamic pricing that updates bitcoin-denominated amounts against live fiat markets to offset volatility.
- Address whitelisting for recurring B2B partners to streamline approvals.
- Transaction monitoring to flag unusually large or rapid payments for extra review during the settlement window.
By treating the 10-minute interval as a built-in fraud and compliance buffer, organizations can integrate bitcoin into existing treasury, risk, and reconciliation processes with fewer surprises.
| Use Case | Confirmations Target | Operational Practice |
|---|---|---|
| In-store retail | 0-1 | Accept with risk cap; auto-lock price at checkout |
| E-commerce | 1-3 | pick & pack after 1 confirmation; ship after 3 |
| High-value B2B | 3-6 | Trigger delivery or credit only after full clearance |
Combining such confirmation targets with clear settlement SLAs, automated alerts for delayed blocks, and transparent customer messaging about expected confirmation times helps businesses turn bitcoin’s probabilistic 10-minute settlement into a predictable component of daily operations within a decentralized payment environment.
Future Outlook Potential Protocol changes and layer Two Solutions to Mitigate Delay
Looking ahead, most discussions about changing bitcoin’s base-layer confirmation speed revolve around careful, conservative modifications that preserve its core security model. Because the 10‑minute interval is hard‑coded into consensus rules and tightly linked to network difficulty and issuance, any reduction would demand global agreement and a coordinated upgrade across the decentralized node network that maintains the blockchain ledger. Proposed ideas include shorter block intervals with adjusted difficulty algorithms, dynamic block timers responsive to network conditions, or enhanced propagation mechanisms to reduce orphaned blocks and keep the network stable.These concepts remain largely theoretical, as the community tends to prioritize robustness, censorship resistance and predictability over raw speed.
Instead of overhauling the base layer, developers increasingly focus on off‑chain and second‑layer architectures that can offer near‑instant settlement while ultimately relying on bitcoin’s security. Prominent solutions include:
- Lightning Network – bi‑directional payment channels enabling high‑speed, low‑fee microtransactions, later settled on‑chain.
- Sidechains and rollup‑style systems – separate chains pegged to BTC, where faster block times or different rules can be experimented with without impacting the main network.
- Payment batching and channel factories – techniques that aggregate many payments into fewer on‑chain transactions to reduce perceived waiting times.
These approaches preserve bitcoin’s ~10‑minute settlement cycle at the base layer while delivering user experiences that closely resemble real‑time payments on the surface.
| Solution | Speed | Trust Model |
|---|---|---|
| Base‑layer bitcoin | ~10 min per block | Fully decentralized |
| Lightning Network | Seconds or less | Channels anchored to bitcoin |
| Sidechains | Variable, often faster | Federated or separate validators |
Over time, incremental protocol enhancements-such as more efficient transaction formats, better fee estimation, and improvements in node software-are expected to complement these layers and reduce practical delays without abandoning the conservative 10‑minute design that has underpinned bitcoin’s security and monetary reliability since inception.
Q&A
Q: What does “bitcoin’s 10-minute block time” mean?
A: bitcoin’s 10-minute block time is the target average time it takes the network to add a new block of transactions to the blockchain. Miners compete to find a valid block, and on average, one is found roughly every 10 minutes. This interval is built into bitcoin’s protocol and is central to how the system reaches consensus and issues new coins over time.
Q: Why did Satoshi Nakamoto choose a 10-minute target rather of something faster?
A: The 10-minute target is a design compromise between speed and security:
- Slower blocks (e.g., 10 minutes rather of a few seconds) reduce the number of competing blocks (forks) propagating through the network simultaneously occurring.
- Fewer forks make it easier for nodes to agree on a single canonical chain, improving consensus reliability.
- A moderate interval also allows blocks to propagate globally before the next one is likely found, which is important for a decentralized network with varying connection speeds.
In short, 10 minutes is meant to be slow enough to keep consensus stable yet fast enough to be usable for everyday transactions.
Q: Is the block time always exactly 10 minutes?
A: No. Ten minutes is an average target, not a guarantee. Because mining is a probabilistic process:
- Some blocks may be found within a few seconds of the previous block.
- Others can take 20 minutes or more.
Over many blocks, the time per block tends to average out around 10 minutes because of the difficulty adjustment mechanism.
Q: How does the network maintain this 10-minute average? (Difficulty adjustment)
A: bitcoin automatically adjusts the “difficulty” of mining approximately every 2,016 blocks (about two weeks at 10 minutes per block):
- The network measures how long it took to mine the last 2,016 blocks.
- If blocks came too quickly (e.g.,under 10 minutes on average),it increases difficulty.
- If they came too slowly,it decreases difficulty.
This adjustment keeps the average block interval around 10 minutes,even as the total mining power (hash rate) of the network changes over time.
Q: How does 10-minute block time affect bitcoin transaction confirmations?
A: A “confirmation” occurs each time a new block is added after the block that contains your transaction:
- When your transaction first gets included in a block: 1 confirmation.
- After one more block is mined: 2 confirmations, and so on.
Because blocks come on average every 10 minutes:
- 1 confirmation ≈ 10 minutes (on average)
- 3 confirmations ≈ 30 minutes
- 6 confirmations ≈ 60 minutes
for high-value on-chain payments, 3-6 confirmations are commonly recommended. The 10-minute interval therefore directly determines how quickly a transaction is considered deeply settled on-chain.
Q: Why do many services require multiple confirmations?
A: Multiple confirmations reduce the risk of a transaction being reversed by a competing chain (a reorganization):
- With 0 confirmations (unconfirmed), a transaction is only in the “mempool” and can be replaced or dropped.
- With 1 confirmation, it’s in the longest chain but still relatively easy to reverse if a longer competing chain appears.
- Each additional block added on top makes a reorg exponentially less likely and more costly to execute.
Because of this, exchanges and merchants often wait a set number of confirmations-commonly 3 to 6-before considering a payment final.
Q: Does the 10-minute block time limit how many transactions bitcoin can process?
A: Yes, indirectly. bitcoin’s throughput depends on:
- Block size / weight limits (how many transactions fit in a block)
- block interval (how frequently enough new blocks arrive)
Given the current protocol rules, the approximate maximum on-chain throughput remains a few transactions per second, constrained by both block capacity and the 10-minute average interval.
Q: Why not just shorten the block time to scale bitcoin?
A: Shortening block time would increase capacity somewhat, but it would also introduce trade-offs:
- More frequent blocks → higher probability of temporary forks as different parts of the network see different “latest” blocks.
- More forks → more wasted work,weaker security per block,and greater centralization pressure,since better-connected miners gain an advantage.
- Network propagation limits → global nodes may struggle to stay synchronized if blocks arrive too quickly and are large.
As bitcoin prioritizes security, decentralization, and reliable consensus, simply reducing block time is not seen as a safe scaling solution. Instead, scaling is pursued via efficiency improvements and off-chain/Layer 2 solutions.
Q: How does the 10-minute block time relate to bitcoin’s supply schedule?
A: New bitcoins are issued as the block subsidy in each block. Because blocks arrive roughly every 10 minutes:
- Approximately 6 blocks per hour, ~144 blocks per day, ~52,560 blocks per year.
- “Halving” events (when the block subsidy is cut in half) are scheduled every 210,000 blocks, which is about every 4 years at 10 minutes per block.
Thus, the 10-minute target underpins the predictable pace at which new bitcoins come into circulation and the timing of halving events.
Q: What happens to market activity during long or short block intervals?
A: When a block takes significantly longer than 10 minutes to be found:
- The mempool (backlog of pending transactions) can grow.
- Users may raise fees to get included in the next block.
When several blocks are found quickly in succession:
- The mempool can temporarily clear faster.
- Fees may fall if there is spare block space.
On large exchanges and price-tracking platforms, you can see how on-chain congestion and confirmation times can correlate with trading activity and market volatility.
Q: Does a 10-minute block time mean I always have to wait 10 minutes to use bitcoin?
A: Not necessarily:
- Many low-value or trusted-relationship payments may be accepted with 0 or 1 confirmation, especially in everyday contexts.
- layer 2 solutions (such as the Lightning Network) enable near-instant transactions that ultimately settle back to the main chain.
- Some wallets and services provide risk-based policies to accept payments faster, depending on the amount and threat model.
The 10-minute interval governs final settlement on the base layer, but user experience can be much faster.
Q: Can bitcoin’s 10-minute block time be changed by the community?
A: In theory, yes-but it would require a network-wide protocol change (a hard fork or complex consensus change) and broad agreement among node operators, miners, and users. given the deep impact on:
- Security and reorg risk
- Supply schedule and halving timing
- Economic assumptions built into infrastructure
there is strong resistance to altering this basic parameter. Stability and predictability of core rules are considered critical to bitcoin’s value proposition.
Q: How does bitcoin’s 10-minute block time compare to other cryptocurrencies?
A: many other cryptocurrencies use shorter block times:
- Some aim for blocks every 1-2 minutes or even every few seconds.
These designs typically prioritize throughput and perceived speed over bitcoin’s conservative consensus parameters, and they accept a higher rate of forks and other trade-offs. The different choices reflect distinct design goals and risk profiles across networks.
Q: Where can I monitor current bitcoin network activity and block intervals?
A: You can observe:
- Recent block times
- Current transaction fees
- Market price and volume
on block explorers and market data sites. For example:
- bitcoin.com provides general information and educational resources on bitcoin and blockchain usage.
- Crypto data aggregators like CoinGecko show real-time price, market cap, and activity trends for BTC.
- Financial portals like Yahoo Finance track BTC-USD price history and news, which often correlate with network usage peaks.
Together, these tools offer context on how the protocol’s 10-minute block rhythm interacts with real-world trading and usage.
Insights and Conclusions
bitcoin’s 10‑minute block time is not an arbitrary quirk, but a deliberate trade-off between speed, security, and network stability.By targeting a block roughly every ten minutes, the protocol reduces the likelihood of competing chains, helps keep transaction finality predictable, and allows difficulty adjustments to respond smoothly to changes in mining power.Understanding this timing also clarifies why bitcoin confirmations take the time they do, why transaction fees fluctuate with congestion, and how scaling solutions-such as batching transactions or using second-layer networks-aim to improve user experience without altering bitcoin’s core consensus rules.
as you follow bitcoin’s market behavior on platforms like Coinbase, Yahoo Finance, or Google Finance, keeping the 10‑minute block interval in mind provides useful context for understanding confirmation times, fee dynamics, and the broader design philosophy that prioritizes robustness over raw speed.
![Bitcoin [btc]: cme group posts losses in q1 of 2019 as bitcoin [btc] futures plan continue unhindered](https://ohiobitcoin.com/storage/2019/05/npwN5U.jpg "Bitcoin [btc]: cme group posts losses in q1 of 2019 as bitcoin [btc] futures plan continue unhindered")