Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Hijacking Bitcoin

Hijacking Bitcoin

The Hidden History of BTC
Bitcoin's scaling battle was also a fight over who gets to define money without banks.
by Roger Ver 2024 306 pages
4.21
306 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Judge Bitcoin by usable cash, not by its ticker or price.

A design dispute became a split. Roger Ver argues that Bitcoin began as permissionless digital cash: a way to make online payments directly, quickly, and cheaply. In his account, Bitcoin Core, the software behind BTC, changed course between roughly 2014 and 2017. Its restricted transaction capacity made everyday payments costly and unreliable, while the dominant story shifted toward Bitcoin as digital gold, an asset to hold rather than spend. Bitcoin Cash, or BCH, emerged in 2017 as an alternative that kept the larger-block payment model.

The book takes a side. Ver presents BCH as the continuation of Bitcoin’s original purpose and treats the change to BTC as a hijacking. That claim organizes the book, but it is also advocacy from a prominent BCH supporter. The reader’s useful first question is therefore practical: what can each network do, and at what cost?

Analysis

The book’s strongest move is to make a technical argument legible through a familiar test: can ordinary people use the system to pay one another? That shifts attention from charts and slogans to fees, reliability, custody, and access. It also exposes a common category error: a network can succeed as a financial asset while disappointing as payment infrastructure. The caution is that “original purpose” cannot, by itself, settle which present-day design is best. A founder’s intentions are important historical evidence, but users also judge systems by their current performance and tradeoffs.

A currency earns store-of-value status by proving useful in exchange.

Use helps sustain value. Ver draws on Austrian economics to explain that value is subjective: people value goods because they expect them to satisfy wants. Money is useful as a medium of exchange, meaning people accept it to trade for other goods. That broad usefulness also gives them reason to expect it will retain purchasing power. In this view, calling Bitcoin a store of value while dismissing its use for payments puts the conclusion before the evidence.

The origin story matters. Satoshi’s whitepaper describes online payments between parties without a financial intermediary, and Ver points to Satoshi’s discussions of small purchases and micropayments. The book contrasts that vision with a later BTC culture that discourages spending. It acknowledges Bitcoin could gain value for other reasons, but argues that practical exchange is the stronger foundation for money.

Analysis

This argument clarifies that “store of value” is not a physical property like weight. It is a judgment about future demand, and everyday acceptance can support that expectation. The distinction is useful well beyond cryptocurrency: an asset’s usefulness and its exchange value can reinforce one another. Still, the relationship is not a strict one-way sequence. Scarcity, speculation, and expectations can support demand before an asset becomes common in commerce. Ver’s point is most persuasive as a challenge to treating payment utility as irrelevant, not as proof that every useful payment network must become a durable store of value.

Treat block capacity as an economic choice, not a law of physics.

A small cap creates a queue. Bitcoin’s blocksize limit restricts how much transaction data miners can add about every ten minutes. Ver says the original one-megabyte limit was a temporary defense against denial-of-service attacks, not a permanent throughput target. With that limit, BTC processes only a few thousand on-chain transactions per block. When demand exceeds capacity, users compete by offering higher fees, while lower-fee payments wait. During congestion, the book reports fees above $50 and delays stretching to days.

The tradeoff is disputed. Small-block advocates worry that bigger blocks make operating full nodes more expensive. Ver counters with declining storage and bandwidth costs, and notes that nodes can prune old transaction history. He cites an estimate that Visa-level throughput would require blocks around 800 megabytes and roughly 42 terabytes of data per year. His conclusion is that cost is a design tradeoff, not an absolute barrier.

Analysis

The key economic insight is that capacity limits do not merely manage technical load. They allocate scarce space, and therefore determine who can transact, how quickly, and at what price. The housing analogy in the book’s wider argument is apt: restricting supply under rising demand tends to raise prices. Yet digital infrastructure has genuine distributional costs. Larger blocks can favor well-connected operators, and falling storage prices do not make bandwidth, latency, or geographic inequality disappear. The sound question is not whether capacity should be unlimited, but which costs are acceptable and who bears them.

