Roger Ver

Roger Ver Twitter Review Guide: Everything You Need To Know (With FAQ)

Thinking about following Roger Ver on X/Twitter but not sure if it’s worth your time—or your attention?

I’ve watched his journey from “Bitcoin Jesus” to Bitcoin Cash champion in real time, and I know how easy it is to get lost in the noise. In this guide, I’ll show you exactly what you can learn from his feed—what he posts, the ideas he pushes (peer-to-peer cash), how that might shape your thinking or portfolio, and how to fact-check it all before you act.

“A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another.” — Bitcoin whitepaper

Describe problems or pain

Roger’s timeline is a firehose: bold takes, fee screenshots, merchant videos, and heated BTC vs BCH arguments. Sorting signal from noise is the hard part.

• BTC vs BCH tribal fights: You’ll see strong claims on both sides—“BTC fees are unusable” vs “BCH has no demand.” The truth often depends on timing and context.


• Screenshot wars: Fee charts and mempool graphs get shared without timestamps. During congestion, BTC fees can spike; off-peak, they can drop sharply. If you don’t check the date and market conditions, you can get misled.


• Layer confusion: On-chain, Lightning, sidechains, custodial wallets—each has trade-offs. It’s easy to compare apples to oranges if you don’t know which layer a claim refers to.


• Merchant clips: A café accepts BCH today—but is it a pilot, a promo, or an ongoing setup? Without a quick test or follow-up, “adoption” can be a one-off video.


• Algorithmic outrage: Platforms reward spicy content. Studies have shown that emotionally charged posts spread faster than factual ones, so the loudest claims aren’t always the most useful. See: Science (MIT): The spread of true and false news and broader context from Pew Research Center.


• Years of history: The 2017 split, scaling debates, legal headlines—newcomers jump in mid-episode and miss the backstory, which makes current claims hard to weigh.

Real-world example patterns you’ll encounter:

• Fee snapshot vs lived experience: A tweet shows BTC fees “$X per send” next to “pennies on BCH.” That might be true in that hour. A better read: check today’s mempool chart, send a tiny test on both, and note wallet defaults (RBF, batching, channel liquidity).


• Merchant highlight: A restaurant announces BCH payments. Strong signal if you can actually place a small order and the QR codes match what’s claimed. Weak signal if there’s no menu system or the terminal is offline.


• UX claims: “Payments feel instant.” Which wallet? On which network? With what settings? Small details—like invoice expiries or channel routing—make or break the experience.

Promise solution

Here’s how I’m going to make this simple and useful:

• Map out who Roger is today and how his stance has evolved so you can understand the lens behind his takes.


• Spell out what he actually recommends and why the “peer‑to‑peer cash” angle dominates his posts.


• Show you what his Twitter feed usually looks like—recurring themes, metrics he cites, and how to spot strong vs weak evidence.


• Share a quick, repeatable sanity-check routine: where to verify fees, how to confirm merchant claims, and how to run your own micro-tests safely.


• Extract value without getting dragged into endless arguments—use his posts as prompts for experiments, not tribal identity.

Who this guide is for, and quick disclaimer

If you’re crypto‑curious, building payment tools, or trading with an eye on real-world utility, this is for you. I’m not taking sides; I’m focused on helping you read his feed strategically and verify claims before you act.

• You want to understand the “peer‑to‑peer cash” thesis without getting stuck in flame wars.


• You care about fees, reliability, and UX—because you actually want to send and receive money, not just talk about it.


• You need practical checks: live dashboards, tiny test transactions, and simple rules to avoid being misled by screenshots.

Ready to make sense of the person behind the posts? Next up, I’ll quickly walk through who Roger Ver is today, what changed after 2017, and the simple money lens he uses to judge every coin—so you can read his tweets like a pro. Curious what that lens is?

Roger Ver today: fast bio, stance, and what’s changed

