A book that spends twelve chapters building a case and then stops is asking you to trust it.
This chapter exists so that it is not doing that. Everything the previous chapters argued is true as far as I can verify it, and none of it changes the fact that Epic Cash has serious problems. They are listed here in order of how much they should worry you, with the numbers attached, and with what would have to happen for each one to stop being a problem.
One: almost nobody uses it The scorecard's empty box, in numbers.
Epic's market capitalization was about fifteen million dollars at the time of writing, against roughly nineteen million coins in circulation. Zcash is around twenty-one billion. Monero is around eleven billion. The entire category is small; Epic is a rounding error inside it.
Market cap is not usage, so here is usage. Merchant acceptance is thin and concentrated — a handful of businesses, some community projects, a payment processor integration or two. Exchange listings are few: NonKYC is the deepest market, with a small presence elsewhere. There is no published count of nodes, only observations from more than 130 countries, which measures reach rather than adoption.
This is the one attribute on the list that no design can fix, and it is the one that matters most. Money that nobody accepts is not yet money. It is a design that has not been adopted, which is a different thing from a design that has failed — but the difference is only visible in hindsight, and no chapter can settle it for you.
What would change it: one integration that matters. A payment processor, a marketplace, a merchant with real volume. Adoption is not a smooth curve; it is a series of doors, and Epic has not walked through the first one.
Two: the liquidity is shallow enough to hurt This one is not theoretical, and I have the order books.
On the EPIC/USDT market, the best ask has held around four coins — about three dollars — with a spread near half a percent. On EPIC/XMR, the best ask has been around six coins, roughly five dollars, at a similar spread. A buyer wanting a thousand dollars of Epic is not buying a thousand dollars of Epic at the quoted price; they are walking up the book and paying progressively more.
That cuts both ways. A seller of size gets less than the screen says, and anyone who needs to exit quickly pays for the privilege. The thinness also makes the price easy to move, which means the quoted market cap is a softer number than it looks.
What would change it: market makers. Depth is a business decision by someone with capital and an incentive, and until there is one, every buyer and seller is trading against a shallow book.
Three: there is no consolidated audit This is the claim I would not let into the book without qualification, and I want to be precise about what is and is not true.
Epic's cryptography does not come from nowhere. The Mimblewimble design, the Bulletproof range proofs and the secp256k1-zkp libraries have been examined publicly, repeatedly, across the projects that share them. That inheritance is real and checkable.
What does not exist, as far as I have been able to establish, is a single consolidated third-party audit of the Epic protocol — a named firm, a date, a scope, and a public report that a skeptic can read. A marketing sheet in circulation refers to eight independent audits of the building blocks. I have not been able to locate the list, and a book that printed the number without one would be doing the thing this book has criticised in every other project.
What would change it: the list. Firm, date, scope, link. If it exists, it belongs in an appendix with citations, and the sentence becomes the strongest in the book. If it does not, the honest formulation is the one above: reviewed lineage, no consolidated audit.
Four: the tools are behind the design The design is elegant. The software is improving and is not yet easy.
The interactivity requirement — the handshake between two wallets — is the structural cost of having no addresses, and it shows up as friction everywhere: onboarding, receiving a first payment, running a shop, integrating with an exchange. The relay solves the worst of it, at the cost of a dependency that has to be running.
The mobile wallet is a light wallet, which means it trusts a node. The desktop wallet is not a full node either, though it can run one — optional, a setting you turn on, never the default. Turn it on and the wallet verifies rather than trusts, at the price described in chapter twelve: a slow first run, and a peer that comes and goes with the lid. Neither is a bank app, and comparing them to one is the fastest way to lose a non-technical user.
What would change it: time and users. Tooling improves when there are enough people hitting the rough edges to justify the work. This is the same chicken-and-egg that adoption has, wearing a different hat.
Five: there is no company, which cuts both ways There is no Epic company and no marketing budget, and no one to call. A declining levy does fund development — the foundation output the consensus code pays out — and it ends on schedule.
That is the design, and chapter nine argued it is a feature. It is also the reason development moves at the speed of volunteer effort, the reason exchange integrations happen slowly, and the reason a journalist looking for a spokesperson finds a Telegram group instead of a press office.
The bootstrap levy that funded early development ends in December 2027. After that, the protocol has no funding mechanism at all. Whether the ecosystem can sustain itself on donations, grants and commercial self-interest is an open question, and nobody should pretend otherwise.
What would change it: sustained independent funding of the kind other projects get from a foundation or a company — without reintroducing the capture that a foundation brings. Nobody has solved this.
Six: access can disappear, and has for others Privacy coins have been delisted by exchanges in several jurisdictions, and the regulatory direction of travel is not friendly. Epic is a small asset with thin listings; if two of its venues decide the compliance cost is not worth it, the asset becomes much harder to buy and sell.
This is not a flaw in Epic's design. It is a fact about the environment every privacy coin operates in, and it belongs in the honest column because a reader planning to hold this asset should know that the on-ramp is the fragile part.
In November 2026 the Treasury's FinCEN did exactly that to MEXC Global — not by banning a coin, but by ordering every U.S. financial institution to refuse funds moving to or from that exchange, under section 9714. The stated grounds were sanctions evasion and money laundering, and no privacy coin was needed to justify the order. That is the lever worth understanding: the asset is rarely the target, the on-ramp is. A venue that cannot touch a dollar cannot easily be used to buy anything with one, and if your coins are sitting on that venue when the order lands, someone else's conduct has reached your balance. The defense is not a better coin. It is holding your own keys, so that the only person who can lose your money is you.
What would change it: nothing Epic controls. This one is a function of politics, and the design's answer to it — that you can hold your own keys and transact peer to peer without an exchange — is real but partial.
Seven: the record, including the part that is uncomfortable In March 2021 the chain was rolled back to remove a value- overflow exploit, and it was paused for several weeks while that happened. Chapter eleven covers the mechanics; here is the cost.
A rollback is a centralization event. Someone decided which history would stand. The precedent is Bitcoin's own in 2010, and the alternative was a chain carrying counterfeit coins — but a reader who values immutability is entitled to treat this as a scar rather than a footnote, and I do.
There is also the reputational residue of the years since: a price that fell a long way from its earlier highs, a community that has argued with itself in public, and a persistent assumption among people who have not looked closely that the project is dormant. It is not dormant. It is small, which looks similar from a distance.
What would prove this book wrong A book that cannot be falsified is propaganda. Here is what would falsify this one.
If the privacy were broken in practice. Not a theoretical weakness — a demonstrated deanonymization of ordinary transactions at scale. If that happened, the central claim collapses and most of the book with it.
If the supply were not what the code says. If a value-overflow class bug returned, or if the commitments failed to enforce the cap, the monetary argument dies.
If adoption stayed flat for another decade while a rival solved privacy with better tools. The thesis is not "Epic eventually wins." It is "the design is sound and the adoption is a matter of time." If the second half is false for ten more years, the first half is an interesting museum piece.
If a soundness bug hit Epic's own range proofs. The 2026 failures in this category were proof-system failures. Epic uses Bulletproofs, which have a long record, and "long record" is not "immune."
None of these has happened. All of them could.
Why this chapter is not the end of the argument Because "not yet" and "cannot" are different words, and the distinction is the whole book.
Epic Cash does not have adoption. That is a fact about the present. It does not follow that it cannot have adoption, and the argument for why it might — the design, the verification, the moment — is what the previous twelve chapters were for.
What the book will not do is pretend the gap is small, or that the missing pieces are somebody else's fault, or that a good design is owed a market. It is not.
The next chapter is the one that has to earn the optimism back: why a gap this large, in a category this early, is the thing that makes the asset interesting rather than the thing that makes it doomed.