Note: This article is for informational purposes only and explains a recent patent inventorship dispute in plain English. It is not legal advice, but it may help founders, engineers, inventors, and technology teams understand why documentation matters long before anyone shakes hands at a conference dinner.
Introduction: A Bitcoin Mining Dinner, Four Attachments, and a Patent Fight
Patent disputes are often dressed in formal language, but underneath the robes and citations, they can feel surprisingly human. Someone has an idea. Someone talks about the idea. Someone later sees a patent and says, “Wait a minutewasn’t that mine?” That is the basic heartbeat of BearBox v. Lancium, a Federal Circuit case involving cryptocurrency mining, energy markets, a conference conversation, a follow-up email, and the difficult question of who legally counts as an inventor.
The case centered on whether Austin Storms, founder of BearBox LLC, should have been added as an inventor to Lancium’s U.S. Patent No. 10,608,433, titled Methods and Systems for Adjusting Power Consumption Based on a Fixed-Duration Option Agreement. BearBox argued that Storms had shared key concepts with Lancium before the patent application was filed. Lancium disagreed, and the courts ultimately sided with Lancium.
On January 13, 2025, the U.S. Court of Appeals for the Federal Circuit affirmed the District of Delaware’s judgment against BearBox. The decision denied BearBox’s correction-of-inventorship claim, upheld the exclusion of a supplemental expert report, and affirmed that BearBox’s Louisiana conversion claim was preempted by federal patent law. In less legal language: BearBox did not prove that Storms conceived or communicated the claimed invention before Lancium independently did, and its state-law claim looked too much like an attempt to get patent-style remedies without a patent.
What Was the Technology About?
The technology at the center of the dispute sat at the intersection of cryptocurrency mining, flexible data centers, and electricity pricing. Bitcoin mining can consume a large amount of power, which means profitability depends heavily on energy cost. If power is cheap, miners may run. If power is expensive, miners may pause or reduce consumption. Simple enough in theory; in practice, it becomes a technical and contractual puzzle involving software, hardware, grid signals, power thresholds, and timing.
Lancium’s patent involved systems that adjust power consumption based on power option agreements. These agreements can specify minimum power thresholds and time intervals, and the computing system can determine a performance strategy based on that power data and other monitored conditions. Those conditions may include electricity prices, cryptocurrency economics, operational priorities, and grid-related inputs. In plain English, the system is designed to help computing loads behave more intelligently around energy availability and pricing.
BearBox, meanwhile, developed mobile cryptocurrency datacenter concepts. Storms had experience with Bitcoin mining and worked on systems that could control miners remotely. According to the court record, he met Lancium co-founder Michael McNamara at a Bitcoin mining industry event in Boston in May 2019. After a cocktail reception and dinner discussion, Storms sent McNamara one email with four attachments: a BearBox product specification sheet, an annotated diagram of BearBox’s Automatic Miner Management System, hardware specification sheets, and a data file modeling a simulation of the BearBox system.
That email became the star witness of the case. Unfortunately for BearBox, it did not perform like a star witness.
The Inventorship Claim: Why BearBox Lost
Correction of inventorship is possible, but the burden is heavy
U.S. patent law allows inventorship to be corrected after a patent issues. Under 35 U.S.C. § 256, a court may order correction when an inventor was wrongly omitted or someone was wrongly named. That sounds forgiving, and in some ways it is. Patent law recognizes that mistakes happen. However, when a person asks a court to change the inventors listed on an issued patent, the law does not simply take their word for it.
An issued patent carries a presumption that the named inventors are correct. To overcome that presumption, the challenger must present clear and convincing evidence. That is a demanding standard. It is not enough to say, “I talked about this first,” or “That sounds like my idea.” The alleged inventor must connect their contribution to the actual patent claims and must usually support their testimony with independent corroborating evidence.
Inventorship is tied to claims, not vibes
One practical lesson from BearBox v. Lancium is that inventorship is not awarded for general inspiration. Courts look at the claims of the patent. Did the alleged inventor contribute to the conception of at least one claimed invention? Was that contribution significant? Was it more than explaining known ideas, business goals, or industry background? Was the contribution communicated to the named inventors before they independently conceived it?
BearBox argued that Storms had either solely invented or jointly invented the subject matter of the ’433 patent. The district court held a three-day bench trial on inventorship and found that BearBox failed to prove the claim. The Federal Circuit affirmed, emphasizing that the evidence did not establish that Storms conceived the claimed invention or communicated the relevant claim subject matter before Lancium’s independent conception.
The courts paid close attention to what Storms actually shared. The strongest documentary evidence was the single May 2019 email and its four attachments. One attachment, involving fans and other hardware components, was not tied to the patent’s subject matter. The other materials did not show that Storms had conceived the claimed invention in the way the patent required, or they did not show communication before Lancium had already independently developed the relevant ideas.
The timing problem hurt BearBox
Timing was a major obstacle. The record showed that Lancium had been developing flexible datacenter technology and energy-responsive mining systems before Storms met anyone at Lancium. Lancium’s earlier work included concepts for ramping computing loads up or down based on power economics and operational conditions. The district court found that Lancium had independently conceived important claim elements before Storms’ May 2019 email.
This matters because even if an outsider later sends a document that overlaps with something in a patent, that does not make the outsider an inventor if the named inventors had already conceived the claimed subject matter. Patent inventorship is about original contribution to conception, not merely later overlap.
The Expert Report Issue: Too Late, Too Much
BearBox also challenged the district court’s exclusion of a supplemental expert report. Expert reports can be powerful in patent litigation, especially when technical details get dense enough to make normal people reach for coffee. But courts care deeply about deadlines, fairness, and whether a new report is truly a clarification or an attempt to introduce fresh opinions at the last minute.
BearBox argued that the supplemental report was justified because of claim construction developments. The Federal Circuit was not persuaded. It agreed that the report contained opinions beyond mere elaboration and that the district court did not abuse its discretion by excluding it. That procedural ruling mattered because inventorship disputes often depend on highly technical comparisons between alleged contributions and patent claim limitations.
The takeaway is straightforward: in patent litigation, timing is not a decorative calendar feature. It is part of the battlefield. A useful expert opinion that arrives too late may become legally useless.
The Conversion Claim: Why Federal Patent Law Preempted It
BearBox also claimed improper use of its technology
Alongside inventorship, BearBox brought a Louisiana state-law conversion claim. In ordinary terms, conversion involves wrongful control over someone else’s property. BearBox alleged that Lancium improperly used BearBox’s technical materials, documents, data, and know-how.
The problem was not simply that BearBox pleaded a state-law claim. State-law claims are not automatically preempted just because a case involves technology. Trade secret claims, contract claims, and confidentiality-based claims may survive when properly pleaded and supported. The problem was how BearBox’s claim functioned in this case.
The court saw “patent-like” protection without a patent
The Federal Circuit agreed that BearBox’s conversion claim, as pleaded, sought something too close to patent protection. BearBox used language associated with patent law, including allegations that Storms had “conceived,” “developed,” and “reduced to practice” the technology and that Lancium improperly used it. BearBox also sought remedies that resembled patent damages, such as recovery tied to Lancium’s use and monetization of the technology.
That created a federal preemption problem. U.S. patent law reflects a balance: inventions that meet patent requirements can receive patent protection, while unpatented and publicly available ideas generally remain free for public use. A state-law claim cannot be used to create a backdoor patent monopoly over technical information that is not protected by federal patent law.
The Federal Circuit’s reasoning followed the logic of Supreme Court precedent, including the principle that states cannot grant patent-like protection to unpatented ideas in a way that conflicts with federal patent policy. Because BearBox’s conversion theory was framed like an inventorship or infringement claim and sought patent-style remedies for unpatented technology, it was preempted.
Why This Case Matters for Founders and Inventors
BearBox v. Lancium is not just a crypto-mining patent case. It is a cautionary tale for anyone who pitches technology to investors, manufacturers, partners, vendors, conference contacts, or larger companies. The setting may involve wind farms and Bitcoin miners, but the lesson applies just as well to software startups, AI tools, hardware prototypes, biotech platforms, energy systems, and even that “small idea” someone casually explains over dinner.
1. File before you pitch when possible
If the technology is important enough to build a company around, it may be important enough to discuss with patent counsel before public disclosure. A provisional patent application is not magic armor, but it can establish an early filing date and create a cleaner record of what was invented and when. Pitching first and documenting later is the business equivalent of installing a smoke alarm after the toaster is already on fire.
2. Use confidentiality agreements strategically
Non-disclosure agreements are not always realistic at conferences, but they matter when detailed technical materials are exchanged. If a conversation moves beyond general business development into diagrams, source code, control logic, simulations, or technical specifications, the parties should think carefully about confidentiality. Without confidentiality, a later trade secret or misappropriation theory can become much harder to maintain.
3. Keep contemporaneous records
Inventorship disputes are evidence disputes wearing a lab coat. Courts want documents, dates, drafts, emails, source-code repositories, version histories, lab notebooks, meeting notes, and claim-by-claim support. A founder’s memory may be sincere, but sincerity is not the same as corroboration. The best records are created at the time, not reconstructed after litigation begins.
4. Understand the difference between an idea and a claimed invention
A broad idea like “control miners based on electricity prices” may be commercially useful, but patent claims are more specific. They may require particular data structures, thresholds, time intervals, control instructions, monitored conditions, or agreement mechanics. To prove inventorship, an alleged contributor must map their contribution to the claimed invention, not merely to the general business concept.
Practical Analysis: What the Court Was Really Saying
The Federal Circuit did not say that ideas shared at conferences never matter. It did not say that large companies may freely take confidential submissions. It did not say that omitted inventors have no remedy. Instead, the court said BearBox did not meet the legal standard on this record.
That distinction is important. Patent law is not built around who had the better story. It is built around proof. In this case, the proof had gaps. The court saw evidence that Lancium had already worked on relevant concepts before the May 2019 meeting. It saw only one follow-up email from Storms to McNamara. It saw attachments that did not establish conception and communication of the claimed subject matter in the required way. It also saw a conversion claim that, as pleaded, tried to recover patent-like damages for unpatented information.
In other words, BearBox may have had a story that sounded emotionally compelling: an entrepreneur shares materials, another company later receives a patent, and the entrepreneur feels left out. But patent litigation asks a colder question: where is the claim-level, corroborated, timely evidence? Without that evidence, the story does not win.
This is why the case is useful for SEO readers, startup lawyers, patent attorneys, technology founders, and business development teams. It turns abstract legal doctrine into a real-world checklist. Before sharing technical material, ask: What exactly are we disclosing? Is it confidential? Has it been filed? Who receives it? What records will prove what was shared? If a patent later issues, can we map our contribution to a specific claim?
Experience-Based Lessons from BearBox v. Lancium
For anyone who has worked around startups, the fact pattern in BearBox v. Lancium feels painfully familiar. A founder goes to an industry event, talks to potential partners, sends follow-up materials, and hopes the conversation turns into a deal. That is how business gets done. Nobody wants to walk into a cocktail reception carrying a rolling suitcase full of NDAs like a legal magician. But this case shows why informal moments can become expensive later.
The first experience-based lesson is to separate “pitch mode” from “disclosure mode.” Pitch mode is where you describe the problem, the market, the customer pain point, and the high-level value of your solution. Disclosure mode is where you reveal the technical mechanics: diagrams, code, data files, formulas, system architecture, control logic, or implementation details. Founders often slide from one mode into the other because enthusiasm is powerful. The room feels friendly. The potential customer seems interested. Someone asks a smart question. Suddenly, the founder is explaining the engine instead of selling the car.
The second lesson is to create a paper trail that a stranger can understand two years later. Litigation is not judged by the warm feeling of the meeting. It is judged by records. After an important technical conversation, send a careful follow-up email summarizing what was discussed, what was not disclosed, what remains confidential, and what the next step is. Save drafts. Preserve attachments. Keep version histories. If source code matters, use repositories with timestamps and commit messages that do more than say “final final real final.” Future-you will thank present-you for being slightly boring.
The third lesson is to build an invention capture process before the company feels “big enough” to need one. Many early-stage teams believe patent hygiene is something for giant corporations with marble lobbies and conference rooms named after dead inventors. That belief is charming and dangerous. Even a two-person startup can maintain invention disclosure forms, internal review notes, contributor lists, and filing calendars. The goal is not bureaucracy for sport. The goal is to know who invented what, when they invented it, and what evidence proves it.
The fourth lesson is that legal theories should match the facts. If information is confidential, protect it like a trade secret. If compensation is expected for use of an idea, document the agreement. If patent protection is desired, file promptly. Trying to transform an unpatented, publicly shared technology discussion into a patent-style damages claim can create preemption problems. Courts tend to dislike legal costumes; if a conversion claim walks, talks, and asks for money like a patent infringement claim, the court may treat it that way.
Finally, BearBox v. Lancium reminds innovators that collaboration is not the same as inventorship. A person can inspire, advise, pitch, sell, demonstrate, or brainstorm without becoming a patent inventor. Inventorship requires a legally significant contribution to the conception of the claimed invention. That may sound strict, but it protects the integrity of the patent system. The practical solution is not to avoid collaboration. The solution is to collaborate carefully, write things down, file early when appropriate, and never rely on memory when a timestamped document can do the job better.
Conclusion: The Real Message Behind the Denied Inventorship Claim
BearBox v. Lancium: Inventorship Dispute Denied is a reminder that patent law rewards proof, not assumptions. BearBox believed its founder should have been named on Lancium’s patent, but the courts found that the evidence did not show conception or communication of the claimed invention before Lancium’s independent work. The Federal Circuit also rejected BearBox’s attempt to proceed with a state-law conversion claim that looked too much like a patent infringement theory for unpatented technology.
For founders and technical teams, the lesson is not “never talk to anyone.” That would make conferences very quiet and extremely awkward. The lesson is to protect important ideas before sharing them, document technical contributions in real time, use confidentiality tools where appropriate, and understand that inventorship depends on specific patent claims. A great idea may start over dinner, but a winning inventorship case needs more than a dinner story. It needs evidence strong enough to survive court.