Quick snapshot: he was one of Bitcoin’s loudest early promoters—nicknamed “Bitcoin Jesus” for handing out BTC and pushing merchant adoption when almost nobody cared. After the 2017 scaling war, he shifted his energy to Bitcoin Cash (BCH), arguing it stayed truer to the “peer-to-peer electronic cash” goal. That shift wasn’t just branding; it was a philosophical line in the sand about fees, speed, and how everyday people should pay each other.

“Bitcoin is one of the most important inventions in the history of the world.” — Roger Ver

What’s changed since the early days? He still champions permissionless payments, but he’s far more critical of BTC’s high-fee periods and reliance on layered solutions. He frames BCH as the practical path for day-to-day transactions—groceries, gig work, tipping, cross-border remittances—while positioning BTC as drifting toward a store-of-value niche.

His money philosophy in plain English

Underneath the noise is a consistent worldview: individuals should control their money without middlemen telling them “no.” He wants money that moves like information does—cheap, instant, global, and unstoppable.

• Self-custody first: You hold the keys, you hold the money. No arbitrary freezes.


• Low fees matter: If sending $5 costs $5 in fees during congested times, you’ve priced out half the planet.


• Speed and UX: If your aunt can’t complete a payment in one try, adoption stalls.


• Borderless commerce: Anyone, anywhere, no permission asked.

That lens syncs with real-world friction. Global remittances still carry heavy costs—World Bank data shows average fees hovering around 6% in recent years, with some corridors far higher. If you’re sending small amounts or paying daily expenses, those fees crush utility. This is the emotional core of his message: money shouldn’t feel like a gated privilege—it should feel like sending a text.

Personal example: years back, I paid on Purse.io using BCH for a small order and it felt like online shopping should—scan, confirm, done. That kind of low-friction experience is why he keeps hammering “payments-first.”

Companies and investments you’ll hear about

His background is full of payments rails, merchant tooling, and on-ramps—so his feed often references wallets, gateways, and real-world checkout flows.

• MemoryDealers.com: His early business that famously accepted Bitcoin back when that was a radical idea.


• Bitcoin.com: He led it for years—think wallet, news, and beginner on-ramps (expect frequent wallet and merchant chatter).


• Early investments:
  
  
  
  • BitPay (payment processing; added BCH support in 2018—useful context for his “spend crypto” stance)
  
  
  • Kraken (exchange infrastructure)
  
  
  • Blockchain.com (wallet/exchange)
  
  
  • Purse.io (crypto-for-goods marketplace that has long supported BTC and BCH)
  
  
  
  

Because his capital went into payment rails early, he tends to measure success in practical terms: how quickly a checkout clears, how intuitive the wallet flow is, what fees look like today, and whether a merchant can accept a $3 payment without friction.

Context and controversies

Strong views attract strong pushback. A few threads you’ll often see referenced around him:

• BTC vs BCH split (2017): He backed bigger blocks and on-chain scaling; critics preferred small blocks plus layers. BCH forked with larger capacity, lower typical fees, and a “spend it” culture.


• Branding and confusion: His stewardship of Bitcoin.com to promote BCH led to complaints from some BTC supporters who say newcomers mixed up “Bitcoin” and “Bitcoin Cash.” He argues BCH is closer to Bitcoin’s original use-case.


• Legal headlines: In April 2024, the U.S. Department of Justice announced charges related to tax matters; he was arrested in Spain (DOJ press release). Treat legal news as evolving—follow primary sources.


• Exchange disputes: The 2022 CoinFLEX situation triggered very public claims and counterclaims about an alleged debt; both sides published their positions (coverage). As always, verify timelines and documents.


• Heated debates with Bitcoiners: Expect arguments over fees, throughput, Lightning UX, and what “Satoshi’s vision” really meant. He stays focused on payments; opponents emphasize security trade-offs and layered scaling.

If you strip away the drama, the throughline is simple: he believes ordinary people need crypto that just works at checkout, without surprises. Agree or disagree, that’s the filter shaping every recommendation he makes.

