| A future-tense corollary: “What if it turns out not to be open source?” As someone who works in crypto-currency, the enduring mystery over who invented bitcoin bothers me a lot. The going belief is in a still-anonymous fairy godfather, Satoshi Nakamoto, who gave unto the world his/her/their foundational idea, or intellectual property, and said go forth and multiply. Just one problem: What if Nakamoto invented his/her/their technology at a company or academic institution? That institution c/would claw back the intellectual property. Where there is intellectual property, there are patent lawyers; and where there are patent lawyers, there are licensing fees! See Oracle v. Google over Sun Microsystems' Java. What if the reason he/she/it maintains anonymity is because to reveal himself is to reveal where he worked when he invented bitcoin? That employer would be the true owner of the IP, and open-source bitcoin would go private. The foundational idea that's launched a thousand startups, supposedly open-source, turns out to be anything but open-source. That would suck. I wager that, at some point in the future, bitcoin will be private property owned by a corporation or academic institution. |
At best I would imagine that nakamoto could get sued for releasing IP that wasn't his to release, and they might be able to lay claim over the bitcoin name and codebase for future updates... but they can't do anything about all the existing forks and derivatives. They already exist!
And as I understood it, the Oracle v Google case was based on the fact that Oracle was already licensing java for mobile devices, and android basically wrote a new not-java, which is all fine and well, but Oracle was claiming that not just the implementation but also the API fell under their licensing operation. That is, licensing was already part of the story, it was just a question of whether it applied to Google's usage.
Bitcoin is not that situation: no licensing story currently exists. If it were taken into closed source, it wouldn't be much different from forking the code and making a proprietary version of it, and licensing that out. But the codebase that already exists, in the open, and includes a whole lot of code that is by no means property of sakamoto's institution, can't just be removed from the internet
Also, can you even patent a network protocol? Because the client itself doesn't hold much value, especially not for the derivative works. It's the protocol that's key
ofc I'm not a lawyer, I don't know squat about the topic, but intuitively it seems nonsensical. Imagine doing that operation intentionally: releasing a design so you could retroactively patent and force licenses after worldwide adoption. It'd be dumb as hell