Let people verify their payments without requiring everyone to run a server.

Lightweight use was part of the design. A full node downloads and checks the blockchain’s transaction history and current rules. Simplified Payment Verification, or SPV, lets a lightweight wallet check that its own payment appears in the chain without processing every transaction. Ver argues that Satoshi expected ordinary users to use lightweight wallets, while businesses and specialist operators would run full nodes. This division is familiar elsewhere: most people use email without running their own mail servers.

The node debate reflects competing priorities. Small-block advocates see many independently operated full nodes as protection against rule changes. Ver argues that making every user run one burdens ordinary people without necessarily giving them meaningful power over miners. He also stresses that businesses with substantial economic activity have stronger reasons to validate the network independently.

Analysis

This is a useful distinction between personal verification and maintaining the whole system. Decentralization does not require every participant to perform every task; specialization can make a network usable. But convenience is not the same as independence. A lightweight wallet checks less than a full node, so users must understand what evidence it relies on and which services provide it. The practical design challenge is to preserve a low-friction path for everyday use while keeping robust verification accessible to businesses, researchers, and technically capable users.

Audit who controls upgrades and funding before calling a network decentralized.

Open code still has gatekeepers. Bitcoin software is open source, meaning people can inspect and modify its code. That does not mean their changes enter the version most people use. Maintainers decide which proposals are accepted into a widely used implementation. Ver traces Bitcoin’s leadership from Satoshi to Gavin Andresen and then to Wladimir van der Laan, whose role, in Mike Hearn’s account, became too passive to resolve the scaling dispute. The Bitcoin Foundation, intended to support development, later ran out of money.

Money shapes development. Ver argues that the funding and governance of software are inseparable: developers need income, and funders can create conflicts of interest. He presents Blockstream’s hiring of key developers and its paid sidechain business as a conflict, while treating developer dominance as a systemic risk. His broader lesson is that code, incentives, and decision-making power must be examined together.

Analysis

The book makes a valuable institutional point: decentralization is not a binary property of software. It is distributed across maintainers, miners, exchanges, wallets, businesses, and users, each with different leverage. This resembles a principal-agent problem: people entrusted to maintain infrastructure may develop priorities that diverge from those relying on it. However, the existence of a financial relationship does not establish corrupt intent. The strongest version of Ver’s argument is structural, not conspiratorial: governance needs transparent funding, accountable leadership, and credible alternatives, regardless of anyone’s motives.

A scaling workaround can shift dependence off-chain instead of removing it.

Lightning moves payments into channels. The Lightning Network links payment channels, which let two parties exchange repeated payments off-chain and settle their final balances on Bitcoin’s base layer. To send through someone else’s channel, a payment must find a route with enough available funds at every step. The book argues that opening and closing channels still require on-chain transactions, which become expensive when base-layer space is scarce.

The design has practical demands. Ver highlights the need for channels to stay online, sufficient liquidity, and reliable routing. He argues that these demands encourage hubs and custodial wallets, where companies manage funds for users. He also cites the Lightning whitepaper’s estimate that onboarding billions of people through channels would require blocks far larger than BTC’s current capacity. The book’s conclusion is that channels may suit specialized or frequent small payments, but do not erase the need for a scalable base layer.

Analysis

This section is strongest when it asks who pays the costs that a second layer appears to remove. If users must enter and exit through a congested base layer, the bottleneck remains part of the system’s economics. Payment channels can still be valuable for repeated transactions between parties, much as a specialized transport route can serve a particular corridor. The leap from that usefulness to a universal payment solution deserves scrutiny. Ver emphasizes failure modes, while a fair evaluation also asks how much reliability, liquidity, and ease of use improve in real implementations.

Follow the scaling fight through decisions, not just price charts.

A sequence of failed compromises. Ver frames 2014 to 2017 as Bitcoin’s civil war. In 2015, developers Gavin Andresen and Mike Hearn backed BitcoinXT, an alternative implementation that proposed larger blocks. Ver recounts censorship of discussion, denial-of-service attacks against some supporters, and efforts to discredit the proposal. In 2016, the Hong Kong Agreement promised SegWit and a later two-megabyte increase. A 2017 New York Agreement renewed the plan, but the increase was canceled before it happened.