So what does that belief look like in practice on his Twitter/X timeline—what patterns show up, which metrics he leans on, and how do you separate signal from heat? Let’s look at exactly what to expect next.

What to expect from @rogerkver on Twitter/X

I scroll his feed the way some people check the weather: quick, practical, and focused on whether payments feel “sunny” or “stormy” today. Expect a steady rhythm of posts about low fees, fast confirmations, and real-world spending. He’ll celebrate a coffee paid in BCH, critique BTC’s fee spikes, and spotlight wallets or merchant tools that make checkouts smoother. If you care about crypto working like actual money, his timeline is a daily pulse check.

“A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another.” — Satoshi Nakamoto

That line is the emotional backbone of his posts. You’ll feel it when he shows a $3 purchase that clears instantly for fractions of a cent. You’ll feel it again when he rails against a $10 network fee that blocks small payments. Love him or not, he’s relentlessly focused on usable money.

The recurring themes

• “Peer-to-peer cash” as a north star: If a chain makes everyday payments cheaper and simpler, it gets airtime. If it makes them harder, expect pushback.


• Low fees and fast confirmations: He shares fee screenshots, mempool charts, and checkout videos. During 2023–2024 congestion spikes, BTC’s median fee often cleared $5 (sometimes north of $20); you’ll see him contrast that with BCH fees that typically sit at fractions of a cent. Neutral sources to verify:
  
  
  
  • mempool.space (BTC mempool and fees)
  
  
  • BitInfoCharts fee charts (BTC/BCH)
  
  
  • TXStreet (visual transaction flow)
  
  
  
  


• Payment UX over speculation: He highlights tap-to-pay flows, QR scanning, and simple wallet experiences (you’ll often see Bitcoin.com Wallet, Paytaca, etc.). The point is always: “Could your grandma use this?”


• Merchant adoption and receipts: Think cafes, e‑commerce, and gift cards. He loves a clean receipt screenshot and a price breakdown showing near-zero network costs. If you’re curious, try replicating one of those purchases with a $1–$5 test.


• Freedom and permissionlessness: He ties payments to personal liberty. The emotional hook is clear: money you control, no middleman, no gatekeeper.


• Micropayments as a litmus test: Small buys are where high fees wreck the experience. This lines up with what payments research keeps finding: when transaction costs grow, low-value payments drop off quickly (see general findings in BIS 2023 reports on crypto’s limits for retail payments).


• New BCH features and tooling: You’ll see nods to things like CashTokens, simpler point-of-sale flows, and 0-conf with extra safeguards. The tone is “make it work at the counter.”

Bitcoin vs Bitcoin Cash: how he frames it

His line is consistent and blunt: BTC optimized for being a store of value and leaned on higher fees plus layered solutions; BCH kept the “spend it like cash” approach. You don’t have to agree, but understanding his lens helps you read his posts without getting sucked into the arguments.

• BTC in his view: Great brand, strong security, but on-chain fees make small payments impractical during busy periods. He questions the everyday UX of pushing most users to second layers or custodial services.


• BCH in his view: Scales on-chain for day-to-day use, keeps fees tiny, and aims for a “tap and go” feel. He’ll show grocery totals, coffee purchases, or cross-border remittances with costs rounded to almost zero.


• What he posts to back it up:
  
  
  
  • Fee comparisons with timestamps
  
  
  • Checkout videos using QR codes and instant confirmations
  
  
  • Merchant anecdotes (cafes, online stores, travel bookings)
  
  
  
  


• Where to sanity-check: Compare fee and throughput data across a few sources and timeframes (peak vs calm hours). Watch how often a merchant actually accepts BCH or if it was a one-off promo.

Context matters here. In late 2023 and multiple moments in 2024, BTC fees spiked around inscriptions/ordinals activity. He’ll amplify those days hard. On quiet days, BTC fees can be low. The takeaway: don’t extrapolate from a single screenshot—look at the week, not just the moment.

Signal vs. noise: reading his timeline smartly

