Everything before this was the argument. This chapter is the part you can act on.
It is deliberately procedural, because the failures in this space are almost never philosophical. People lose coins to a missing memo field, a mistyped address, a seed phrase photographed into a phone that was later replaced, and an exchange that closed while the balance was still on it. None of those require an adversary. They require an ordinary Tuesday.
Four things, in order: buying it, getting it off the exchange, keeping it, and spending it.
Buying it Epic is listed on a small number of exchanges. NonKYC is the deepest market and the one this book uses for its worked examples, because it lists Epic against both a stablecoin (USDT) and Monero (XMR).
The two pairs are not the same trade.
EPIC/USDT prices the coin in dollars, which makes the arithmetic simple and the mental accounting easy. It puts a stablecoin in the path, which means an issuer sits between you and the coin for the duration of the trade.
EPIC/XMR keeps the stablecoin out entirely, which is the coherent choice if the reason you want Epic is that no one can freeze it. It costs you a conversion in your head, because every price is quoted in Monero, and it typically carries a wider spread.
Neither is wrong. Pick the one that matches why you are buying.
Three practical rules apply to both.
Use limit orders. The order books are thin — the best ask has held single-digit coins on both pairs — and a market order walks up through several levels paying progressively worse prices. A limit order at or near the touch fills quickly and never surprises you.
Price from the book, not from the chart. Click the row you want and let the exchange fill in the number. It removes a whole category of rejected orders and mispriced fills.
Keep fee headroom. The trading fee is charged on top of the order value. If you spend your entire balance, the ticket can reject for insufficient funds. Keep a few percent back.
The deposit method, and the field that is not optional This is the single most common way a beginner loses access to their coins, and it deserves its own section rather than a bullet.
Because Epic has no addresses, an exchange cannot look at the chain and see that a payment was sent to it. It settles the question one of two ways. The first runs through a relay: the exchange gives you a number — an onchain note — and asks you to include that number in the payment, then matches the note to your account and credits you. The second puts your account number inside the deposit URL itself, so the exchange knows whose payment it is from the string you paste.
Where both are offered, use the URL. There is no note to leave out and no relay to be down, which removes both failure modes at once.
If you are on a deposit page that only does the relay method, the note is required, whatever your wallet says. The wallet labels that field optional; the exchange's page labels it required. The wallet is describing the protocol field; the exchange is describing its own need. Both are telling the truth, and only one of them will get your money credited.
If you leave it blank, the funds arrive and cannot be attributed to anybody. The exchange holds money it cannot give to you, and recovering it depends on a support process you do not want to rely on.
Write the note down when you first generate a deposit address. It stays the same for that address. Keep it with the address, not in a screenshot folder.
Getting it off the exchange The only coins that are yours are the ones you control the keys to. Everything on an exchange is a promise, and chapter two is about what promises are worth.
First, set up the wallet. BT Wallet, from BT LABS at epiccash.btlabs.uk/releases or from the app store on your phone. Check a downloaded file against the SHA-256 on that page before you run it. Write the twenty-four words on paper — not in a note, not in a password manager you have not tested, not as a photograph. Verify the backup by restoring it before you put anything in it. If this wallet received coins before 2025, choose "Scan from the start" when restoring, or the wallet will restore an empty balance.
Second, send a test amount. Ten dollars, or the smallest amount that clears the withdrawal minimum. Confirm it arrives, confirm you can see it, confirm the note was credited if it went to an exchange.
Third, send the rest. Withdraw to the wallet's identifier. Wait for confirmations. Then, if the amount matters, point your wallet at your own node, so the balance it shows comes from a chain you checked yourself.
Withdrawal fees are small — around a dollar on most venues — but not zero. Consolidating several small buys into one transfer is worth doing.
Keeping it Six rules. They are not complicated and almost every loss in this space is a violation of one of them.
The words are the money. Anyone who has the twenty-four words has the coins, no matter what the wallet says. Anyone who does not, does not — no support desk, no developer, no court can restore them.
Never type them into anything except your wallet during a restore. Not a website, not a chat, not a support form, not a helpful person on Telegram who offers to check them for you.
Keep two copies, in two places, offline. Paper or stamped metal. A house fire should not be a total loss, and neither should a burglary.
Test the restore. A backup you have never restored is a hope. Restore it once, on a spare device, before the balance is large enough to hurt.
Do not keep the whole balance in one place. Two wallets with separate seeds is a meaningful improvement over one perfect wallet.
Remember that the wallet application is not the money. Wallets get abandoned and replaced; the words are the asset, and any compatible wallet restores them.
Using it Sending is covered in chapter twelve at the level of principle. At the level of practice, three things.
The handshake. Your wallet and the recipient's have to exchange data for the payment to be built. The wallet handles this through the relay: you paste the recipient's identifier, the wallet does the rest, and the recipient collects it. If the recipient is online and using the same wallet, this is nearly as fast as any payment app.
The confirmations. One block is about a minute. For a coffee, that is enough. For a car, wait for several, and for anything between strangers, treat it like any settlement: time is the collateral.
The receipt problem. Every payment leaves a kernel in a public block, and explorers exist — but they show that a payment's kernel was confirmed, not who paid or how much. To show a merchant the amount, share the transaction from your wallet. Your wallet's history is the record, and the merchant's node is theirs. For a business, this means the point-of-sale process has to record the transaction on both sides rather than pointing at a URL. It is a real integration cost and the ecosystem is still building for it.
When something goes wrong A deposit never arrives. Open a support ticket with the transaction ID, the amount, the time and the onchain note if there was one. On a privacy chain, the exchange genuinely cannot find your money without your help.
You forgot the onchain note. Contact the exchange immediately with the transaction ID. Recovery is possible — the funds are in their custody and identifiable from their side — but it depends on their process and goodwill.
You sent to the wrong identifier. There is no reversal and no recovery. This error has no remedy, and it is the reason the test transaction rule exists.
You lost the seed. Nothing can be done. This is not a support failure; it is the design working as intended.
The one page version If you remember nothing else from this book, remember these five sentences.
Buy with a limit order, priced from the book, and keep a few percent back for the fee.
Write the onchain note down with the deposit address, because the wallet says optional and the exchange says required.
Send a small test before you send anything that matters.
The twenty-four words are the money; two copies, offline, in two places, tested once.
And the only coins that are yours are the ones you can move without asking anyone.
Everything else — the scorecard, the mining, the Mimblewimble, the entire argument of this book — is worth exactly as much as your ability to do those five things correctly.
The quiet conclusion On the second of November, three million people opened an app and were told that their balance could not be displayed.
Nothing in this book can change what happened to them. But everything in this book exists because of the question they must have asked themselves that morning: what did I actually own?
The answer, for almost everyone reading this, is a claim — on an institution, denominated in a supply that someone else controls, reachable only through permissions someone else grants. That is true on the good days too. It is a description of the instrument, not a prediction about the bank.
Epic Cash is an attempt to answer that question differently, and this book has tried to show its work rather than assert its conclusion: thirty-two attributes defined before anything was scored, six assets judged against them, a design opened up and examined, a list of failures stated in full, and a gap named plainly rather than explained away.
What you do with that is not something a book can decide. It can only try to leave you with something more useful than an opinion — a test you can run yourself, on any asset, without asking anyone's permission.
That is the whole of it. The rest is patience.
A P P E N D I C E S A P P E N D I X A The scorecard on page 38 compresses thirty-two attributes into a grid. This is the same test, expanded, so a reader can argue with a specific line rather than the whole table.
Each row is a question. If you disagree with the verdict, the disagreement is now narrow enough to be useful.
A note on the word yes. It means the property holds in the base protocol, not that it holds for every user in every circumstance. Someone who buys EPIC on an exchange and leaves it there has a custodial claim on a private ledger, which is a different object from coins in a wallet they control. Several of these attributes are lost at that boundary, and the loss is the exchange's business model, not Epic's design.
# ATTRIBUTE WHAT IT ASKS EPIC Means of payment Can you pay someone with it directly? Yes Peer to peer Can you pay without an intermediary? Yes Divisible Can it be split into ordinary amounts? Yes Digital Does it exist natively online? Yes Borderless Does it cross borders without permission? Yes Unit of account Can prices be set in it? Yes Private by default Is privacy the default? Yes Decentralized Is control spread beyond any one party? Yes Fungible Is one unit interchangeable with another? Yes # ATTRIBUTE WHAT IT ASKS EPIC Surveillance resistant Are who-paid-whom links hidden from observers? Yes Politically resistant Are its rules out of a government's reach? Yes Censorship resistant Is it safe from selective blocking? Yes Confiscation resistant Are holdings safe from seizure without the keys? Yes Scarce Is the supply capped? Yes Store of value Does it hold value across time? Yes Inflation resistant Is expanding supply at will hard? Yes Fair launch Did everyone start on equal terms? Yes Publicly verifiable Can anyone check the ledger? Yes Trust minimized Can you verify without trusting a third Yes Permissionless Can you use it without approval? Yes Immutable Is rewriting history hard? Yes Neutral Is it indifferent to who uses it? Yes Survivable Can it outlast its founders? Yes Eco-friendly Is securing it cheap in energy? Yes Open governance Can anyone see and influence decisions? Yes Regulation friendly Can it comply without changing its nature? Yes Durable Does it resist decay? Yes Scalable and fast Does it settle quickly under load? Yes Portable and mobile Can you carry it anywhere? Yes Available to the unbanked Does it work without a bank? Yes Widespread acceptance Will a stranger take it? Not yet # ATTRIBUTE WHAT IT ASKS EPIC Quantum future proofed Does it survive quantum computing? Not today Thirty of those answers are a plain yes, and they read the way they should: nobody can map your payments, change the rules underneath you, pick your coins out of the set, or seize them without your keys. Two are qualified — the design is not quantum-proof today, and it is not widely accepted yet — and only the second of those is a failure no design can fix.
Five rows people argue about 12, censorship resistant. Safe from selective blocking, which is the row's meaning. A miner can still leave a transaction out of a block, and a state can cut your connection — but no one can pick your coins out of the set and refuse those in particular, because the chain gives them nothing to pick by.
24, eco-friendly. The claim is comparative, not absolute. Most of Epic's blocks are mined on commodity CPUs and GPUs rather than purpose-built ASICs — though a minority, around four percent, use Cuckatoo, which ASICs can mine. The comparison that matters is against chains secured entirely by industrial hardware, not against a hypothetical zero. A reader who thinks any proof-of-work is disqualifying will mark this row no, and that is a coherent position.
26, regulation friendly. This does not mean Epic is compliant with any particular regime, and it does not mean regulators approve of it. It means the protocol does not require an identity field to function, so an exchange or custodian can meet its own obligations at the edges without the base layer being rebuilt.
31, widespread acceptance. The only unambiguous failure, and the one this book is about. Everything else on the list is a property the design supplies. This one is supplied by other people deciding to use it, which is why no amount of engineering settles it.
32, quantum future proofed. Not today. A large enough quantum computer would break the commitments and the signatures alike, as chapter seven says. What makes the row survivable is that the scheme can be replaced without changing the money — same chain, same supply, new cryptography.
A P P E N D I X B This is the practical appendix: how to actually acquire EPIC without a bank, a broker, or a form that asks for your employer. It condenses two longer guides — one for the EPIC/XMR pair, one for EPIC/USDT — which are available separately.
Nothing here is advice. It is a description of what the screens ask for, and where people lose money using them.
The venue NonKYC is a small exchange that runs on the premise that it does not want to know who you are. That premise is worth exactly as much as the operator's honesty, and no more: an exchange that does not collect identity documents still holds your coins while they are on the exchange. Custodial until you withdraw is the rule; "no KYC" is not the same as "no risk.
The two pairs that matter:
EPIC/XMR — Epic priced in Monero. For someone arriving from Monero, this is the cleanest path: no stablecoin, no bank rail, no identity.
EPIC/USDT — Epic priced in Tether. Easier if you already hold dollars on-chain, and it introduces the issuer risk that chapter two describes: a balance that can be frozen by an administrative decision.
Both books are thin. Sizes that would be a rounding error on a major exchange move the price here, which is a fact about the asset and worth knowing before you place an order.
The account An email address, a password, and two-factor authentication. Turn on the authenticator before you deposit anything; an account without it is an account someone else can empty. Withdrawals additionally require an eight-digit PIN sent to your email, which is a second factor and also a second thing to lose access to.
The deposit, and the field that is not optional NonKYC offers two deposit methods for EPIC, and the choice matters.
Epicbox gives you a deposit address and an onchain note number. The note is how the exchange attributes an incoming payment to your account, because on a ledger with no addresses it has no other way to know who sent what. The payment travels through the exchange's relay, and if the relay is unreachable or your wallet cannot reach a node, the send fails.
HTTP gives you a custom URL with your account number already inside it. Paste that as the destination and there is no note to forget and no relay in the path. Use this one. It removes the failure mode the next paragraph is about.
If you use epicbox anyway, the note is not optional. Your wallet may label that field (optional) — that is the protocol's description of it, not the exchange's. Leave it out and the coins arrive, cannot be attributed, and become a support ticket — the privacy design working exactly as designed.
Write the note down when you create the account. If you lose it, you can retrieve it from the deposit page, but not from the blockchain.
The trading screen The market is an order book, not a swap box. Two columns of resting orders — bids on one side, asks on the other — and a form that either takes the best available price (market) or waits at a price you name (limit).
Three things trip people up:
Decimals. Prices are quoted to eight places, quantities to three. 0.00128652 is a price, not a typo, and a limit order at the wrong decimal is a gift to whoever takes it.
Market orders on a thin book. A market buy for a size the book cannot absorb walks up through every ask, and you pay the worst price on the way through. On EPIC/XMR, check the depth before you send anything larger than a few hundred dollars.
The spread. The gap between the best bid and the best ask is your cost of entering and leaving. On a quiet day it is around half a percent, which is cheap for a privacy coin and expensive compared with a major pair.
The fees Trading is 0.2 percent at the base tier, falling toward 0.06 percent at the top, with a further 25 percent discount for holding the exchange's own token. A maker order — one that rests in the book — is cheaper than a taker order that removes liquidity.
Withdrawal of EPIC costs 1.4 EPIC, which is a flat fee and therefore proportionally cruel on small amounts.
The exit Withdraw to a wallet you control. Paste the address from your wallet, not from a chat message, and confirm the first characters and the last on both screens. There is no chargeback and no support line that can reverse a payment on a chain designed to make reversal impossible.
Four ways beginners lose money The onchain note, omitted. Described above. It is the most common, and it is silent — the transaction succeeds, the balance does not appear.
The wrong network. USDT exists on a dozen chains. A deposit sent on the wrong one is usually gone.
The seized exchange. A custodial balance is a promise. Promises are not coins.
The panic sale. Thin books fall faster than thick ones. If you cannot name the price at which you would be wrong, you will find it during a bad hour.
A worked example Buying 500 EPIC at 0.76551 USDT costs 382.76, plus 0.77 in fees: 383.53. Selling the same 500 straight back at the bid, 0.76170, returns 380.85, less 0.76 in fees: 380.09. The round trip loses 3.44, about 0.9 percent — roughly what the spread and two fees cost, and the reason a thin market punishes people who trade rather than hold.
A P P E N D I X C Two shapes of software, doing two different jobs.
BT Wallet is the one to install. It is self-custodial, open source, and made by BT LABS, whose founder is a long-time Epic Cash developer, and it ships for Windows, Linux, macOS (Apple silicon), Android and iPhone, updating itself from inside the app (copies from Google Play or the App Store update through the store). Every file on its release page at epiccash.btlabs.uk/releases has a SHA-256 checksum you can compare with BT LABS' signed list before you run it.
What it does that the older wallets did not: invoices — you ask a paired contact to pay an amount, and they approve and pay it or decline it, while you can withdraw it until it is paid; contacts and pairing, so you pay a person you know rather than a pasted string; payment links, which fill in the payment for you; a version with Tor* and a version without it, because the law on Tor differs from place to place, with a Tor mode that sends every connection through Tor; a Kill switch mode that stops the wallet connecting at all; and support for running your own node, which the wallet sets up and manages for you. BT Wallet is in active development, and the work aims at making payments between wallets more private and more reliable, using new cryptographic tools.
* No Tor on iPhone for now.
A wallet without a node of its own keeps your keys on the device and connects to nodes spread across the network to fetch chain updates and check balances. The trade-off is the same as every light wallet: you are trusting a node to tell you the truth about balances. A node never holds your keys, but a node can be hostile, so use nodes the community trusts; status.btlabs.uk lists public nodes and shows whether they are online and in step with the chain. Run your own node and the wallet checks the chain itself, at the price of a first sync and some disk space.
New wallet software deserves a small first payment, whichever wallet it is, and the recovery phrase written down either way — a wallet is replaceable, the words are not.
No wallet here is a bank app. There is no password reset, no support line that can move your coins or see your history, and no way to reverse a transaction. That is the point, and it is also the cost.
Ten rules, in the order they matter 01. The recovery phrase is the money. Twenty-four words in BT Wallet (some other wallets use twelve), written on paper, stored somewhere that does not burn and is not photographed. Anyone who has them has the coins. Anyone who does not, does not — including you, if you lose them.
02. Never type the phrase into anything but the wallet. No support agent needs it. No website needs it. No helpful person in a chat needs it. A recovery phrase requested is a theft in progress.
03. Test the restore before you trust the backup. On a second device, or a fresh install of the wallet, choose Restore wallet, enter the phrase, and confirm the balance appears. If the wallet received coins before 2025, tap Start from a date or height, then Scan from the start. Keep the original wallet as it is until it does, and close the test copy afterwards. A backup you have never tested is a hope.
04. Two copies, two places. One at home, one somewhere else that is physically separate. Fire and flood are more likely than cryptography failing.
05. Do not store the phrase digitally. No screenshots, no cloud notes, no password manager entry that syncs, no email to yourself. A copy of the phrase on a connected device, outside the wallet, is a copy someone else may find.
06. Verify addresses character by character. Epic has no addresses on its chain, but to get paid a wallet still hands out a long string that tells the sender's wallet where to deliver the payment. Anywhere such a string is pasted, check the first and last characters on both screens. Malware can swap a copied string for another, and a swapped string pays someone else.
07. Send a small amount first. Any new destination, any new wallet, any new exchange: send the minimum, confirm it arrives, then send the rest.
08. Keep the deposit note. Where the exchange uses the relay method, the note is part of the address. Store it with the deposit address, not separately, and in BT Wallet put it in the Message field when you send; a deposit link or QR from the exchange fills it in for you. Without it the exchange may not know the coins are yours. Where the exchange offers a URL deposit, use the URL and leave the message empty.
09. Mind what happens around the chain. Epic's chain shows that payments happened, not who paid whom or how much: there are no addresses on it, amounts are hidden, and nodes drop spent outputs as they go, so there is no public list of your payments for anyone to search. What can leak is around the chain: when you connect, from which IP address, and through which node and server. A well-resourced observer watching one particular wallet over time could learn something from that. Tor and your own node make it harder.
10. Write down what you did. A short note, offline: which wallet, which version, where the backup is, which exchange account exists. The person recovering your coins may be you, years later, with no memory of any of it.
If something goes wrong A wallet that will not sync is usually a network problem, not a loss: check the internet connection, check the network mode in Settings › Network & privacy (Kill switch and Node only hold some or all connections), and check whether the node you point at is answering. A wallet that will not open is not a loss while the recovery phrase exists. A phrase that is lost is a loss, and it is final.
The recovery path is always the same: install the wallet, choose Restore wallet, enter the phrase, then Start from a date or height and Scan from the start if the coins arrived before 2025, and wait for the chain to catch up. The coins come back from the phrase; payment history, notes and contacts come back only from an exported wallet data file. It works or it does not, and testing it in advance is the only way to know which.
A P P E N D I X D Aggregated signature. A single small proof that stands in for thousands of signatures, which is how Mimblewimble keeps a chain small.
Block reward. New coins paid to whoever finds a block. Epic halves this on a schedule; Bitcoin halves roughly every four years.
CoinJoin. A technique that combines several payments into one transaction so an observer cannot tell which input funded which output.
Confiscation resistance. The property that holdings cannot be taken without the keys, regardless of who asks.
Consensus. The rules every node enforces, and the reason a ledger with no administrator still has one agreed history.
Custodial. Held by someone else — an exchange, a broker, a bank. You have a claim, not the coins.
Cut-through. Removing intermediate outputs — within a block, and across blocks as the chain is compacted — keeping only what is still unspent.
Dandelion++. A relay protocol that sends a transaction through a random "stem" before broadcasting it, so the first node to see it is not obviously its author.
Emission curve. The schedule by which new supply is created over time.
Era. Epic's term for a period between halvings of the block reward.
Fungibility. The property that one unit is indistinguishable from another. A coin with a history is worth less than a clean one; a coin that cannot have a history is worth the same as every other.
Genesis block. The first block in a chain.
Halving. The scheduled cut in block reward. Epic's are annual in its early eras, then stretch out.
Kernel. In Mimblewimble, the part of a transaction that proves it balances and commits to the fee, without revealing amounts.
Levy. Epic's declining issuance allocation, which funds development and expires before the supply curve flattens.
Light wallet. A wallet that does not store the chain and asks a node about it instead, trading verification for convenience.
Mimblewimble. The protocol family Epic uses: no addresses, no amounts on-chain, and a compact ledger built from cut-through and aggregated signatures.
Mempool. The queue of transactions waiting to be included in a block.
Mixnet. A network that hides who is talking to whom by routing traffic through several relays.
Node. A computer that validates the chain and relays transactions.
Onchain note. NonKYC's term for the number that attributes a deposit to your account on a ledger with no addresses.
Output. A discrete amount of coin, spent as a whole and re- created as change.
Pedersen commitment. A cryptographic commitment that hides an amount while still allowing the network to verify the books balance.
Permissionless. Usable without anyone's approval.
Range proof. A zero-knowledge proof that a hidden amount is a valid, non-negative number. Epic uses these; they are a genuine zero-knowledge construction, and the protocol has no general- purpose zero-knowledge circuit beyond them.
Reorg. A reorganization of recent blocks, where the chain replaces its tip. Normally shallow; consequential when deep.
Seed phrase. The words that regenerate a wallet. Whoever holds them holds the coins.
Slate. In Mimblewimble, the file exchanged between two parties to build a transaction together — the closest thing the protocol has to an invoice.
Solo mining. Mining without a pool, keeping the full reward and bearing the full variance.
Stem phase. The first, private hop of a Dandelion++ relay.
Taint. The informal marking of coins by their history, which exchanges and analytics firms use to refuse or flag deposits.
Tail emission. A small permanent block reward, used by some chains to pay for security indefinitely. Epic has none; its supply is capped.
UTXO. An unspent transaction output — the individual coin being spent.
Zero-knowledge proof. A proof that a statement is true without revealing why it is true.
A P P E N D I X E A book that asks you to check its work should say what the work was.
What the argument rests on Primary documents. The Epic Cash white paper, first published in 2019 and revised since; the 2026 technical edition; and the protocol's own source code and consensus rules, which are the only authority on what the chain actually does. Where the documents and the code disagree, the code wins, and the book says so where it matters.
The chain itself. Supply figures, emission schedule, block times and the date of the singularity are properties of the ledger, not claims about it. A reader with a node can reproduce every supply number in this book.
The public record. Exchange listings and fee schedules; the Zcash Orchard advisory; the Zano incident report; disclosures from Firo and Beam; the Bogatyy paper on Grin transaction tracing; and the market data used in chapter fourteen, captured on 5 November 2026. Prices move; the capture date is stated so a reader can tell the difference between an error and a stale figure.
The Quest for Superior Money. The thirty-two attribute framework, published in 2026, which supplies the test in Part Two. The book applies it; it did not invent it.
What could not be verified, and is marked as such No consolidated third-party audit of the full protocol has been published. Epic's cryptography inherits from the Grin and secp256k1-zkp lineage, and its range proofs are a genuine zero- knowledge construction — but a lineage is not an audit of this codebase. Chapter thirteen says this plainly rather than letting the reader assume otherwise.
There is no published post-mortem of the 2021 episode. The book describes what is publicly known and declines to narrate what is not.
The genesis date is inconsistent across sources. The 2019 white paper gives 1 August 2019; later material gives 2 September 2019. The chain settles this question and the sources do not; the discrepancy is noted rather than resolved by preference.
Privacy has not been measured. No study has attempted to trace Epic transactions at the scale Bogatyy attempted on Grin. The claim that Epic resists the tracing he claimed on Grin is an argument from its construction, not an experimental result, and is presented as such.
How the book was made The research, drafting, typesetting and figure work were done with substantial AI assistance, directed and edited by the author. This is disclosed because a reader is entitled to know how a text was produced, and because the alternative — leaving it out — would be the kind of omission this book criticizes elsewhere.
Every number in the text was checked against a source at the time of writing. Where a figure is an estimate, the text says so.
Where a claim is contested, the text gives the contest. Where the author does not know, the text says he does not know.
If you find an error, the useful response is not to trust the book less. It is to check the source, and then to say which line is wrong — that is the whole method, and it only works if readers use it.
If you find an error, the useful response is not to trust the book less. It is to check the source, and then to say which line is wrong — that is the whole method, and it only works if readers use it.