The exit became Bitcoin Cash. With the SegWit2x proposal abandoned, Bitcoin Cash split from BTC in August 2017, preserving the larger-block approach. Ver presents the conflict as more than a technical disagreement: it involved software leadership, online information control, business interests, and miners’ reluctance to risk disruption. He reads Blockstream’s role as a conflict of interest, though the book cannot establish that every delay or attack had a coordinated motive.

Analysis

The timeline makes governance visible. A technical decision can be delayed not only by engineering uncertainty, but also by veto points, reputation management, and fear of a damaging split. That is an important lesson for any open-source infrastructure project. The reader should also distinguish documented events from interpretations of intent. An agreement’s failure is observable; whether it reflects sabotage, strategic bargaining, or institutional paralysis is harder to prove. Ver’s detailed account is therefore most useful as a case for scrutinizing power, while its partisan framing calls for comparison with other participants’ records.

Forks protect the right to exit, but every split taxes network effects.

A fork is both safeguard and cost. A hard fork changes protocol rules in a way that makes the upgraded software incompatible with older versions. Ver argues that the ability to fork can discipline developers by allowing dissatisfied users, businesses, or miners to leave. Bitcoin Cash itself emerged through such a split. But each fork can divide users, merchants, developers, and the liquidity that gives a monetary network its usefulness.

BCH faced its own governance tests. Bitcoin SV split from Bitcoin Cash in 2018 after disagreements over development direction. In 2020, Bitcoin ABC proposed a permanent share of block rewards for development, ultimately setting out an eight-percent plan. Opponents rallied around Bitcoin Cash Node, and ABC split off as eCash. Ver sees these episodes as disruptive, but also as evidence that a development team can be rejected. He warns that forks should remain a last resort, not a routine substitute for workable governance.

Analysis

The book refuses an easy resolution: exit rights can prevent a closed group from ruling indefinitely, yet repeated exits weaken the coordination that makes money useful. This resembles constitutional design. A credible mechanism for removal can restrain leaders, but making removal too easy can destabilize the institution itself. The BCH disputes sharpen the central question: what rules should govern developer funding before a crisis arrives? Ver’s account favors miner and community resistance, but resistance alone is not a funding model. Stable procedures can matter as much as the ability to rebel.

Measure crypto success by permissionless use, not appreciation alone.

The promised benefit is direct control. Ver argues that digital cash matters because it can let people transact without banks or payment processors deciding who may participate. That benefit weakens when users rely on custodial wallets, accounts controlled by a company, because those providers can monitor or restrict access. In the book’s account, high base-layer fees encourage that dependence. Ver promotes Bitcoin Cash for low-cost payments, but also says no cryptocurrency or development team is immune to capture.

Utility must be tested, not assumed. The conclusion urges readers to judge networks by reliable transactions, fees, and the ability to control their own funds, rather than by token prices or celebrity endorsements. Ver offers a hypothetical example: one billion daily transactions at a one-cent fee would yield about ten million dollars a day for miners. That illustrates a proposed revenue model, not an achieved level of use.

Analysis

This ending offers a practical scorecard: adoption should mean more than an asset changing hands on exchanges. For a payment system, meaningful measures include whether people can transact reliably, retain control of funds, and avoid fees that make small purchases irrational. Those measures also expose tradeoffs that price alone hides. Permissionless access is not automatically private, and self-custody can be difficult for users. The book’s strongest lasting contribution is its insistence that freedom claims be tested against the actual path a payment takes, including the companies and institutions between sender and recipient.

Analysis

Hijacking Bitcoin is best read as an argument about governance told through a technical history. Its central claim is that BTC changed from everyday digital cash to a scarce, high-fee settlement asset because a small group of developers resisted larger blocks. The book supports that account with early writings, public proposals, business decisions, and the author’s own recollections. Its archival detail is valuable, especially where it reconstructs the sequence of proposals, agreements, and failed upgrades. But the evidence does not always carry the full weight of the interpretation placed on it.