His replies can get fiery; your goal is to extract the useful bits without wasting time. Here’s the simple system I use:

• Track the numbers he cites: Median fee in USD and sat/vB, time-to-first-confirmation, and failed payment attempts. Verify on mempool.space and BitInfoCharts.


• Always check the timestamp: A fee screenshot from last month is ancient history in crypto. If he posts a graphic, I right-click, save, and label the date before comparing with today’s data.


• Recreate the payment: Send $1–$5 across two or three wallets (one BCH, one BTC on-chain, optionally a Lightning wallet) and compare:
  
  
  
  • How long until you feel confident the merchant can hand over goods?
  
  
  • Final fee in USD, including any wallet or routing surprises
  
  
  • Steps required: QR scan, confirmations, channel liquidity, etc.
  
  
  
  


• Merchant claims: If he tags a store, check their site or socials. Gift card rails (e.g., BitPay or other processors) often support multiple coins; make sure BCH is truly accepted and not just through a third-party workaround.


• Mute the drama, keep the data: Use an X List just for payments-related accounts and fee dashboards. Mute hot-button keywords so you see receipts, not arguments.


• Cross-compare wallet UX: Try the same payment on two different apps. Sometimes the coin is fine but the wallet adds friction. He’ll often call that out; you can confirm firsthand.

When he posts something like “$3 coffee, fee: $0.001,” it’s an invitation to test, not a final verdict. During congested windows, BTC can price out that same coffee; during calm periods, it might not. Studies on retail payments make the same point in plain English: small frictions kill small purchases. Your own $5 experiment will teach you more than a hundred threads.

So the big question hanging over all those screenshots and checkouts is simple: which coins does he actually back for that “tap and go” life, and why? Let’s look at the shortlist he consistently supports next—along with how I personally verify those claims before I change anything in my stack.

What crypto does Roger Ver recommend?

Short version: anything that actually works as peer-to-peer cash. In reality, his day-to-day champion is Bitcoin Cash (BCH)—because it keeps fees tiny, makes payments simple, and encourages spending instead of only hoarding.

“Money that works for the next billion won’t ask for permission or charge $10 to say hello.”

When I watch his feed, the pattern is consistent: celebrate fast, cheap payments; call out friction; amplify real-world merchant stories. If a coin or tool makes it easier to pay a friend or a shop—non-custodially and without hoops—he’s onboard. If not, expect a hard pass.

Why BCH fits his thesis

BCH lines up with the “everyday money” playbook: low fees, predictable UX, and a culture that values actually using crypto.

• Fees that don’t ruin small payments. Typical BCH fees are often a fraction of a cent. You can check recent averages on data sites like BitInfoCharts (BCH) or Blockchair. That’s the difference between “buy a $3 coffee” and “why did I pay $5 to send $3?”


• Simple UX for normal people. Most BCH wallets send on-chain by default, no channels, no liquidity puzzles. A first-time user can scan a QR and pay—done.


• Spend-first culture. You’ll see merchant anecdotes, gift-card routes, and payment processors supporting BCH (e.g., BitPay, CoinPayments, GoCrypto). This matches his “money you can use today” stance.


• Fast settlement for the real world. Many BCH payments are accepted instantly by merchants using risk checks (so-called 0-conf). If a merchant wants an on-chain confirmation, it’s still straightforward—no extra layers to manage.

Real sample from my own testing: I’ve sent sub-$10 BCH transactions internationally for fees rounding to $0.00 on receipts, with the recipient seeing it in seconds and spendable based on merchant policy. That’s the kind of experience he highlights—and it’s easy to reproduce.

Where he stands on BTC, Lightning, and stablecoins

BTC on-chain: He’s consistently critical of high base-layer fees during congestion. When mempools fill, on-chain BTC payments can jump to a few dollars or more. Don’t take anyone’s word—check current suggested fees on mempool.space before you try to pay for something small.

