On September 10, Steak 'n Shake told the world that accepting Bitcoin had produced double-digit same-store sales growth. The press release was exactly the kind of headline crypto advocates love: a legacy American restaurant chain, famous for burgers and milkshakes, claiming that Bitcoin and Lightning Network adoption had turned around its stores.
No transaction hash was attached. No wallet address was shared. No payment processor was identified. No Bitcoin-denominated sales volume was disclosed. The only evidence presented was a corporate press release and a series of executive statements. Hashes don't lie. Wallets do. But in this case, Steak 'n Shake has not allowed the market to see either.
This is not an attack on the brand. It is an evidence review.
Context: a $14 burger with a Bitcoin wrapper
Steak 'n Shake is not a crypto startup. It is a nearly century-old American restaurant chain controlled by Biglari Holdings, with an average ticket price somewhere between $10 and $15. That matters. Small-ticket, high-frequency dining is the hardest use case for Bitcoin payments. Credit cards and cash already solve that problem with almost zero friction. Bitcoin, even over Lightning, still requires a wallet, a channel or a custodial app, and a customer who is willing to spend an asset that the broader market tells them to hold.
In May 2025, Steak 'n Shake began accepting Bitcoin through the Lightning Network. In September 2025, management announced what it framed as a triumph: total same-store sales rose at a double-digit rate, franchise same-store sales jumped 19%, the growth had accelerated from about 11% in the second quarter to roughly 15% in the third quarter, and those numbers supposedly put Steak 'n Shake ahead of McDonald's, Taco Bell, and Domino's. Management also claimed that processing costs fell by about 50%. The corporate parent separately authorized a Bitcoin treasury position of up to $10 million.
That is the entire observable dataset. It comes from a company with a direct interest in the story. There is no independent audit of the payment flow, no graph of Bitcoin transaction counts, no settlement record, and no accounting footnote that separates same-store sales growth from menu price inflation.
I have seen this shape before. In 2017, I spent four weeks reverse-engineering token distribution mechanics instead of reading ICO blog posts. In 2022, I watched stablecoins move out of Curve pools before Terra's collapse became a mainstream headline. The lesson is the same: follow the liquidity, not the narrative. The narrative here is attractive. The liquidity is invisible.
The evidence chain stops at a logo
Let's start with what is verifiable on-chain. The answer, in this case, is almost nothing.
A Lightning payment is not a public L1 transaction in the traditional sense. Lightning channels settle on-chain only when opened or closed. A customer can pay a $14 burger bill through a Lightning invoice without ever writing a visible series of small transactions to the Bitcoin base layer. That is by design. It also makes external verification nearly impossible for anyone outside the company.
If Steak 'n Shake wanted to prove that Bitcoin payments were a real driver, it could release aggregated Lightning settlement data. It could name its processor. It could show the volume of Bitcoin-denominated transactions per store, the average ticket size by payment method, or the exchange rate at which bitcoin was converted into dollars. None of that is present.
On-chain truth is better than Twitter narrative. But for a Lightning-based merchant, even on-chain truth is only partial truth. The company is asking the market to trust an internal conclusion without providing the underlying raw material.
That is a red flag, not because the company is necessarily lying, but because the claim is unfalsifiable from outside. In forensic analysis, an unfalsifiable claim is not the same as a true claim. It is simply a claim that cannot be tested.
The yield math on a milkshake
The centerpiece cost claim is a 50% reduction in payment processing fees. In a restaurant environment, that sounds meaningful. Let's look at the actual arithmetic.
Traditional credit card processing in the restaurant sector typically costs between 2.5% and 3.5% of the transaction. A Bitcoin payment processor that converts Lightning payments to fiat usually charges somewhere in the range of 0.5% to 1%, depending on volume, monthly minimums, and settlement terms. If the comparison is 3% card fees versus 1.5% Bitcoin processor fees, the press release can honestly claim a 50% reduction.
But that comparison is too clean. The real payment stack has more components. The merchant of record must handle tax reporting, refunds, chargebacks, compliance, and custodial risk. If Steak 'n Shake uses a third-party processor, that processor becomes the entity responsible for money transmission licenses and anti-money-laundering obligations. If the restaurant instead runs its own Lightning infrastructure through BTCPay Server or a similar self-custodial stack, the company takes on custody risk, private key management, employee training, and a volatile Bitcoin balance.
Neither path is free. Fragmented yields, fragmented trust. The same problem that fractured DeFi lending in 2020 applies to a burger chain's payment stack. Every store, every settlement route, and every wallet configuration creates a different cost curve. Adding all of those pieces into a single '50% savings' claim requires assumptions that have not been disclosed.