Three questions need to remain separate. First, what did Satoshi intend? The whitepaper strongly supports a payment purpose. Second, could the system scale through larger blocks? Ver argues that improving storage and bandwidth made this feasible, but affordability for some operators does not settle the consequences for network concentration or reliability. Third, which design is better today? Historical intent cannot answer that without operational evidence about security, adoption, fees, and user experience.

The book is least conclusive when it infers motive from institutional connections. Blockstream’s business interests and the developers’ decisions are legitimate subjects for scrutiny, but correlation and incentive do not prove a coordinated takeover. Likewise, claims about censorship and attacks are important to the narrative, yet the account is openly written from one side of a bitter dispute. Readers should distinguish reported events from conclusions about why they occurred.

The broader insight is more durable than the title’s accusation: decentralized technology still depends on human institutions. Maintainers, miners, exchanges, wallet providers, and users exercise different forms of power. A fork offers an exit, but also fragments the network it is meant to protect. The book is therefore a useful warning about governance failures and a partisan case for BCH, not a neutral final history or an independent technical audit.

Summary in 30 Seconds
Bitcoin began as a proposal for online payments without financial intermediaries, but BTC's limited block capacity can make transactions costly and slow when demand rises. Larger blocks may increase throughput while also raising the cost of running a full node. Off-chain channels reduce some base-layer traffic but rely on liquidity, routing, and online access. Software maintainers, funders, miners, businesses, and users all hold different forms of influence. Forks offer a way to exit a dispute, but can divide users and liquidity.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.21 out of 5
Average of 306 ratings from Goodreads and Amazon.

Hijacking Bitcoin received mostly positive reviews, with readers praising its informative content and fresh perspective on Bitcoin's history. Many found it eye-opening and thought-provoking, appreciating the author's insights into the cryptocurrency's original purpose and subsequent challenges. Some readers criticized it as one-sided or lacking balance, but overall, reviewers recommended it as essential reading for those interested in understanding Bitcoin's evolution and the forces that shaped it. The book sparked discussions about decentralization, blockchain technology, and the future of digital currencies.

Your rating:
4.61
332 ratings
Want to read the full book?

Glossary

Fundamental Five

Five claims about Bitcoin’s design

Ver’s organizing summary of what he considers Bitcoin’s original design: digital cash for internet payments, low fees, scaling through larger blocks, lightweight access for ordinary users rather than a full node for everyone, and the importance of economic incentives alongside software. The book contrasts these claims with the later Bitcoin Core approach.

Simplified Payment Verification

Lightweight payment checking

A method described in Bitcoin’s design that lets a lightweight client check whether its own transaction is included in the blockchain without downloading and validating the entire transaction history. Ver presents it as a practical way for ordinary users to verify payments without operating a full node.

Full node

Complete blockchain validator

Software that downloads and validates blockchain data and checks transactions against the network’s rules. In Ver’s account, full nodes are valuable for businesses and specialist operators, but requiring every ordinary user to run one would impose unnecessary technical and storage burdens. The book contrasts this role with lightweight wallets using Simplified Payment Verification.

Blocksize limit

Maximum block data allowance

A protocol rule limiting the amount of data that can be included in each block. Since transactions occupy block space, the limit constrains how many on-chain payments can be processed over time. Ver argues that Bitcoin’s original one-megabyte limit was a temporary anti-attack measure, while Bitcoin Core made small capacity a lasting feature.

Zero-confirmation transactions

Payments awaiting a block

Transactions broadcast to the network but not yet included in a mined block. They can be seen within seconds and may support fast retail payments, but they have less security than transactions confirmed in blocks. Ver argues that merchants can manage the associated risk, while changes such as replace-by-fee make conflicting transactions easier to submit.

Replace-by-fee

Higher-fee transaction replacement