Lightning Network (LN): He respects the intent (cheaper, faster BTC payments) but calls out UX friction—channel setup, inbound liquidity, routing failure rates for larger payments, and the tendency toward custodial shortcuts. To balance that:

• Pro-LN datapoint: A 2023 report from River showed high success rates for small payments on a well-connected node.


• Counterpoints he echoes: Academic and community research has shown reliability can drop for larger amounts and that liquidity management adds complexity for new users. You’ll feel this if you try running your own non-custodial LN wallet versus using a custodial one.

In short, he views Lightning as progress with caveats, not “problem solved.” When he says BCH is simpler for day-to-day spend, this is the friction he’s pointing at.

Stablecoins: Pragmatic is the keyword. He’s generally positive on stablecoins for payments and remittances when they’re cheap and fast, especially in places where volatility or banking friction kills adoption. The catch is custody and trust: if you’re using centralized stablecoins on centralized rails or custodial wallets, you’re back to asking permission. He’ll cheer the real-world utility but still nudge you toward non-custodial setups when possible.

How I validate these claims

I don’t treat any hot take as gospel. I test. Here’s the exact playbook I use—and you can copy it in 20 minutes:

• Check today’s fees, not last week’s.
  
  
  
  • BTC on-chain: mempool.space
  
  
  • BCH on-chain: BitInfoCharts, Blockchair
  
  
  
  


• Run small test payments.
  
  
  
  • BCH: Send $1–$5 with the Bitcoin.com Wallet to a friend or a spare device. Note cost and time-to-seen.
  
  
  • BTC on-chain: Use Electrum, set a fee suggested by mempool.space, and compare the cost.
  
  
  • Lightning: Try Phoenix (non-custodial, handles channels for you) or Zeus with a node. Note if a channel open fee hits, or if a larger payment struggles.
  
  
  • Stablecoins: If you must, test a small USDT or USDC payment on a low-fee network. Track speed, fees, and whether you controlled the keys.
  
  
  
  


• Verify merchant claims. If he posts a merchant accepting BCH, I look for a payment processor badge (BitPay, CoinPayments, GoCrypto) on the site or try a $1 gift card at a reputable aggregator. No badge or no checkout? Treat it as marketing until proven.


• Cross-read. If a thread says “X is cheaper than Y,” I pull live dashboards for both. Fees swing with demand; you want today’s snapshot, not a cherry-picked screenshot.

Here’s the emotional truth behind his recommendations: he’s fighting for money that’s usable. Not shiny. Not theoretical. Just money you can send now without a tutorial. If you’ve ever watched a $20 remittance shrink to $13 in fees, you already feel why he pushes this.

Want the play-by-play on using his feed for real value without getting dragged into a flame war? Ready to separate useful tactics from tribal bait in under 60 seconds?

How to use his feed without getting dragged into tribal wars

“Absorb what is useful, discard what is not.” — Bruce Lee

I treat his timeline like a live product feed for peer‑to‑peer payments, not a battleground. The trick is simple: extract tactics, ignore tribes. If a post contains a tool, a metric, or a test I can reproduce, I save it. If it’s a dunk or a dogpile, I scroll.

Here’s the playbook I use to stay focused on value:

• Build a quiet feed: Add him to a private X List called “Payments.” Mute noisy phrases like bcash, maxi, laser eyes, and scam. You’ll keep the signal (wallet tips, merchant news, fee snapshots) and starve the outrage machine.


• Collect, then verify: When he posts fee screenshots or merchant wins, I don’t argue—I test. If I can’t reproduce it in under 3 minutes, it goes to the “maybe later” pile.


• Treat claims like hypotheses: “BCH fees are near-zero,” “BTC fees spike during congestion,” “Lightning adds steps.” Great—now measure it today, not last month.

Quick fact-check checklist

• Is there a verifiable metric? Check it in real time.
  
  
  
  • BTC mempool and fee estimates: mempool.space
  
  
  • BTC vs BCH transaction stats: Blockchair (BTC) and Blockchair (BCH)
  
  
  • Historical context: Coin Metrics charts
  
  
  
  


