Steak 'n Shake's 19% Same-Store Sales Claim: A Forensic Teardown of the Bitcoin Payment Narrative
On September 10, Steak 'n Shake published a number to its X account that the crypto press corps swallowed whole: double-digit same-store sales growth, with franchised locations posting a 19% bump. Within hours, the timeline was awash in screenshots, quote-tweets, and the familiar cadence of a narrative being born. A burger chain had accepted Bitcoin through the Lightning Network in May 2025. Four months later, the numbers supposedly proved it worked.
I have spent the better part of a decade dissecting these announcements, and my first instinct is never excitement. It is suspicion. A 19% same-store sales figure for a legacy American diner chain โ average ticket somewhere between ten and fifteen dollars โ is not a number that emerges cleanly from a payment-rail decision. It emerges from menu pricing, marketing exposure, promotional cycles, and a dozen variables the company did not disclose. The Bitcoin adjacency is the headline. It is almost certainly not the cause.
This is where most coverage stops. Mine does not. What follows is a full dissection of the Steak 'n Shake claim across seven surfaces: the technical integration, the token and treasury logic, the market mechanics, the ecosystem position, the regulatory exposure, the human cost accounting, and the contrarian case for why the bulls may be partially right despite themselves. Cold hands dissect the heat of a hype cycle. Let us begin.
Context: What Steak 'n Shake Actually Is
Before we dissect anything, we need to establish the substrate. Steak 'n Shake is not a startup. It is not a crypto-native brand trying to bootstrap liquidity. It is an 80-plus-year-old American hamburger and milkshake chain, headquartered in Indianapolis, historically positioned as a value-priced, sit-down casual diner. Its average customer is not a Bitcoin holder. Its average transaction is not a settlement-grade transfer. Its franchise network is a sprawling, uneven collection of regional operators, each with their own P&L pressures, staffing realities, and tolerance for operational complexity.
The chain's parent, Biglari Holdings, is itself a curious creature โ a publicly listed holding company (NYSE: BH) that operates Steak 'n Shake alongside other restaurant and insurance assets. Sardar Biglari, the chairman, has a long track record of activist capital allocation, contrarian bets, and an allergy to conventional corporate communication. When Biglari announces something, it tends to be loud, idiosyncratic, and under-documented. This is a man who once ran an entire shareholder letter campaign around the concept of being undervalued. He is not afraid of a headline.
In March 2025, Biglari Holdings announced a plan to allocate $10 million of corporate treasury into Bitcoin as a strategic reserve asset. In May 2025, Steak 'n Shake began accepting Bitcoin for in-restaurant purchases, with the technical settlement running through the Lightning Network. By September, the company was publicly claiming that same-store sales had accelerated into double digits, with franchised locations at 19%. The narrative crystallized: Bitcoin adoption drives restaurant growth.
I want to be explicit about my epistemic posture here. This analysis will operate across three tiers โ what the company has explicitly stated, what can be reasonably inferred, and what is high-octane speculation. Several of the most important figures in this story โ the 50% processing-fee savings, the attribution of same-store growth to Bitcoin, the competitive rankings โ originate solely from the company's own communications. There is no third-party audit. There is no POS-level data disclosure. There is no breakdown of Bitcoin transaction volume as a percentage of total revenue. When a company is both the actor and the scorekeeper, the scoreboard is a marketing instrument, not a measurement.
The second thing I noticed when I pulled the original material was a timeline contradiction buried in the footnotes. One reference point cites Michael Boes โ identified as a "Chief MAHA Officer" โ speaking at the Bitcoin 2026 conference. That conference cannot have occurred by September 2025, because the Bitcoin annual gathering is held in late May. The reference is either a transcription error, a forward-dated placeholder, or a fabricated detail. None of those possibilities are flattering to the source material. And the title "Chief MAHA Officer" does not map to any conventional executive role in restaurant operations, finance, or technology. It reads like a brand-constructed title from a Web3-adjacent playbook, which raises the question of how much of this story is being engineered forๅไบ rather than disclosure.
With those caveats established, let us dissect.
Core: The Technical Integration Is Real, and That Is Not the Interesting Part
Strip away the marketing and the Lightning Network integration is technically unremarkable. This is the first thing the bulls will not admit and the first thing the bears misunderstand. Steak 'n Shake did not build anything. It integrated an existing payment rail, most plausibly through a third-party service provider โ OpenNode, Strike, or a similar merchant-focused Lightning processor โ and connected that to its existing point-of-sale systems.
The architecture almost certainly looks like this:
A consumer holding Bitcoin opens a Lightning channel through their wallet โ Strike, Cash App, Phoenix, or a Custodial option like Coinbase. They scan a QR code or tap an NFC terminal at the register. The payment routes through the merchant's chosen processor, which either holds the Bitcoin, converts it to fiat in real time, or passes it into the restaurant's treasury operation. The restaurant receives a settlement, typically in dollars, minus a processing spread. The customer's Bitcoin leaves their custody. The register rings up a hamburger.
This is not novel. El Salvador mandated Bitcoin acceptance in 2021. Jersey Mike's began accepting Bitcoin through a similar integration in 2024. Starbucks ran Lightning pilots through Bakkt years ago before quietly scaling back. What Steak 'n Shake has done is not a technology milestone. It is a commercial integration โ the kind of thing that becomes routine when the underlying tooling matures enough that a non-technical restaurant operator can flip it on without hiring a blockchain engineer.
That maturity is genuinely worth noting, and I will credit it. The Lightning Network in 2025 is a fundamentally different beast from the Lightning Network of 2019. Channel liquidity routing, watchtowers, submarine swaps, and merchant SDKs have all progressed to the point where a national chain can run Bitcoin payments through a managed provider with minimal operational drag. The barrier to entry has collapsed. When I audited merchant crypto integrations in 2020 and 2021, the dominant failure mode was operational: reconciliation chaos, tax tracking gaps, cashier confusion, and settlement latency. Most of that has been abstracted away by the current generation of providers.
But here is where the company's own claims begin to strain under their own weight. The announcement cites a 50% reduction in payment processing fees โ a comparison against the roughly 2.5% to 3.5% that credit card networks extract from merchants. A 50% saving would imply Steak 'n Shake is now paying 1.25% to 1.75% per transaction. That figure is only achievable under two specific conditions, and the disclosure does not tell us which one applies.
Condition one: the company uses a self-hosted, zero-fee solution like BTCPay Server, holds the Bitcoin on its own balance sheet, manages its own cold and hot wallets, and accepts the price volatility and liquidity management burden that comes with it. That would explain a dramatic fee reduction, but it would also mean Steak 'n Shake is now running a treasury operation that requires dedicated personnel, custody security, accounting infrastructure, and continuous liquidity provisioning.
Condition two: the company uses a managed Lightning processor that charges somewhere between 0.5% and 1%, but the 50% figure is being calculated against a blended average that includes higher-fee card mix. In that case, the "savings" is really a comparison between two different baskets of payment methods, not a pure Lightning-vs-Visa differential.
The disclosure does not distinguish between these scenarios, and that omission is the tell. A company genuinely proud of a 50% cost reduction would publish the underlying fee schedule, the transaction volume, and the settlement structure. Steak 'n Shake published a percentage and moved on.
The Verification Problem
There is a deeper structural issue that almost no coverage has touched. Lightning Network payments are, by design, resistant to third-party observability. Channel balances are private. Routing is onion-layered. A merchant receiving Lightning payments does not generate a publicly auditable on-chain trail the way a Bitcoin L1 transaction does. This means that even a determined forensic analyst cannot independently verify how many Bitcoin transactions Steak 'n Shake actually processed in May, June, July, or August 2025. The company's claim โ that Bitcoin acceptance contributed to same-store growth โ is, from an external verification standpoint, unfalsifiable.
Unfalsifiable claims are not automatically false. But they are structurally protected from scrutiny, and entities making unfalsifiable claims have strong incentives to overstate them. When I audited the Yearn Finance vault strategies during DeFi Summer, the discrepancies I found were not in the headline APY figures โ they were in the slippage calculations buried two layers down in the strategy logic. The headline number was always plausible. The reality was always more complicated.
Here, the headline is a 19% same-store sales figure for franchised locations. The reality is that we cannot see the transaction log, we cannot see the fee ledger, and we cannot see the Bitcoin revenue as a percentage of total sales. We are asked to accept the causal claim on faith. I do not accept causal claims on faith. I accept them on data, and the data is not there.
Core: The Treasury Logic Is Where the Risk Actually Lives
The $10 million Bitcoin treasury allocation is the part of this story that deserves the most attention, because it is the part with the largest potential downside for the company's actual financial health โ and the part that is most likely to be underweighted by the retail investors now watching the stock.
Let me be precise about what a $10 million Bitcoin reserve means for a company of Steak 'n Shake's scale. Biglari Holdings is not MicroStrategy. It does not have a multi-billion-dollar market capitalization and an equity base large enough to absorb a 60% drawdown in a single asset class without consequences. A $10 million allocation for a mid-cap restaurant holding company is a meaningful balance-sheet exposure, not a rounding error.
Under US GAAP, as amended by FASB's ASU 2023-08, companies holding crypto assets are required to measure them at fair value, with changes flowing through net income. That rule took effect for fiscal years beginning after December 15, 2024. For a company that books the reserve, every Bitcoin price swing becomes a reported earnings swing. If Bitcoin trades from $100,000 to $70,000 in a quarter, that is a $3 million non-cash loss hitting the income statement on a $10 million position โ a 30% impairment that has nothing to do with how many milkshakes were sold.
Yield is a sedative; volatility is the needle. The Bitcoin reserve may look like a yield-generating strategic asset on the way up. It looks like a reported loss generator on the way down. And the way down is not a hypothetical โ Bitcoin has historically experienced multiple 70%+ drawdowns within single market cycles. A restaurant holding company that puts 100% of its announced crypto reserve into a single non-yielding, fair-value-measured asset is not diversifying. It is concentrating.
Here is the accounting recursion that nobody is discussing. If the same-store sales growth is partially attributable to Bitcoin adoption, and the Bitcoin reserve is marked to market through earnings, then a Bitcoin price decline simultaneously: (a) reduces the treasury value, (b) hits reported net income, (c) potentially dents consumer confidence in the Bitcoin-payment experience, and (d) pressures management to reconsider the whole strategy. These effects compound. The strategy that looks accretive in a bull market becomes serially corrosive in a bear.
I have seen this movie before. In 2021, during the NFT NYC circuit, I watched projects pile into crypto reserves and treasury strategies that looked brilliant for two quarters and became existential liabilities by the third. The mechanism is always the same: the treasury reinforces the narrative, the narrative drives the headline, the headline attracts the retail flow, and the retail flow masks the structural fragility until it does not.
Now, in fairness to Biglari Holdings, the $10 million figure is small enough that a severe drawdown would not threaten solvency. This is not Terra/Luna. There is no algorithmic peg to break, no reflexive death spiral. The company can absorb a bad Bitcoin year. But the question is not whether the company survives. The question is whether the causal story being told โ Bitcoin adoption drives restaurant growth โ survives the next mark-to-market cycle. And that story is entirely dependent on a variable that no restaurant operator controls.
Core: The Market Reaction Is the Story Nobody Is Telling
Let me shift to what actually moved, because this is where the honest analysis diverges most sharply from the crypto-media version of events.
When Steak 'n Shake published its same-store sales figures, the price of Bitcoin did not move meaningfully. That is not a criticism of the announcement. It is a simple fact of market mechanics. Bitcoin trades somewhere in the range of $1.5 to $2 million per day per major venue, and the aggregate daily spot volume across global markets runs into the tens of billions. A few dozen hamburger-related Lightning transactions, or even a few thousand, are statistical noise against that backdrop. The marginal impact of a single restaurant chain accepting Bitcoin on the spot price of Bitcoin is approximately zero.
This is a point that the crypto-enthusiast press corps routinely fails to internalize. Merchant adoption narratives are emotionally satisfying but economically trivial at the price level. The assets that move on this kind of news are not Bitcoin. They are the payment processors โ OpenNode, Strike, and the smaller-cap public entities with Bitcoin-adjacency exposure. If you were positioning for this event, you would not have bought Bitcoin. You would have looked at the merchant-acquiring stack and the Lightning infrastructure layer.
What did move โ or at least what deserves attention โ is the equity narrative around Biglari Holdings itself. The company is publicly listed. A double-digit same-store sales headline, regardless of its attribution, is a legitimate operational signal. If the numbers are real and sustainable, they represent a genuine turnaround in a legacy brand that had been struggling with foot traffic and franchisee economics for years. The Bitcoin angle may be the marketing frame, but the operational improvement, if real, is the substance.
And here is where I want to flag a gap in the public reporting. Most coverage conflated two very different claims: (1) Steak 'n Shake's same-store sales grew, and (2) Bitcoin acceptance caused that growth. Claim (1) may be true. Claim (2) is unproven and, given the base-rate math, unlikely to be the primary driver.
Consider the mechanics of same-store sales growth in the restaurant industry. It decomposes into two components: traffic (more customers) and ticket (higher average spend). A 19% same-store sales increase could be 5% traffic and 14% ticket, or 19% ticket and flat traffic, or some combination. In a high-inflation environment โ and 2025 US food-away-from-home prices remained elevated โ a significant portion of same-store sales growth across the industry was driven by menu price increases rather than customer count. If Steak 'n Shake raised prices 10% to 12% and gained modest traffic, it could manufacture a double-digit same-store number without any Bitcoin effect at all.
The company did not disclose the traffic-versus-ticket split. It did not disclose Bitcoin transaction volumes. It did not disclose the geographic distribution of the supposed Bitcoin-driven demand. The absence of these disclosures is not an accident. It is the selective-release pattern of a company that wants the headline without the audit.
Core: The Ecosystem Position Is Thinner Than It Looks
Steak 'n Shake's role in the Bitcoin ecosystem is best understood as a capillary, not an artery. It is a consumer-facing endpoint that connects ordinary retail transactions to the Lightning Network, and that connection has some value โ it expands the practical utility of Bitcoin as a medium of exchange and provides real-world merchant data to the payment processors. But it is not infrastructure. It is not a moat. It is not a strategic position that competitors cannot replicate in a weekend.
Any restaurant chain can integrate OpenNode or BTCPay Server. Any regional operator can flip on Lightning payments through a managed provider. The technical integration is a commodity. The only thing Steak 'n Shake has that a competitor does not is the first-mover brand story โ the "America's first major burger chain to accept Bitcoin" narrative โ and that story has a half-life measured in months, not years.
There is also a meaningful distinction between a Bitcoin-accepting merchant and a Bitcoin-native merchant. Steak 'n Shake accepts Bitcoin. It does not build on Bitcoin. It does not custody user keys, does not run a Lightning node as a routing service, does not offer Bitcoin-denominated rewards, does not settle with suppliers in Bitcoin, and does not create any Bitcoin-based financial product. The integration is one-directional: consumer spends Bitcoin, restaurant receives fiat. There is no circular economy here, no loop that reinforces itself. Assets don't circulate in a one-way payment pipe. They just pass through.
Compare this to the way a genuinely Bitcoin-native business operates. Strike's merchant network routes settlement through Bitcoin rails and offers merchant treasury options denominated in BTC. The Bitcoin mining operators I have audited hold their treasury in BTC and transact with suppliers in kind. Those are businesses whose operating model is structurally tied to the asset. Steak 'n Shake's operating model is tied to hamburgers. Bitcoin is a payment rail and a marketing story. That is a meaningful distinction when you are trying to assess whether the strategy is durable or theatrical.
The Franchise Problem
There is a structural complication the headline numbers obscure: franchise economics. Steak 'n Shake operates a mixed model of company-owned and franchised locations. When the company reports a 19% same-store sales increase for franchised locations โ higher than the aggregate โ it is reporting a number that is shaped by franchisee-level decisions about pricing, promotion, and operations, not by the parent company's Bitcoin strategy alone. Franchisees have autonomy over their menus, their pricing, and their technology adoption. If a franchised location has not integrated the Lightning payment system, its sales are unaffected by the Bitcoin narrative entirely.
The 19% franchised figure is, in other words, an aggregate of locations with widely varying degrees of exposure to the company's crypto initiatives. It is a number that cannot be cleanly attributed to any single cause, and it is being presented as though it can. This is the statistical sleight-of-hand that should make any analyst pause.
Core: The Regulatory and Accounting Overhang Is Real
Bitcoin is not a security. That much is settled in the United States โ the CFTC treats it as a commodity, and the SEC has publicly distinguished it from securities. So the classic Howey-test analysis that dominates crypto legal commentary is largely moot here. Steak 'n Shake does not face securities-law risk from accepting Bitcoin or holding it in reserve.
But that is where the comfort ends.
The real regulatory exposure sits in three operational buckets: money transmission, tax accounting, and consumer protection.
On money transmission: accepting Bitcoin directly from a consumer is generally outside the scope of money transmitter licensing, because the merchant is selling goods, not transmitting funds on behalf of a third party. But the moment a third-party payment processor is involved in holding or converting the customer's Bitcoin, that processor needs state-level money transmitter licenses across the jurisdictions it operates in. Steak 'n Shake almost certainly routes through a licensed processor, which shifts the direct compliance burden but introduces dependency risk. If the processor's license is challenged, or if it changes fee schedules, the merchant is exposed.
On tax accounting: this is the underreported cost center. Every Bitcoin acceptance is a taxable event. The merchant must record the fair market value of the Bitcoin at the time of receipt, track it through the settlement process, and recognize any gain or loss on the subsequent disposition if the Bitcoin was held for any period. This requires accounting infrastructure that most restaurant POS systems are not natively built to provide. Steak 'n Shake โ or its processor โ must be running fair-value tracking on every transaction. That is not free. That is a per-transaction and per-period cost that does not appear in the marketing slide.
On consumer protection: state-level regulations around digital asset transactions are a patchwork. Some states have adopted comprehensive frameworks; others have not. A multi-state restaurant operation accepting Bitcoin must navigate this inconsistent landscape, and its ability to do so without running afoul of at least one jurisdiction's rules is not guaranteed.
The 50% Claim Under a Full-Cost Lens
Here is where I want to apply the discipline that the company's own disclosure avoids. The "50% processing fee savings" is presented as a gross comparison between Lightning fees and card fees. But the honest comparison is a full-cost accounting, which includes:
- The processor's per-transaction spread (0.5% to 1%)
- The cost of fair-value accounting infrastructure and personnel
- The cost of Bitcoin treasury management and custody security
- The liquidity cost of holding or converting BTC positions
- The cost of employee and franchisee training
- The cost of any regulatory or tax advisory work
- The opportunity cost of treasury capital locked in a non-yielding, volatile asset
When those lines are added, the marginal cost advantage of Bitcoin acceptance over card rails narrows considerably. At low transaction volumes, the fixed cost of Bitcoin infrastructure can exceed the variable savings entirely. The 50% figure is a variable-cost comparison masquerading as a total-cost claim. That is a material misrepresentation, even if it is not intentional.
Core: The Human Layer Nobody Wants to Audit
There is a tendency in technical analysis to treat these stories as abstract systems โ nodes, channels, treasuries, rate structures. But every system is ultimately a collection of humans making decisions under uncertainty. And the human layer of this story is the part that deserves the most careful attention.
Let me tell you about the people this narrative touches. In 2021, I attended NFT NYC and met a group of Axie Infinity players who had lost their life savings to a phishing site. I traced the smart contract interaction logs and proved the exploit was signature spoofing, not a protocol bug. I wrote a blunt thread exposing the negligence. That experience made me permanently allergic to stories that celebrate adoption without accounting for the humans at the bottom of the stack.
Who are the humans in the Steak 'n Shake story?
First, the franchisees. They are the ones who bear the operational cost of Bitcoin integration โ the training, the reconciliation, the tax complexity โ while the parent company gets the headline benefit. If the integration does not work smoothly, they are the ones fielding confused customers at the register. If the accounting is wrong, they are the ones facing audit exposure. The corporate announcement does not describe franchisee obligations, franchisee costs, or franchisee consent. We audit the code, but we mourn the users โ and here the users are the small-business operators wearing the brand's logo.
Second, the ordinary customers. The overwhelming majority of Steak 'n Shake customers do not hold Bitcoin. They will never use the Lightning payment option. They are, in a sense, invisible to this narrative โ except that they will bear any cost that gets passed through. If Bitcoin integration adds operational complexity that requires the menu to be re-priced, they pay. If the company's treasury losses pressure margins, they pay. The public-told story of crypto adoption rarely accounts for the non-crypto majority who subsidize it.
Third, the crypto-native customers who genuinely want to spend Bitcoin. For them, this integration is a small pleasure. They get to buy a milkshake with sats. That is a real, if minor, quality-of-life improvement, and it deserves acknowledgment. But the emotional satisfaction of that transaction should not be confused with evidence that the integration is economically meaningful for the company.
Contrarian: What the Bulls Actually Got Right
I have spent the bulk of this piece dismantling the Steak 'n Shake narrative, and I want to be honest about the parts that hold up โ because a forensic analysis that only cuts is not forensic. It is polemic.
The bulls are right about one thing, and it is more important than they realize. The operational maturing of the Lightning Network is real, and Steak 'n Shake's ability to integrate it without a dedicated engineering team is meaningful evidence of that maturation. Three years ago, a legacy restaurant chain integrating Bitcoin payments would have required a technology partner, significant development work, and a willingness to absorb operational risk. Today, it can happen through a managed provider with minimal friction. That shift is real, and it is worth respecting.
The bulls are also right that consumer-facing adoption has a signaling value that goes beyond the transaction volume. When a mainstream brand normalizes crypto payments, it reduces the psychological barrier for other merchants and for consumers. That normalization effect compounds slowly, and it is genuinely valuable to the ecosystem over a multi-year horizon. A single restaurant chain does not move the needle. A thousand do. The path to a thousand starts with the first few.
And finally, the bulls are right that Steak 'n Shake's same-store sales improvement, whatever its cause, is a real operational signal. A legacy chain posting double-digit growth in a difficult restaurant environment is notable. If the company can sustain it, the story is interesting on its own merits โ with or without Bitcoin.
Where the bulls go wrong is in the causal leap. They take a plausible mechanism (Bitcoin acceptance โ brand buzz โ foot traffic) and treat it as a proven effect. They do not ask for the transaction data. They do not ask for the traffic-versus-ticket decomposition. They do not ask whether the same-store improvement predates the Bitcoin integration. They accept the narrative because the narrative is flattering to their priors, and that is the oldest trap in the book. I fell into it in 2017, when I put $3,000 into ICOs promising revolutionary AI tokens and ignored every fundamental signal that told me not to. I sold at a loss. That mistake made me what I am. The bulls have not yet had their 2017 moment, and until they do, they will keep accepting headlines.
Takeaway: The Accountability Question Nobody Wants to Ask
The real question is not whether Steak 'n Shake's Bitcoin integration worked. The real question is why we keep accepting unverifiable corporate claims as evidence of crypto adoption. The company gave us a percentage. It did not give us a ledger. It gave us a narrative. It did not give us a causal analysis. And we treated the percentage as if it were the ledger, and the narrative as if it were the proof.
There is a discipline that the crypto-analyst community applies when auditing protocols. We pull the transaction history. We verify the contract logic. We trace the flows. That discipline evaporates the moment the subject becomes a publicly traded company with a press release. We grant hospitality that we would never grant to an anonymous DeFi protocol, and we do it because the brand is familiar and the story is flattering. Cold hands dissect the heat of a hype cycle. Warm hands accept the press release.
So here is the accountability call for the next cycle. When a company claims that crypto adoption drove its business results, demand three things: the transaction volume, the revenue share, and the traffic decomposition. If the company will not provide them, treat the claim as marketing, not measurement. The Lightning Network is mature enough to be integrated. It is not mature enough to be a growth engine for a hamburger chain on its own. The operational story at Steak 'n Shake is interesting. The Bitcoin story is a frame. Do not confuse the two.
The next company to announce a double-digit same-store sales win "driven by crypto" will be tested by this standard. How they respond to the audit will tell you more about their strategy than any number they publish.