A transaction policy that allows a user to broadcast a conflicting transaction with a higher fee, potentially replacing an earlier unconfirmed payment. The book argues that this weakens zero-confirmation payments by making double-spending easier before a transaction is confirmed. Ver presents the feature as part of the broader shift away from instant retail use.

Segregated Witness

Revised transaction structure

A Bitcoin software change that separates certain transaction data from the main transaction structure and changes how block capacity is measured. It was promoted in the scaling dispute as a way to increase effective capacity and support second-layer systems. Ver regards it as more complex than a direct blocksize increase and argues that it did not deliver the capacity promised by the industry agreements.

Lightning Network

Network of off-chain channels

A payment system built from channels between users. Participants exchange payments within channels without recording every transaction on the blockchain, then settle channel balances on-chain. Channels can be linked so payments route through other participants. Ver criticizes the system’s dependence on on-chain setup and settlement, online availability, routing, and liquidity.

Hard fork

Incompatible protocol upgrade

A change to a blockchain’s rules that is not compatible with older software. If some participants adopt the new rules and others do not, they may end up on separate networks. In the book, hard forks are both a way to upgrade Bitcoin and a means for users to exit a development team’s control, though they can divide network effects.

Infrastructure Funding Plan

Proposed miner-funded development

A 2020 Bitcoin Cash proposal to direct a portion of block rewards toward software development. An initial version proposed 12.5 percent for six months; Bitcoin ABC later proposed a different, permanent plan directing eight percent to a designated address. Opposition strengthened support for Bitcoin Cash Node, and the dispute contributed to ABC’s split from the main network.

FAQ

What's Hijacking Bitcoin: The Hidden History of BTC about?

  • Exploration of Bitcoin's Evolution: The book examines Bitcoin's journey from its creation in 2009 to its current state, focusing on changes in its purpose and functionality.
  • Developer Influence: It highlights how a small group of developers shifted Bitcoin's design from a medium of exchange to a speculative asset.
  • Call for Awareness: Roger Ver aims to educate readers on Bitcoin's true history and the implications of its "hijacking," advocating for a return to its original vision as digital cash.

Why should I read Hijacking Bitcoin by Roger Ver?

  • Insightful Perspective: The book offers a unique viewpoint from Roger Ver, a key figure in the cryptocurrency space since Bitcoin's early days.
  • Understanding Bitcoin's Evolution: It provides a comprehensive analysis of the factors that led to Bitcoin's transformation, essential for anyone interested in cryptocurrency.
  • Encourages Critical Thinking: Ver challenges the mainstream narrative, prompting readers to think critically about the future of digital currencies and their governance.

What are the key takeaways of Hijacking Bitcoin?

  • Bitcoin's Original Purpose: The book asserts that Bitcoin was intended to be "digital cash" for everyday transactions, with low fees and fast processing times.
  • Developer Control: It highlights how a small group of developers, particularly those associated with Bitcoin Core, have significantly influenced Bitcoin's trajectory.
  • The Rise of Bitcoin Cash: Ver discusses Bitcoin Cash as a response to limitations imposed by Bitcoin Core, aiming to restore Bitcoin's original vision.

What are the best quotes from Hijacking Bitcoin and what do they mean?

  • "Bitcoin was designed to be digital cash used to make payments over the internet.": This quote emphasizes Bitcoin's intended use as a currency rather than a speculative asset.
  • "The project was taken over by a small group of software developers who redesigned the whole system.": It critiques the influence of developers on Bitcoin's evolution and the resulting consequences.
  • "The original, scalable design of Bitcoin still exists, but it’s not traded on cryptocurrency exchanges under the ticker symbol BTC.": This points to Bitcoin Cash, which Ver argues aligns better with Satoshi Nakamoto's original vision.

How does Hijacking Bitcoin address the concept of decentralization?

  • Critique of Centralization: The book argues that Bitcoin's development has become centralized under a small group of developers, undermining its original decentralized ethos.
  • Developer Influence: Ver emphasizes the significant implications of developer decisions on the network's governance and functionality.
  • Call for True Decentralization: The author advocates for a return to a more decentralized model, where multiple implementations of Bitcoin can coexist and thrive.