• Is the claim about a live merchant? Try it.
  
  
  
  • Look up the brand on AcceptBitcoin.cash or the merchant’s own checkout.
  
  
  • Make a tiny test purchase or a $1 donation if available. Screenshots aren’t proof—receipts are.
  
  
  
  


• Is the fee comparison current? Compare today’s conditions.
  
  
  
  • BTC: grab the current sat/vB recommendation on mempool.space. Quick math: fee ≈ sat/vB × ~140 vB for a simple send. Example: 35 sat/vB × 140 ≈ 4,900 sats.
  
  
  • BCH: check median fees on Blockchair; they’re typically a tiny fraction of a cent.
  
  
  • Lightning: remember channel opens/forwards can add fees and friction; user experience varies by wallet and liquidity.
  
  
  
  

If you follow his ideas, what’s the portfolio impact?

You’ll naturally tilt toward assets and tools that favor everyday payments. That can be smart if you actually pay people or accept crypto. But there are trade-offs I account for:

• Utility bias: You may hold more BCH and payment-centric wallets because they feel smooth for microspends.


• Liquidity and venue risk: Not every exchange, OTC desk, or on/off-ramp has deep BCH liquidity. I keep a liquid core in assets with broad market depth.


• Network effects: Store-of-value narratives can dominate cycles even if fees are higher. I size payment-focused bets with this reality in mind.


• Tool stack matters: For BTC Lightning, wallets like Phoenix or Breez reduce complexity, but opening channels costs on-chain fees. Industry research (e.g., River’s 2023 Lightning report) shows strong success rates in certain setups, yet your mileage depends on wallet, liquidity, and counterparties.

My rule of thumb: optimize for what you actually do. If you send lots of small payments, align part of your stack with low-fee rails. If you mostly save, keep that core stable and liquid. You don’t need to pick a tribe to pick the right tool.

Green flags vs red flags in his tweets

• Green flags
  
  
  
  • Real merchant demos with a link to checkout or a donation page.
  
  
  • Reproducible tests: video or step-by-step with wallet, amount, and timestamp.
  
  
  • Open-source tools, code commits, or PRs you can read.
  
  
  • Fee screenshots alongside a public dashboard link (e.g., mempool, Blockchair).
  
  
  
  


• Red flags
  
  
  
  • Cherry-picked fee screenshots with no time, no vB rate, or cropped data.
  
  
  • Claims about “everyone accepts X” without a directory or checkout link.
  
  
  • Benchmarks from bull-run congestion presented as universally true.
  
  
  • One-off horror stories treated as proof the entire network “doesn’t work.”
  
  
  
  

Two fast samples I use constantly

• $2 coffee test
  
  
  
  • BCH: Send $2 via the Bitcoin.com Wallet. Note fee (usually tiny) and how quickly a merchant would accept a zero-conf payment for small purchases.
  
  
  • BTC on-chain: Check the current sat/vB, calculate the fee, and ask yourself if you’d pay it for a $2 item.
  
  
  • BTC Lightning: Try a $2 send in Phoenix or Breez. If you’re new, expect a one-time on-chain fee to open a channel or to receive inbound liquidity.
  
  
  
  


• Merchant reality check
  
  
  
  • See a tweet claiming “Merchant X takes BCH”? Open their checkout. If there’s no crypto option, look for a donation page or a regional partner link.
  
  
  • If it’s listed on AcceptBitcoin.cash, confirm it isn’t outdated. A single $1 test is worth 100 retweets.
  
  
  
  

A 3‑minute sanity loop I run before reacting

• Open fee dashboards (BTC and BCH) and record today’s numbers.


• Recreate the example with a tiny send (testnet where possible, or a nominal mainnet amount you’re comfortable risking).


• Screenshot your results with timestamp and links. If you can’t reproduce it quickly, save the claim for later—not your portfolio.

