|
| 1 | +Before disabling any content in relation to this takedown notice, GitHub |
| 2 | +- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work). |
| 3 | +- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice). |
| 4 | + |
| 5 | +To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice). |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.** |
| 10 | + |
| 11 | +Yes, I am the copyright holder. |
| 12 | + |
| 13 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** |
| 14 | + |
| 15 | +No |
| 16 | + |
| 17 | +**Does your claim involve content on GitHub or npm.js?** |
| 18 | + |
| 19 | +GitHub |
| 20 | + |
| 21 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 22 | + |
| 23 | +I am the [private] and [private] copyright holder of the project "ESP-Miner-NerdQAxePlus". |
| 24 | +[private] developed and published the original firmware and source code under [private] [private] GitHub account. |
| 25 | +The project includes [private] original code for operating Bitcoin miners using BM1366, BM1368 and BM1370 ASICs, including all firmware components, hardware abstraction layers, mining loop logic, communication protocol implementation, and device configuration logic. |
| 26 | +As the [private] [private] and [private], I hold full copyright over this work. |
| 27 | + |
| 28 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 29 | + |
| 30 | +A third-party company has taken [private] open-source project "ESP-Miner-NerdQAxePlus", forked it, and is now redistributing a modified, closed-source version in violation of [private] copyright and the original open-source license. |
| 31 | + |
| 32 | +Instead of keeping the firmware open-source, they removed all source code and replaced it with binary-only firmware releases. Their repository contains only three binary releases without any source code. |
| 33 | + |
| 34 | +They changed the display module (a minor hardware modification that does not justify a license exemption) and are distributing a proprietary firmware blob instead of publishing the required source code, as the license obliges them to do for derivative works. |
| 35 | + |
| 36 | +They sell devices using [private] hardware and firmware design, bundle a small screen running [private] original open-source firmware, and distribute a closed-source binary that users must install using a third-party flashing tool. Firmware updates in the Web UI are disabled, forcing users to use this external tool to install the binary. |
| 37 | + |
| 38 | +The closed-source binary may contain unauthorized or harmful modifications (e.g., potential hashrate skimming), and users have no ability to verify its contents. |
| 39 | + |
| 40 | +This constitutes: |
| 41 | +– unauthorized copying of [private] copyrighted code |
| 42 | +– unauthorized modification of [private] copyrighted code |
| 43 | +– removal of the open-source license |
| 44 | +– redistribution of derivative work without meeting license requirements |
| 45 | +– commercial use of my project without complying with the license |
| 46 | + |
| 47 | +The infringing repository is located here: |
| 48 | +https://github.com/yysluping/ESP-Miner-NerdQAxePlus/releases |
| 49 | + |
| 50 | +**If the original work referenced above is available online, please provide a URL.** |
| 51 | + |
| 52 | +https://github.com/shufps/ESP-Miner-NerdQAxePlus |
| 53 | + |
| 54 | +**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.** |
| 55 | + |
| 56 | +**Based on the above, I confirm that:** |
| 57 | + |
| 58 | +The entire repository is infringing |
| 59 | + |
| 60 | +**Identify the full repository URL that is infringing:** |
| 61 | + |
| 62 | +https://github.com/yysluping/ESP-Miner-NerdQAxePlus |
| 63 | + |
| 64 | +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.** |
| 65 | + |
| 66 | +No |
| 67 | + |
| 68 | +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:** |
| 69 | + |
| 70 | +**Is the work licensed under an open source license?** |
| 71 | + |
| 72 | +Yes |
| 73 | + |
| 74 | +**Which license?** |
| 75 | + |
| 76 | +gnu-general-public-license-v3.0 |
| 77 | + |
| 78 | +**How do you believe the license is being violated?** |
| 79 | + |
| 80 | +They took [private] open-source project and created a modified version of it, but they do not provide the source code for their changes. |
| 81 | +Instead, they only publish closed-source firmware binaries. |
| 82 | +[private] license requires that anyone who distributes modified versions must also publish the full source code. |
| 83 | +By removing the license, not sharing their changes, and distributing binary-only firmware, they are violating the open-source license. |
| 84 | + |
| 85 | +**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.** |
| 86 | + |
| 87 | +They must either remove the repository, or bring it into full compliance with the open-source license. |
| 88 | +To comply, they need to restore the original license, provide proper attribution, and publish the complete source code for all firmware versions they are distributing, including all modifications they made. |
| 89 | +Only providing binary files is not allowed under the license. |
| 90 | + |
| 91 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 92 | + |
| 93 | +[private] |
| 94 | + |
| 95 | +**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.** |
| 96 | + |
| 97 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 98 | + |
| 99 | +**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.** |
| 100 | + |
| 101 | +**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.** |
| 102 | + |
| 103 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 104 | + |
| 105 | +[private] |
| 106 | + |
| 107 | +**Please type your full name for your signature.** |
| 108 | + |
| 109 | +[private] |
0 commit comments