What is the significance of Bitcoin Cash in Hijacking Bitcoin?

  • Restoration of Original Vision: Bitcoin Cash is presented as a necessary fork to restore Bitcoin's original purpose as a low-fee, fast transaction system.
  • Response to Limitations: Its creation was a direct response to high fees and slow transaction times resulting from Bitcoin Core's development decisions.
  • Alternative for Users: Ver argues that Bitcoin Cash offers a viable alternative for users seeking a cryptocurrency that functions effectively as digital cash.

What are the main arguments against Bitcoin Core presented in Hijacking Bitcoin?

  • High Fees and Slow Transactions: Ver criticizes Bitcoin Core for creating a system with high fees and slow transaction times, contradicting Bitcoin's original purpose.
  • Resistance to Scaling: The book highlights the refusal of Bitcoin Core developers to increase the block size limit, leading to usability issues.
  • Focus on Speculation: Ver argues that Bitcoin Core has shifted the narrative towards Bitcoin as a "store of value," detracting from its utility as a currency.

How does Hijacking Bitcoin explain the "Bitcoin Civil War"?

  • Conflict Among Developers: The book details intense disagreements among developers regarding Bitcoin's future, particularly around block size and transaction fees.
  • Emergence of Factions: Ver describes how these conflicts led to factions within the community, resulting in the split between Bitcoin and Bitcoin Cash.
  • Impact on Adoption: The Civil War is portrayed as a critical period that hindered Bitcoin's growth and adoption due to community division.

What role does Roger Ver see for Bitcoin in the future according to Hijacking Bitcoin?

  • Advocacy for Digital Cash: Ver envisions Bitcoin fulfilling its original role as a widely accepted digital cash system for everyday transactions.
  • Collaboration Among Projects: He emphasizes the need for collaboration among different cryptocurrency projects to achieve this vision.
  • Hope for Redemption: Despite challenges, Ver expresses hope that Bitcoin can return to its foundational principles.

What is the significance of the block size debate in Hijacking Bitcoin?

  • Core vs. Cash Philosophy: The book details the conflict between Bitcoin Core's small-block philosophy and Bitcoin Cash's big-block approach.
  • Impact on Usability: It argues that the small-block approach has made Bitcoin less usable as a currency, pushing users towards alternatives like Bitcoin Cash.
  • Historical Context: The author provides historical context for the block size debate, illustrating its impact on the cryptocurrency landscape.

How does Hijacking Bitcoin address the concept of developer capture?

  • Centralization of Power: The book discusses how a small group of developers can exert significant control over Bitcoin's code, leading to centralization.
  • Consequences of Capture: It outlines the potential for changes that benefit a few at the expense of the broader community.
  • Call for Vigilance: The author emphasizes the need for the community to remain vigilant against such capture to preserve cryptocurrency integrity.

What are the differences between Bitcoin (BTC) and Bitcoin Cash (BCH) as discussed in Hijacking Bitcoin?

  • Transaction Fees: Bitcoin Cash aims to keep transaction fees low, making it more suitable for everyday transactions compared to Bitcoin.
  • Block Size: BCH supports larger block sizes, allowing more transactions per second, while BTC's 1MB limit constrains its capacity.
  • Philosophical Differences: The two coins represent different philosophies—BTC as a store of value and BCH as a medium of exchange.

About the Author

Roger Ver is a prominent figure in the cryptocurrency world, known as an early investor and advocate for Bitcoin. He later became involved in founding Bitcoin Cash, a fork of the original Bitcoin. Ver's background includes facing legal challenges, including allegations of tax evasion. His book presents his perspective on Bitcoin's history and development, offering insights into the events that led to the split between Bitcoin and Bitcoin Cash. Ver's views are often controversial within the cryptocurrency community, but he remains an influential voice in discussions about digital currencies and their future.

Download PDF

To save this Hijacking Bitcoin summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.46 MB     Pages: 20

Download EPUB

To read this Hijacking Bitcoin summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.48 MB     Pages: 26
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...