The result? I get all the upside—new wallets to try, fresh merchant intel, and a clear read on fees—without getting pulled into endless arguments. Because the real flex isn’t winning a thread; it’s paying someone instantly, cheaply, and on your terms.

Want my exact bookmarks, neutral dashboards, and wallet links so you can run these checks in seconds? That’s next—curious which ones I trust daily?

Key links, tools, and where I keep tabs

I keep a short, balanced stack of bookmarks so I can check claims in seconds, not hours. Here’s what I actually use when Roger posts something about fees, merchants, or payment UX, plus a few real-world examples you can try yourself.

Official and profile links

• Twitter/X: https://twitter.com/rogerkver


• Bitcoin.com (wallet, news, guides):
  bitcoin.com
  — wallet: wallet.bitcoin.com — news: news.bitcoin.com
  


• Wikipedia: Roger Ver

Balanced reading to round things out

• Neutral fee and network data (great for sanity checks):
  
  
  
  • BTC mempool and fee estimator: mempool.space
  
  
  • Cross-chain average fees and charts: bitinfocharts.com
  
  
  • Live throughput visualizer (BTC/BCH/ETH): txstreet.com
  
  
  • Bitcoin technical updates and fee context: Bitcoin Optech
  
  
  
  


• Lightning reality check (for comparing “everyday payments” claims):
  
  
  
  • Network explorer and routing stats: amboss.space
  
  
  • Engineering docs: Lightning Labs docs and Core Lightning docs
  
  
  • Independent research: River’s 2023 report on LN payment success rates and routing economics: river.com/research
  
  
  
  


• Bitcoin Cash resources (to verify the “peer-to-peer cash” angle):
  
  
  
  • Protocol/community hub: bitcoincash.org
  
  
  • Node docs and releases: bitcoincashnode.org
  
  
  • Explorer for checking fees/confirmations: explorer.bitcoin.com/bch
  
  
  
  


• Long-form context (skip the memes, get the arguments):
  
  
  
  • What Bitcoin Did — use the site search for “Roger Ver”: whatbitcoindid.com
  
  
  • Unchained Podcast — search for “Roger Ver” and “payments”: unchainedpodcast.com
  
  
  • Reddit — community AMAs and merchant reports: r/btc and r/Bitcoin
  
  
  
  

Real sample: When he says “fees are too high for coffee,” I open mempool.space to see current BTC sat/vB suggestions and USD fee estimates, then compare with BCH’s average fee on bitinfocharts and a live test payment using the Bitcoin.com Wallet. If the BTC mempool is congested, the estimate will reflect that. If BCH stays at a fraction of a cent, bitinfocharts shows it. It’s a quick way to separate a momentary spike from a structural issue.

Project docs and fee dashboards I trust

• BTC core references: developer.bitcoin.org, mempool/fee analytics at mempool.space, historical mempool stats at txstats.com


• BCH core references: BCHN docs, bitcoincashresearch.org


• Merchant directories and verification:
  map.bitcoin.com (BCH),
  acceptbitcoin.cash (BCH),
  coinmap.org (mostly BTC)
  


• Payment tooling docs:
  BTCPay Server,
  Prompt.Cash (BCH payment buttons),
  PayButton.cash (BCH),
  Bitcoin.com Wallet
  

Real sample: If a tweet highlights a new merchant integration, I check whether they’re listed on acceptbitcoin.cash or map.bitcoin.com. If they are, I send a tiny amount to the QR they display (when appropriate) and note the fee and confirmation experience. On the BTC side, I’ll replicate a small payment through BTCPay on-chain or over Lightning, using amboss.space to see if there are any routing constraints likely to affect success rate.

Tip: River’s 2023 Lightning report shows very high success rates for small payments on well-connected nodes. That doesn’t mean every wallet-user combo succeeds, but it’s a useful baseline when evaluating any broad claims about Lightning’s usability.

Extra resources from my vault

