Is going to be notably tied to a custom eth token?
That idea does seem to contribute to the nonsense you mention.
Especially considering the README complaining about competitors being "unintuitive", but then just slapping `blockchain` on a visualization program
- - -
Also pardon my pedanticness, but its "Source available", most people consider "Open Source" (as a branding) to be open to access, changes, and use. You have released the code, sure. But you are massively restricting how that code is used (including preventing the program being used with other versions of the same program??)
https://opensource.org/osd for the "common" definition of the term
Do you know why the project is released under a custom license, rather than something familiar? If this could be summarized in a few simple sentences I'd appreciate it. Ain't nobody got time to read all that legalese.
For example: is the purpose of the license to prevent commercial re-use? In other words: what does this custom license accomplish that no normal OSI-approved license could?