There is also a mismatch between ticket size and operational overhead. If a credit card transaction costs 3% of a $14 meal, the merchant pays roughly 42 cents. If a Bitcoin payment costs 1%, the merchant pays 14 cents. The gross savings is 28 cents per transaction. That is real, but it is not transformational. To generate meaningful dollar savings, Steak 'n Shake would need tens of thousands of Bitcoin transactions per week. There is no evidence that this is happening.
Based on my experience auditing payment flows and yield structures, I assume that the 50% number is a gross savings estimate, not a net savings number. It probably excludes the cost of accounting systems, tax compliance, treasury volatility, and the legal work required to make Bitcoin payments work across multiple states. If those costs are included, the real savings could be closer to zero.
Same-store sales is not same-store traffic
Now to the core marketing claim: double-digit same-store sales growth. In the restaurant industry, same-store sales is a revenue metric. It measures how much money existing locations generate compared with the prior year. It does not measure customer traffic. It does not measure Bitcoin usage. It does not even necessarily measure operational health.
Same-store sales can rise because the company raised menu prices. It can rise because the store base was cleaned up and poorly performing locations were closed. It can rise because the prior year was catastrophically weak. Each of these mechanical explanations can exist independently of Bitcoin acceptance.
Steak 'n Shake, under Biglari Holdings, has spent years restructuring. The franchise system has shrunk, shifted, and changed ownership structures. When a chain is coming off a low base, a 19% same-store sales increase is less impressive than it sounds. The relevant question is not whether sales went up. The relevant question is whether Bitcoin was the cause, a contributor, or a bystander.
Management says the growth was driven by Bitcoin adoption. But the company has not separated Bitcoin users from cash users. It has not disclosed whether Bitcoin-paying customers visited more often, ordered more items, or tipped differently. It has not provided a regression that controls for store closures, local marketing, menu innovation, or inflation. Without those controls, the announcement is an exercise in post hoc attribution.
I learned that during DeFi Summer in 2020. When I mapped Uniswap v2 liquidity pools, I found that reported yields were rarely realized yields. The theoretical APY looked stunning until impermanent loss and slippage were added to the ledger. The same applies here. A same-store sales number is a theoretical yield unless you can decompose the price effect, the volume effect, and the new customer effect. Steak 'n Shake has offered none of that decomposition.
The comparison to McDonald's, Taco Bell, and Domino's is also suspect. McDonald's operates tens of thousands of stores with enormous scale. Its same-store sales percentages move in single digits. Steak 'n Shake's store base is a fraction of that size. Smaller chains can post bigger percentage swings because a handful of successful newly renovated stores can move the entire average. Comparing percentage growth across different scales is a narrative trick, not an analytical framework.
The $10 million treasury is easier to count
The one concrete financial fact in this story is the decision by Biglari Holdings to authorize a Bitcoin treasury position of up to $10 million. That is a balance sheet event, not a payments event. It belongs to a separate trend that began with MicroStrategy and has now spread to traditional companies.
A $10 million Bitcoin reserve is not trivial for a restaurant holding company, but it is also not material in the global Bitcoin market. Bitcoin trades billions of dollars per day. A one-time purchase of $10 million would be absorbed within minutes. The promotional value of announcing the treasury position is probably larger than the market impact of the position itself.