I keep a running, frequently updated list of neutral dashboards, fee trackers, and practical wallets here: Cryptolinks.com. Bookmark it. When the timeline heats up, it’s the fastest way to check reality before you retweet or rebalance.

Want the quick answers I give when people ask what he actually recommends, what his money philosophy really means for your day-to-day crypto use, and how I sanity-check it all in practice?

FAQ and my final take

What crypto does Roger Ver recommend?

Anything that works as peer‑to‑peer cash, with a consistent emphasis on Bitcoin Cash (BCH) because of low fees, simple UX, and a culture that encourages spending. That lines up with his reading of the original Bitcoin whitepaper’s “electronic cash” goal.

If you want to sanity‑check this in under five minutes, here’s what I actually do:

• Compare fees right now: Look at live BTC fees at mempool.space/fees and BCH fee history at BitInfoCharts (BCH fees). Historically, BCH median fees are tiny (often fractions of a cent), while BTC L1 fees vary with congestion.


• Do a $1–$5 test payment: Use a non-custodial BCH wallet (e.g., Bitcoin.com Wallet) and send a small amount. Then try the same on BTC L1 during a busy mempool; you’ll feel the difference in both fee and confirmation speed.


• Try a real purchase: BitPay supports BCH. A practical way to test is to buy a small e‑gift card in the BitPay/Bitcoin.com app using BCH. It settles fast and gives you a concrete “spent crypto” moment.

That quick loop will tell you more than any thread.

What is Roger Ver’s philosophy on money?

Libertarian and utility‑first. People should control their money, move it freely across borders, and pay with it without permission or a middleman. He prioritizes tools that keep transactions permissionless, low‑fee, and easy enough for everyday life—street markets, remittances, tipping, e‑commerce, and beyond.

Why this matters for you: if you care about crypto as spendable money (not just an investment), his lens will constantly push you to evaluate fees, UX, and settlement, not just price charts.

What companies has Roger Ver founded?

He founded MemoryDealers.com and later built and led Bitcoin.com for years. He’s also an early investor (not founder) in payments and exchange infrastructure, including BitPay, Kraken, and Purse.io. That’s why his feed leans hard into merchant tools, wallets, and real‑world usage.

Final thoughts: my simple reading strategy

If you follow his timeline for a month with this playbook, you’ll extract value without getting stuck in tribal crossfire.

• Screenshot claims with a timestamp and save the link. Fees, mempool congestion, and merchant policies change fast.


• Verify the numbers using neutral dashboards:
  
  
  
  • BTC fees and congestion: mempool.space/fees
  
  
  • BCH fee history: BitInfoCharts
  
  
  
  


• Reproduce payments with small amounts:
  
  
  
  • BCH L1: typically low fee, 0–1 block wait for confirmation, instant merchant detection.
  
  
  • BTC: compare L1 vs. Lightning. Lightning can be instant and cheap, but requires channel liquidity; custodial shortcuts add trust trade‑offs. For context, see network‑level stats like River’s research on Lightning performance: The Lightning Network in 2023.
  
  
  
  


• Check merchants, not just logos: If a tweet says “X accepts BCH,” look for a live checkout button or buy a small gift card through BitPay to confirm the stack actually works for you.


• Separate philosophy from tooling: You can appreciate the freedom/utility angle and still prefer different tech. Let the data—not the cheerleading—decide.


• Keep portfolio sanity: If you tilt toward payment coins, set a “payments sandbox” budget for experiments and keep core positions sized by liquidity, security model, and your risk plan.

Bottom line: follow for the payment‑first lens and hands‑on tests. When a claim sounds big, click the data, run a $1–$5 transaction, and see if it stands up. That habit will beat any thread—mine included.

CryptoLinks.com does not endorse, promote, or associate with Twitter accounts that offer or imply unrealistic returns through potentially unethical practices. Our mission remains to guide the community toward safe, informed, and ethical participation in the cryptocurrency space. We urge our readers and the wider crypto community to remain vigilant, to conduct thorough research, and to always consider the broader implications of their investment choices.