diff --git a/2026/06/2026-06-23-zeicoin.md b/2026/06/2026-06-23-zeicoin.md new file mode 100644 index 0000000000..7cd11228fd --- /dev/null +++ b/2026/06/2026-06-23-zeicoin.md @@ -0,0 +1,83 @@ +Before disabling any content in relation to this takedown notice, GitHub +- 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). +- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice). + +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). + +--- + +**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.** + +Yes, I am the copyright holder. + +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** + +No + +**Does your claim involve content on GitHub or npm.js?** + +GitHub + +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** + +I am the [private] [private] of the ZeiCoin blockchain software and hold all copyright. The project is published at https://github.com/ryo-zen/zeicoin under the Apache 2.0 license, which imposes specific preservation requirements on all distributions. + +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** + +ZeiCoin is an original blockchain implementation authored by [private] in 2025, comprising a full node, peer-to-peer networking, consensus engine, proof-of-work mining subsystem, and CLI tooling. It is written in Zig and distributed under the Apache 2.0 license. The original work includes SPDX license identifiers in all source files and a NOTICE file in the repository root attributing authorship. + +**If the original work referenced above is available online, please provide a URL.** + +https://github.com/ryo-zen/zeicoin + +**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.** + +**Based on the above, I confirm that:** + +The entire repository is infringing + +**Identify the full repository URL that is infringing:** + +https://github.com/zeicoin/zeichain + +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** + +No + +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and must be identified separately. Please read more about forks. 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:** + +**Is the work licensed under an open source license?** + +Yes + +**Which license?** + +apache-license-2.0 + +**How do you believe the license is being violated?** + +The Apache 2.0 license requires all distributions to meet three conditions under Section 4. The infringing repository at https://github.com/zeicoin/zeichain has violated all three: (1) it replaced the Apache 2.0 LICENSE file with an MIT license, violating Section 4(a) which requires recipients to receive a copy of the Apache 2.0 license; (2) it emmited the SPDX license identifiers and copyright notices from all source files, violating Section 4(c) which requires retention of all copyright and attribution notices; and (3) it emmited the NOTICE file, violating Section 4(d) which requires a readable copy of the NOTICE file to be included in all distributions. Failure to comply with any of these conditions terminates the infringer's rights to distribute the work. + +**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.** + +The repository must: (1) restore the Apache 2.0 LICENSE file and remove the unauthorized MIT license; (2) restore SPDX license identifiers and copyright notices to all source files; and (3) restore the original NOTICE file. Alternatively, the repository must be made private or removed entirely. + +**Do you have the alleged infringer’s contact information? If so, please provide it.** + +Unknown. No contact information is publicly available for the repository owner. GitHub's own records would identify the account holder. + +**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.** + +**I have taken fair use into consideration.** + +**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.** + +**I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.** + +**So that we can get back to you, please provide either your telephone number or physical address.** + +[private] + +**Please type your full name for your signature.** + +[private]