There is a deeper problem: if Steak 'n Shake holds Bitcoin on its balance sheet, every Bitcoin payment it accepts is a decision to sell a future reserve asset. Management wants customers to use Bitcoin as a payment rail while simultaneously telling shareholders that Bitcoin is a strategic store of value. Those two messages are in tension.
If Bitcoin is expected to appreciate, a customer who pays for a burger with Bitcoin is realizing a loss of future purchasing power. If Bitcoin is merely a low-cost payment rail, the company should not need to hold a $10 million inventory of Bitcoin on its balance sheet. It could simply accept Bitcoin and instantly convert to dollars through a processor. The decision to hold Bitcoin exposes the company to mark-to-market volatility. Under fair value accounting rules adopted for crypto assets, that volatility must eventually flow through the financial statements.
A 30% drawdown on a $10 million Bitcoin position would create a $3 million unrealized loss. How many burger transactions must Steak 'n Shake process to earn $3 million? At roughly $14 per ticket, even with a 10% pre-tax margin, the company would need more than two million burger transactions just to offset the paper loss on a position that is not directly related to its core business. The fee savings argument becomes mathematically trivial compared to the treasury risk.
Regulatory complexity hides in the background
The regulatory status of Bitcoin is clearer in the United States than for most crypto assets. Bitcoin is generally treated as a commodity, not a security. That removes the most obvious securities-law problem. But Bitcoin payments still produce tax events, money transmission questions, and state-level compliance burdens.
When a customer pays for a burger with Bitcoin, the merchant receives an asset at a specific fair market value. For tax purposes, that is a taxable receipt. The merchant must record the value of the Bitcoin on the date of receipt and track any subsequent gain or loss when the Bitcoin is sold or converted. For a restaurant with hundreds of locations, that creates an accounting workflow that every small ticket must pass through.
The task is manageable if the payment processor automatically converts Bitcoin to dollars and provides a clean fiat settlement report. But if the company holds Bitcoin and manages its own wallets, the tax and accounting complexity expands. Employees need custody procedures. The finance department needs wallet reconciliation. The audit team needs to verify private key controls.
None of that overhead has been included in the publicly announced fee savings number. And none of it is visible in the headline story about double-digit sales growth. In this sense, the press release is not wrong in what it says. It is wrong in what it omits.
Also unresolved is the money transmission question. If Steak 'n Shake receives Bitcoin directly from customers and later sells it, the company may trigger money transmitter obligations in certain states. If a third-party processor handles the transaction and the conversion, that burden shifts to the processor. The company has not said which structure it uses. The structure determines whether the compliance cost is low and simple or high and painful.
When a firm reports a 50% processing fee reduction without mentioning its processor or its licensing posture, that is not a technical detail. That is the missing piece of the forensic record.
The promotional material also contains smaller credibility problems. One executive's comments supposedly tie the campaign to a Bitcoin conference that, from a September 2025 vantage point, is still in the future. The same announcement refers to a 'Chief MAHA Officer,' a title that does not exist in conventional restaurant management and looks more like internet-culture branding than an actual operations role. A timeline slip and a novelty title do not prove that the sales data are false. But they do prove that this story was built for narrative velocity, not for auditability.
The contrarian angle: Bitcoin is the wrong cause and the wrong direction
The obvious bullish narrative is that accepting Bitcoin caused customers to spend more money at Steak 'n Shake. There is a plausible contrarian version that points in the opposite direction.
Bitcoin holders who bought the asset as digital gold are likely to be reluctant spenders. Their incentive is to accumulate Bitcoin and defer consumption. A Bitcoin maximalist with a $10 million treasury position should not want to spend his Bitcoin on a burger. If anything, the ideal customer for a Bitcoin-accepting restaurant is not the Bitcoin hodler. It is the curious mainstream customer who heard about the novelty and wants to try something new.
That makes the sales bump a marketing event, not a payments revolution. The announcement itself creates free publicity. The logo on the door attracts attention. Customers come in, ask questions, maybe pay with a credit card and feel more favorable about the brand because it seems innovative. The actual Bitcoin payment may be the smallest part of the sales effect.
If that is true, the correct business conclusion is not that Bitcoin acceptance drives same-store sales. It is that crypto-friendly branding drives same-store sales. Competitors can copy that branding without copying the underlying payment rail. They can issue a press release, add a Lightning button, and create the same halo effect within weeks. The structural moat is not the Lightning channel. It is the media cycle.
The contrarian risk to the market is not that Steak 'n Shake's announcement will fail. The contrarian risk is that it will succeed for reasons unrelated to Bitcoin and then be cited by other companies as proof that accepting Bitcoin is a profitable operational strategy. That is how narrative contagion spreads. A single promotional data point becomes an industry trend without any independent validation.
What a real evidence release would look like
A data-driven follow-up would include four items:
First, the company would disclose the number of Bitcoin transactions per store per month and the average ticket size for Bitcoin payments. That alone would reveal whether this is a meaningful payment channel or a rounding error.
Second, the company would name its Lightning processor and settlement model. Did it auto-convert to dollars at the point of sale, or did it accumulate Bitcoin before selling? Without that answer, the fee savings claim is untestable.
Third, the company would separate same-store sales growth into price increases and customer traffic. A same-store sales metric that includes a 5% menu price increase cannot be treated as a clean signal of Bitcoin-driven demand.
Fourth, the company would disclose whether the $10 million Bitcoin treasury was purchased all at once or accumulated over time. The cost basis and the average purchase price matter. They also matter for the company's future willingness to continue accepting Bitcoin.
None of these data points would compromise the company's competitive position. Every restaurant knows whether its customers are paying with dollars or Bitcoin. Every payment processor knows what percentage of transactions settled through Lightning. The absence of these disclosures is a silence that speaks louder than the press release.
Takeaway: watch the footnote, not the headline
This story is not a breakthrough in Bitcoin protocol design. It is an experiment in brand positioning. Lightning Network has reached the point where a traditional restaurant chain can integrate it through standard APIs, and that is genuinely notable. But technical integration is not the same thing as financial materiality.
The next signal to watch is not the next Bitcoin conference speech. It is the next earnings footnote. If Steak 'n Shake or Biglari Holdings discloses Bitcoin transaction volumes, settlement processor, or treasury purchase details, then the market can begin to test the relationship between Bitcoin acceptance and same-store sales. If the company continues to report only percentages and anecdotes, treat the story as marketing.
Follow the liquidity, not the narrative. In this case, the narrative is everywhere and the liquidity is nowhere. On-chain truth matters more than Twitter hype. A burger paid for in Bitcoin leaves a footprint, but without the company's own ledger, that footprint is as hard to read as a receipt printed in disappearing ink.