> Package maintainers will publish their releases to a decentralized registry powered by a Byzantine fault-tolerant blockchain to eliminate single sources of failure, provide immutable releases, and allow communities to govern their regions of the open-source ecosystem, independent of external agendas.
It's existence is an attempt to justify the creation of yet another cryptocurrency, not as a serious solution to any problem that exists in distributing software.
Keep in mind that this scheme wouldn't reward the authors of software -- it rewards the people who create and upload packages. Those usually aren't the same people, and the maintainers that are most subject to burnout are the authors, not the packagers.
It also appears to require those developers to purchase (or otherwise acquire) tokens before adding software to the packaging system.
It creates an incentive to package software for the ecosystem, which is a pretty good goal to achieve for a package manager -- especially a brand new one where it would be hard to gain traction without a large number of packages.
What money will be entering this ecosystem? Absent funds flowing in, how will package maintainers be able to convert their tea bucks to something they can pay rent with?
I've noticed that a lot of crypto enthusiasts tend to reach for technical solutions without understanding the social causes of the problem in the first place
With all the flaws of npm, people do want to be able to have a immutable, mirrorable package-repository with a trust framework they can independently confirm. This does that, along with clever extras like "tasters" who stake a certain amount of value before confirming a package does x.
It's.. sad, that any tech that uses blockchain is now doomed to flag-death because of everything. I get it, but can't help but wonder how I'd have felt reading this paper 10 years ago.