forked from Delulu-Delilah/free-the-code
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
656 lines (593 loc) · 41.2 KB
/
Copy pathindex.html
File metadata and controls
656 lines (593 loc) · 41.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta
name="viewport"
content="width=device-width, initial-scale=1.0"
/>
<title>PSA: Elegoo Centauri Carbon & GPL Compliance</title>
<link rel="stylesheet" href="styles.css">
<link rel="stylesheet" href="styles-mobile.css" media="only screen and (max-width: 480px)">
<link rel="stylesheet" href="styles-lite.css" media="(max-width: 640px), (prefers-reduced-motion: reduce)" id="liteStylesheet">
<link rel="icon" type="image/png" href="assets/icons/elegoo-logo.png">
<link rel="canonical" href="https://freethecode.lol/">
<meta name="description" content="A community effort aggregating evidence, context, and actions to ensure GPL compliance for the Elegoo Centauri Carbon firmware.">
<!-- Open Graph for rich embeds -->
<meta property="og:title" content="PSA: Elegoo Centauri Carbon & GPL Compliance">
<meta property="og:description" content="Community evidence indicates CC firmware is Klipper‑based with modifications. This page aggregates proof, context, and actions for GPL compliance.">
<meta property="og:type" content="website">
<meta property="og:url" content="https://freethecode.lol/">
<meta property="og:image" content="https://freethecode.lol/assets/images/cat-sunglasses.png">
<meta property="og:image:secure_url" content="https://freethecode.lol/assets/images/cat-sunglasses.png">
<meta property="og:image:type" content="image/png">
<meta property="og:image:alt" content="PSA preview image">
<!-- Twitter Card -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="PSA: Elegoo Centauri Carbon & GPL Compliance">
<meta name="twitter:description" content="Evidence, links, and community actions regarding GPL compliance for the Centauri Carbon firmware.">
<meta name="twitter:image" content="https://freethecode.lol/assets/images/cat-sunglasses.png">
<!-- Scripts -->
<script src="script.js" defer></script>
</head>
<body>
<!-- Navigation Menu -->
<a class="skip-link" href="#overview">Skip to content</a>
<nav class="nav-menu" role="navigation" aria-label="Primary">
<div class="nav-container">
<div class="nav-brand">
<span class="nav-icon">⚠️</span>
<span class="nav-title">GPL Compliance PSA</span>
</div>
<div class="nav-links">
<a href="#overview" class="nav-link">Overview</a>
<a href="#evidence" class="nav-link">Evidence</a>
<a href="#context" class="nav-link">Context</a>
<a href="#legal" class="nav-link">Legal & Policy</a>
<a href="#good-actors" class="nav-link">Good Actors</a>
<a href="#support" class="nav-link">Support</a>
<a href="#contributors" class="nav-link">Contributors</a>
<a href="#response" class="nav-link">Response</a>
<a href="#updates" class="nav-link">Updates</a>
<a href="#action" class="nav-link">Take Action</a>
<a href="#outcomes" class="nav-link">Outcomes</a>
</div>
<button class="nav-toggle" type="button" aria-controls="primary-navigation" aria-expanded="false">
<span></span>
<span></span>
<span></span>
</button>
</div>
</nav>
<header class="glass-container" id="overview">
<div class="hero-content">
<h1><span class="emoji">⚠️</span> PSA: Elegoo Centauri Carbon & GPL Compliance</h1>
<p class="hero-subtitle">
A community effort to ensure GPL license compliance in 3D printer firmware
</p>
<!-- Function for when resolved - true / false - If true, set the right date -->
<div class="timeline" data-resolved="false" data-resolved-date="September 5, 2025">🗓️ Issue raised: August 7, 2025 | Still ongoing</div>
<div class="source-link">
<span class="emoji">📋 Sources: </span>
· <a href="ELEGOO%20Official/Request%20for%20source%20code%20for%20Klipper%20used%20in%20the%20Centauri%20Carbon_7vVQSTcLfW/Request%20for%20source%20code%20for%20Klipper%20used%20in%20the%20Centauri%20Carbon_page_1.html" target="_blank" rel="noopener noreferrer">Discord Export</a>
· <a href="https://www.reddit.com/r/3Dprinting/comments/1n1rlmc/klipper_on_the_centauri_carbon_i_need_your_help/" target="_blank" rel="noopener noreferrer">Reddit: Klipper on CC</a>
· <a href="https://www.reddit.com/r/elegoo/comments/1n36tll/elegoo_is_lying/" target="_blank" rel="noopener noreferrer">Reddit: “Elegoo is lying”</a>
· <a href="https://www.hackster.io/news/elegoo-centauri-carbon-3d-printer-review-c57caab085e1" target="_blank" rel="noopener noreferrer">Hackster review quote</a>
· <a href="https://blog.octoeverywhere.com/the-best-iphone-and-android-apps-for-the-elegoo-centauri-carbon/" target="_blank" rel="noopener noreferrer">OctoEverywhere mention</a>
· <a href="https://consumerrights.wiki/Article_suggestions" target="_blank" rel="noopener noreferrer">Rossmann Consumer Rights wiki</a>
· <a href="https://opencentauri.github.io/OpenCentauri/" target="_blank" rel="noopener noreferrer">OpenCentauri docs</a>
· <a href="https://discord.gg/sRVKm5KjCf" target="_blank" rel="noopener noreferrer">OpenCentauri Discord</a>
· <a href="https://github.com/OpenCentauri/OpenCentauri/tree/main/serial-multiplexer" target="_blank" rel="noopener noreferrer">Serial multiplexer</a>
</div>
</div>
</header>
<main class="layout">
<aside class="toc glass-container" aria-label="Table of contents" id="primary-navigation">
<h3>On this page</h3>
<ul class="toc-list">
<li><a class="toc-link" href="#overview">Overview</a></li>
<li><a class="toc-link" href="#evidence">Evidence</a></li>
<li><a class="toc-link" href="#context">Context</a></li>
<li><a class="toc-link" href="#legal">Legal & Policy</a></li>
<li><a class="toc-link" href="#good-actors">Good Actors</a></li>
<li><a class="toc-link" href="#support">Support</a></li>
<li><a class="toc-link" href="#contributors">Contributors</a></li>
<li><a class="toc-link" href="#response">Response</a></li>
<li><a class="toc-link" href="#updates">Updates</a></li>
<li><a class="toc-link" href="#action">Take Action</a></li>
<li><a class="toc-link" href="#outcomes">Outcomes</a></li>
</ul>
</aside>
<div class="content">
<section>
<div class="glass-card" id="issue">
<h2><span class="emoji">📌</span> The Issue</h2>
<p>
The <strong>Elegoo Centauri Carbon</strong> 3D printer uses a heavily
modified version of <a href="https://www.klipper3d.org/">Klipper</a>
firmware, specifically based on a commit <code>616 commits past v0.9.1 (shorthash 28f60f7e)</code>.
Klipper is licensed under <strong>GPL-3.0</strong>, which legally
requires all modifications to be made publicly available.
</p>
<div class="highlight">
<strong>Why this matters:</strong> GPL compliance isn't optional—it's
a legal requirement. When companies use open-source software, they
must respect the licenses. This ensures transparency, security, and
the right for users to modify and improve their own devices.
</div>
<div class="warning">
<strong>Current Status:</strong> Despite clear evidence and community
pressure since August 7, 2025, Elegoo has only provided generic
support responses stating the issue is "under review by R&D."
</div>
</div>
<div class="glass-card" id="evidence">
<h2><span class="emoji">🔍</span> Technical Evidence</h2>
<p>
Community investigation by user <strong>Sims (HACC)</strong> revealed
multiple pieces of evidence through detailed binary analysis:
</p>
<h4>DSP MCU Firmware Analysis</h4>
<p>
The DSP (part of Allwinner SoC) uses Xtensa architecture and runs as the mainboard MCU.
Binary analysis shows:
</p>
<ul>
<li>Clear Klipper MCU code paths in the DSP firmware</li>
<li>Xtensa architecture not supported by mainline Klipper—proving custom modifications</li>
<li>Firmware is not stripped, allowing detailed reverse engineering</li>
</ul>
<h4>Bed MCU Firmware</h4>
<ul>
<li>Contains commands not present in mainline Klipper</li>
<li>Mainline Klipper can connect but shuts down due to version mismatch</li>
<li>Reveals exact commit: <code>616 commits past v0.9.1 (shorthash 28f60f7e)</code></li>
</ul>
<h4>Host Software Analysis</h4>
<ul>
<li>Main application at <code>/app/app</code> is written in C++</li>
<li>Contains transpiled Python code from Klipper's Klippy host</li>
<li>Original references to Klippy remain intact in the C++ version</li>
<li>Includes components like <code>mem_interface_DSP</code></li>
</ul>
<h4>Embedded Web Server (Mongoose 7.12)</h4>
<ul>
<li>Firmware exposes an HTTP service identifying as <code>Mongoose/7.12</code> (embedded web server).</li>
<li>Mongoose 7.12 requires a commercial license to be able to distribute it without publishing code, which ELEGOO does not have.</li>
<li>If no commercial license was obtained, this is a separate license violation in addition to any GPL obligations.</li>
</ul>
<p>
Sources:
<a href="https://mongoose.ws/" target="_blank" rel="noopener noreferrer">Cesanta Mongoose</a>,
<a href="https://mongoose.ws/licensing/" target="_blank" rel="noopener noreferrer">Licensing</a>,
<span>Firmware evidence link pending</span>
</p>
<h4>Network Traffic Investigation</h4>
<p>
Community members investigated excessive network usage:
</p>
<p>For more details, see the <a href="#traffic-note">note below</a>.</p>
<ul>
<li>Printer generates 70GB+ of traffic per month while idle</li>
<li>Health checks ping servers 10+ times per minute</li>
<li>Traffic analysis shows connections to Apple servers</li>
<li>Responsible for 29.5% of household network traffic while idle</li>
</ul>
<div class="info">
<strong>Technical Note:</strong> While open-sourcing may be challenging due to
Allwinner and Chitu involvement, other manufacturers like Creality
have solved this by releasing source code alongside binary blobs for
proprietary components.
</div>
<div class="warning">
<strong>Security Concern:</strong> Running known out-of-date open-source software
without access to security patches creates significant risks for botnet exploitation.
</div>
</div>
<div class="glass-card" id="context">
<h2><span class="emoji">🏢</span> Industry Context</h2>
<p>
Unfortunately, Elegoo isn't alone in problematic practices. Some vendors have
GPL compliance issues; others impose ecosystem restrictions (not GPL violations):
</p>
<ul>
<li>
<strong>Anycubic:</strong> KobraOS on 2.x and 3.x series violates
GPL on multiple libraries including Klipper
</li>
<li>
<strong>Chitu-supplied platforms:</strong> Shared firmware stacks used across brands (e.g., Anycubic; some Creality models historically) have, in some cases, resulted in distributions missing the corresponding source for modified GPL components. Supplier contracts do not remove the distributor’s GPL obligations (<a href="https://www.gnu.org/licenses/gpl-3.0.en.html" target="_blank" rel="noopener noreferrer">GPL‑3.0</a>). Chitu Systems' firmware and hardware are proprietary, which can constrain user modification and repairability (<a href="https://3dprintingindustry.com/news/chitu-systems-and-chitubox-a-lesson-in-fighting-open-source-3d-printing-194783/" target="_blank" rel="noopener noreferrer">context</a>).
</li>
<li>
<strong>Historical cases:</strong> Community reports cite GPL gaps on specific models (e.g., Creality CR‑X), while other products later published sources (e.g., Creality K1 series).
</li>
<li>
<strong>Marlin/Linux derivatives:</strong> Some vendors have shipped modified Marlin, Linux kernels, or Entware without timely source publication. GPL‑3.0 requires providing complete corresponding source to users of the binaries.
</li>
</ul>
<div class="highlight">
<strong>The Solution:</strong> The 3D printing community needs to
hold manufacturers accountable. GPL violations harm innovation,
security, and user rights across the entire ecosystem.
</div>
<div class="info">
<strong>Vendor statement:</strong> “No, the ELEGOO OS is not based on Klipper. The Klipper solution uses a dual-chip setup, consisting of an SOC + MCU, whereas the Centauri Carbon’s hardware architecture uses only one chip. Currently, it is not compatible with open-source Klipper commands or some open-source plugins, such as Fluidd.” (Hackster, Feb 17 2025) (<a href="https://www.hackster.io/news/elegoo-centauri-carbon-3d-printer-review-c57caab085e1" target="_blank" rel="noopener noreferrer">source</a>). This page aggregates community technical indicators of Klipper‑based components and modifications. If confirmed, GPL‑3.0 requires providing the complete corresponding source to users of the distributed binaries (<a href="https://www.gnu.org/licenses/gpl-3.0.en.html" target="_blank" rel="noopener noreferrer">GPL‑3.0</a>).
</div>
</div>
<div class="glass-card" id="legal">
<h2><span class="emoji">⚖️</span> Legal and Policy Points</h2>
<p>
Recent discussion clarified several important GPL topics and consumer options:
</p>
<ul>
<li><strong>Binary blobs vs. GPL‑3.0:</strong> Linux allows some blobs under GPL‑2.0 with exceptions; GPL‑3.0 requires complete corresponding source for modified GPL components. A blob cannot replace modified Klipper source.</li>
<li><strong>Why compliance matters:</strong> If a vendor cannot publish changes due to third‑party contracts (e.g., Allwinner), they should not have used GPL code. Non‑compliance voids distribution rights.</li>
<li><strong>Fraud and consumer protection:</strong> Misrepresentations (e.g., denying Klipper use) may create consumer fraud exposure; some users consider FTC/state reports.</li>
<li><strong>Chargebacks (use cautiously):</strong> Some banks may accept disputes for deceptive practices. Risk: loss of support or future purchases.</li>
<li><strong>International enforcement:</strong> GPL has seen international enforcement, including in China. For imported hardware, U.S. courts can issue border injunctions.</li>
<li><strong>Chitu involvement:</strong> Community‑reported analysis suggests Chitu involvement with similarities to Anycubic Kobra 2 Pro (<a href="https://www.reddit.com/r/3Dprinting/comments/1n1rlmc/klipper_on_the_centauri_carbon_i_need_your_help/" target="_blank" rel="noopener noreferrer">community analysis</a>, <a href="https://github.com/OpenCentauri/OpenCentauri/tree/main/serial-multiplexer" target="_blank" rel="noopener noreferrer">repo</a>). Where possible, prefer primary evidence (firmware strings/diffs, vendor docs). This informs where to direct compliance requests.</li>
<li><strong>Mongoose 7.x licensing:</strong> The Cesanta Mongoose embedded web server (v7.x) requires a commercial license for proprietary firmware; using it without one would be a separate license violation. Not to be confused with <a href="https://mongoose-os.com/licensing.html" target="_blank" rel="noopener noreferrer">Mongoose OS</a> (a different product with a Community Edition under Apache‑2.0). See <a href="https://mongoose.ws/licensing/" target="_blank" rel="noopener noreferrer">licensing</a>.</li>
</ul>
<p style="opacity:.8">These points reflect community discussion and are not legal advice.</p>
</div>
<div class="glass-card" id="good-actors">
<h2><span class="emoji">✅</span> Good Actors (Embracing Open-Source and Community)</h2>
<p>These companies often contribute to the broader 3D printing ecosystem, foster innovation, and empower users with flexibility and control.</p>
<ul>
<li><strong>Prusa Research</strong> — PrusaSlicer; strong community engagement and documentation.</li>
<li><strong>LulzBot (FAME 3D)</strong> — Historically 100% open‑source; robust printers that encourage user modification.</li>
<li><strong>Creality</strong> — Released open-source Klipper firmware for K1 series and Ender 3 V3 KE.</li>
<li><strong>Ultimaker</strong> — Long-standing open-source ethos; early printers released with open designs.</li>
<li><strong>BCN3D</strong> — Published original design files for Sigma/Sigmax R19 to benefit the community.</li>
<li><strong>Rat Rig</strong> — Open-source V‑Core series; open hardware approach encourages modification.</li>
<li><strong>Sovol</strong> — SV08 project sources published on GitHub.</li>
<li><strong>Snapmaker</strong> — U1 runs Klipper; FAQ states commitment to publish sources (<a href="https://support.snapmaker.com/hc/en-us/articles/33344279396759-FAQ-for-Snapmaker-U1-3D-Printer" target="_blank" rel="noopener noreferrer">FAQ</a>).</li>
</ul>
<p style="opacity:.8">If you have more examples, propose additions via PR or message in the thread.</p>
</div>
<div class="glass-card" id="support">
<h2><span class="emoji">🤝</span> Community Support</h2>
<p>
The community has rallied behind this issue with overwhelming
support:
</p>
<div class="community-support">
<div class="support-badge">
<strong>50+</strong><br />Discord reactions
</div>
<div class="support-badge">
<strong>25+</strong><br />Active community members
</div>
<div class="support-badge">
<strong>Multiple</strong><br />Email requests sent
</div>
<div class="support-badge">
<strong>100%</strong><br />Community agreement
</div>
</div>
<h3>Notable Community Quotes:</h3>
<blockquote class="quote">
<p>
<strong>Lamarc | N4 | CC (HACC):</strong> "Everyone including elegoo is required to stick to licensing rules.
It's clearly Klipper under the hood so it has to be made available"
</p>
<p>
<strong>Anna | DevMiner (HACC):</strong> "Taking opensource projects (Klipper) and calling them your own is super scummy"
</p>
<p>
<strong>Anna | DevMiner (HACC):</strong> "If you take opensource software that's licensed under GPL-3.0,
modify it and then not allow people to see the code, you're violating the license and are very easy to sue."
</p>
<p>
<strong>leiden6665:</strong> "Yeah, any derivatives of Klipper have to be open source because of the license.
I mentioned this in one of the other chats I'm surprised it took this long for someone to bring it up."
</p>
<p>
<strong>zuturiddu:</strong> "I fully support this request, which is essentially asking to adhere to use of open source software under a specific license."
</p>
<p>
<strong>Fabrizio | N4:</strong> "I support this. Provide the source."
</p>
<p>
<strong>bloky246:</strong> "I hope they make it open source as well"
</p>
<p>
<strong>Connor:</strong> "I stopped having the printer from idling anymore and now I'm gonna just turn off the wifi,
the Chinese have too much to gain from my american network until they can explain themselves"
</p>
<p>
<strong>brando753:</strong> "GPL compliance is simple: if you use GPL code, you must provide the modified source on request. If you cannot, you must not use GPL code. Providing binary blobs is not compliance. Next step: document refusals and contact SFC to support enforcement."
</p>
</blockquote>
</div>
<div class="glass-card" id="contributors">
<h2><span class="emoji">🙏</span> Special Thanks to Our Contributors</h2>
<p>
This community effort wouldn't be possible without the dedication and
expertise of numerous individuals. We extend our heartfelt gratitude
to everyone who has contributed to this important cause:
</p>
<div class="gratitude">
<strong>This is what open-source community looks like:</strong>
Technical experts, concerned users, and advocates working together to
protect everyone's rights. Every contribution, from detailed technical
analysis to simple support messages, has been valuable in building
this case.
</div>
<div class="contributors-grid">
<div class="contributor-category">
<div class="carousel-header">
<h4>🔬 Technical Analysis & Investigation</h4>
<div class="carousel-controls">
<button class="carousel-prev-btn" aria-label="Scroll left">‹</button>
<button class="carousel-next-btn" aria-label="Scroll right">›</button>
</div>
</div>
<ul class="contributor-list carousel-container scrollbar-hide">
<li><strong>Sims</strong> - Initiated the request for Elegoo to release their modified Klipper source code, providing detailed technical proof from the firmware binaries showing modifications to the MCU, bed MCU, and the transpilation of Klipper's Python host code to C++. Discovered evidence the firmware was based on Anycubic's and found articles where Elegoo explicitly denied using Klipper.</li>
<li><strong>Rabir</strong> - Verified that mainline Klipper could connect to the printer's bed board, confirming the specific version and commit Elegoo was using.</li>
<li><strong>motorhead1991</strong> - Pointed out usage of other open-source projects like the Linux kernel and Entware, implying further license obligations.</li>
</ul>
</div>
<div class="contributor-category">
<div class="carousel-header">
<h4>✉️ Active Advocacy & Communication</h4>
<div class="carousel-controls">
<button class="carousel-prev-btn" aria-label="Scroll left">‹</button>
<button class="carousel-next-btn" aria-label="Scroll right">›</button>
</div>
</div>
<ul class="contributor-list carousel-container scrollbar-hide">
<li><strong>bloky246</strong> - Emailed Elegoo directly about the open-source request multiple times and shared the canned responses with the group to keep others informed of the official (non)progress.</li>
<li><strong>Anna | DevMiner</strong> - Consistently pushed for the source code release, created a separate channel to move the off-topic network traffic discussion, and regularly pinged Elegoo staff for updates. Also sent emails to support.</li>
<li><strong>beiyr</strong> - Actively pinged Elegoo staff for updates, contacted the creator of Klipper to inform them of the situation, and attempted to contact the firmware developers (Chitu) directly.</li>
<li><strong>EXEN</strong> - Voiced support, actively pinged Elegoo staff for updates, and created a Reddit post to raise broader awareness of the issue.</li>
<li><strong>lilybwees</strong> - Articulated the community's position clearly, arguing that Elegoo had a legal and ethical obligation to release the code, especially since they had lied to reviewers. Defended the community's persistence when moderators intervened.</li>
<li><strong>brando753</strong> - Provided a detailed explanation of GPLv3 license compliance, refuting the idea that binary blobs or "cleaning up the code" were acceptable. Argued that Elegoo's actions constituted fraud and suggested contacting the SFC and the FTC.</li>
<li><strong>ViciousNarwhalFL</strong> - Suggested adding the issue as an article on Louis Rossmann's consumer rights wiki to increase public pressure.</li>
</ul>
</div>
<div class="contributor-category">
<div class="carousel-header">
<h4>💪 Community Support & Awareness</h4>
<div class="carousel-controls">
<button class="carousel-prev-btn" aria-label="Scroll left">‹</button>
<button class="carousel-next-btn" aria-label="Scroll right">›</button>
</div>
</div>
<ul class="contributor-list carousel-container scrollbar-hide">
<li><strong>Lamarc</strong> - Voiced early and consistent support for the request, emphasizing that all parties, including Elegoo, must adhere to licensing rules.</li>
<li><strong>Delulu Delilah</strong> - Expressed 100% support for the open-source request.</li>
<li><strong>zuturiddu</strong> - Supported the request, framing it as a simple matter of adhering to open-source license terms.</li>
<li><strong>leiden6665</strong> - Noted early on that derivatives of Klipper must be open source due to the license and expressed surprise it took so long for the issue to be formally raised.</li>
<li><strong>coffeecup</strong> - Added their voice to the call for Elegoo to provide the source code.</li>
<li><strong>Fabrizio</strong> - Supported the movement and demanded the source code.</li>
<li><strong>nate™</strong> - Co-signed the request.</li>
<li><strong>harrym</strong> - Expressed that the printer would be even better with access to the open-source Klipper software.</li>
</ul>
</div>
<div class="contributor-category">
<div class="carousel-header">
<h4>🌐 Network Traffic Investigation</h4>
<div class="carousel-controls">
<button class="carousel-prev-btn" aria-label="Scroll left">‹</button>
<button class="carousel-next-btn" aria-label="Scroll right">›</button>
</div>
</div>
<ul class="contributor-list carousel-container scrollbar-hide">
<li><strong>crazyantihacker</strong> - First raised the issue of the printer's excessive network traffic, reporting that his device had uploaded over 70GB in a single month while idle and linked to a Reddit thread discussing it.</li>
<li><strong>Marcel</strong> - Provided screenshots from his network monitoring tool confirming the excessive data usage.</li>
<li><strong>LA3QMA-KGB</strong> - Used tcpdump to investigate the traffic, noting that the slicer software also generated significant traffic.</li>
<li><strong>Kvviingu</strong> - Analyzed his network traffic, confirming that the printer was responsible for a large percentage of activity even while idle and that it was mostly a high volume of health checks.</li>
</ul>
</div>
<div class="contributor-category">
<div class="carousel-header">
<h4>📚 Industry Context & Legal Insights</h4>
<div class="carousel-controls">
<button class="carousel-prev-btn" aria-label="Scroll left">‹</button>
<button class="carousel-next-btn" aria-label="Scroll right">›</button>
</div>
</div>
<ul class="contributor-list carousel-container scrollbar-hide">
<li><strong>Corey Stup</strong> - Pointed out that Anycubic engages in the same practice of violating GPL with their KobraOS, providing industry context.</li>
<li><strong>baconmilkshake</strong> - Argued that the situation was more likely due to a rushed development process rather than conspiracy, but highlighted the security risks of running outdated, closed-source software and the potential for creating a botnet.</li>
<li><strong>erica</strong> - Downplayed network traffic conspiracy theories but emphasized the seriousness of the legal and ethical violation of the Klipper license.</li>
<li><strong>Tyler</strong> - Suggested that Elegoo's staff might be unaware of the Klipper usage, with the firmware being handled by a third-party board manufacturer, and mentioned that US state departments of justice could be interested in the case due to deceptive advertising.</li>
<li><strong>Louis</strong> - Offered the perspective that Chinese companies have historically had less respect for open-source licenses and that marketing likely denied using Klipper because the implementation didn't meet user expectations for a full Klipper-based product.</li>
</ul>
</div>
</div>
<div class="info">
<strong>Special Recognition:</strong> <strong>Owen (Technical Support)</strong> from Elegoo deserves credit for being the only Elegoo employee to acknowledge the issue directly and provide a timeline, showing that constructive dialogue is possible.
</div>
<h3>Community Moderators & Platform Providers:</h3>
<ul>
<li><strong>YogurtDrink | Resin / CC</strong> - Clarified community roles and helped direct requests to appropriate Elegoo employees</li>
<li><strong>Chirimorin | CC, N4Pro, S4U</strong> - Provided context on network traffic analysis</li>
</ul>
<div class="gratitude">
<strong>To everyone listed above and the many others who have supported this effort:</strong> Your collective voice has turned a single technical observation into a powerful community movement. This is exactly how open-source communities should work—together, transparently, and with respect for the legal frameworks that protect everyone's rights.
</div>
</div>
<div class="glass-card" id="response">
<h2><span class="emoji">📧</span> Elegoo's Response</h2>
<p>
Community members have received mostly identical canned responses from
Elegoo support, with multiple people reporting receiving the exact same message:
</p>
<div class="warning">
<h3>Typical Canned Response:</h3>
<div class="email-template">
Subject: Re: Request for GPL Compliance - Centauri Carbon Firmware
Dear Customer,
Thank you for providing us with your valuable reply. We greatly appreciate your input, and we want to assure you that we are actively working on addressing the issue you raised.
Currently, we have submitted the relevant information to our Research and Development (R&D) team and are awaiting their response. However, we regret to inform you that there has been a delay in the process, which has contributed to the extended timeframe. We sincerely apologize for any inconvenience this delay may have caused you.
Please rest assured that your feedback is important to us, and we are fully committed to resolving the matter as promptly as possible. Our R&D team is diligently reviewing the information and exploring possible solutions to address the issue you encountered.
Regards
Jett Yue
ELEGOO Support Team
</div>
<p style="margin-top: 1rem; font-style: italic; opacity: 0.8">
<strong>— Multiple community members received this identical response</strong>
</p>
</div>
<div class="info">
<strong>Community Reactions:</strong>
</div>
<ul>
<li><strong>Marcel | CC (HACC):</strong> "Got the same response 1 to 1"</li>
<li><strong>erica:</strong> "yeah, i got this exact same response too"</li>
<li><strong>Anna | DevMiner (HACC):</strong> "they just have canned responses to all the common issues"</li>
<li><strong>Anna | DevMiner (HACC):</strong> "I'd be great if elegoo can get their head out of their butt and have the courage to talk like real people and not just copy-paste the same message"</li>
</ul>
<div class="highlight">
<strong>Staff Response:</strong> Owen (Elegoo Technical Support) acknowledged the issue and mentioned there "should be a response in a day or two" as of August 12, 2025. However, no concrete action has been taken as of the latest community reports on August 27, 2025.
</div>
<div class="warning">
<strong>Community Concern:</strong> Multiple members expressed frustration that Elegoo employees (including moderators) were unable or unwilling to directly address the technical GPL compliance issues raised by the community.
</div>
</div>
<div class="glass-card" id="updates">
<h2><span class="emoji">🆕</span> Latest Updates</h2>
</br>
<ul>
<li>Clarified: binary blobs are not a GPL‑3.0 workaround; complete corresponding source is required for modified Klipper.</li>
<li>Community notes potential fraud concerns from past denials; some consider FTC/state reports.</li>
<li>Some users weighing chargebacks; caution: this can impact future support/purchases.</li>
<li>Discussion on international enforcement and possible border injunctions for non‑compliant imports.</li>
<li>Chitu involvement likely; similarities to Anycubic Kobra 2 Pro firmware observed (<a href="https://www.reddit.com/r/3Dprinting/comments/1n1rlmc/klipper_on_the_centauri_carbon_i_need_your_help/" target="_blank" rel="noopener noreferrer">community analysis</a>). Prefer primary evidence and add dates where possible.</li>
<li>Links added: Reddit context, Hackster review, OctoEverywhere mention, Rossmann wiki suggestion.</li>
<li>Workarounds: Raspberry Pi host possible via <a href="https://github.com/OpenCentauri/OpenCentauri/tree/main/serial-multiplexer" target="_blank" rel="noopener noreferrer">serial‑multiplexer</a>, MCU side remains challenging.</li>
<li>New Reddit thread highlights: broken WebUI during prints; reports of thermal‑runaway risk on 1.1.25; excessive network traffic; community demand for source to enable community fixes and OpenNept4une‑like progress; confirmation that Klippy is transpiled to C++ and modified.</li>
<li>Examples cited: router blocking as workaround for telemetry; precedent that Creality released Klipper‑based sources for K1; acknowledgment that third‑party developers (e.g., Chitu) may be involved, which does not remove GPL obligations.</li>
<li>New: Evidence of embedded <code>Mongoose/7.12</code> web server in firmware; the Cesanta Mongoose library (v7.x) requires a paid commercial license for proprietary use. Add primary evidence links. Note: not Mongoose OS.</li>
<li>Aug 28, 2025: Community discussion emphasizes documenting refusals and contacting SFC; debate on binary blobs vs. GPL‑3.0 compliance; border‑enforcement remedies for imports noted.</li>
</ul>
</div>
<div class="glass-card" id="action">
<h2><span class="emoji">📢</span> What You Can Do</h2>
<p>
If you own a Centauri Carbon, care about open-source rights, or want
to support legal compliance in the 3D printing industry, you can help
by politely but firmly requesting Elegoo release the source code.
</p>
<h3>Email Elegoo Support:</h3>
<p>
Use this template to contact Elegoo directly. The more people who
reach out, the more likely they are to take action:
</p>
<div class="email-template">
Subject: Request for GPL Compliance – Centauri Carbon Firmware
Dear Elegoo Support Team,
I am writing regarding the Elegoo Centauri Carbon 3D printer and its firmware's GPL compliance obligations.
BACKGROUND:
It has been conclusively determined that the Centauri Carbon firmware is based on Klipper (commit 616 past v0.9.1, shorthash 28f60f7e), which is licensed under GPL-3.0. Community analysis has revealed:
• Modified DSP MCU firmware with Klipper code paths
• Custom bed MCU firmware with non-standard commands
• Transpiled Klippy host code (Python to C++) with original references intact
• Version strings that confirm the exact Klipper commit used
LEGAL REQUIREMENT:
Under GPL-3.0, all modifications to licensed code must be made available to users. This is not a request—it is a legal obligation that applies regardless of business preferences or technical challenges.
REQUEST:
I respectfully but firmly request that Elegoo immediately release the complete modified source code for:
1. DSP MCU firmware (Xtensa architecture modifications)
2. Bed MCU firmware with custom commands
3. Host-side Klippy code (C++ transpiled version)
4. Any other GPL-licensed components used in the system
PRECEDENT:
Other manufacturers like Creality have successfully handled similar situations by releasing source code alongside binary blobs for proprietary components where necessary.
I expect a concrete timeline for source code release, not generic "under review" responses. The 3D printing community is watching how Elegoo handles this legitimate compliance request.
Thank you for your prompt attention to this legal matter.
Sincerely,
[Your Name]
[Your Contact Information]
</div>
</br>
<h3>Other Ways to Help:</h3>
<ul>
<li>
<strong>Share this page</strong> with other Centauri Carbon owners
</li>
<li>
<strong>Join the discussion</strong> on Reddit, Discord, and 3D
printing forums
</li>
<li>
<strong>OpenCentauri community</strong>: Read the <a href="https://opencentauri.github.io/OpenCentauri/" target="_blank" rel="noopener noreferrer">docs</a> and join the <a href="https://discord.gg/sRVKm5KjCf" target="_blank" rel="noopener noreferrer">Discord</a>
</li>
<li>
<strong>Support open-source alternatives</strong> like mainline
Klipper
</li>
<li>
<strong>Consider manufacturers</strong> who properly respect
open-source licenses when making future purchases
</li>
<li>
<strong>If refusal persists</strong>, document responses and evidence and consider contacting the Software Freedom Conservancy about GPL compliance. For consumer deception concerns, some users are also reporting to the FTC/state agencies.
</li>
<li>
<strong>Chargebacks (last resort)</strong>: Some banks may accept disputes for deceptive practices. Be aware this can affect future support or purchases.
</li>
</ul>
</div>
<div class="glass-card" id="outcomes">
<h2><span class="emoji">🎯</span> Expected Outcomes</h2>
<p>
If Elegoo complies with the GPL license (as they legally must), users
will gain:
</p>
<ul>
<li>
<strong>Security updates:</strong> Community can patch
vulnerabilities
</li>
<li>
<strong>Feature improvements:</strong> Open development enables
innovation
</li>
<li>
<strong>Hardware longevity:</strong> Continued support even after
EOL
</li>
<li>
<strong>Transparency:</strong> Users know exactly what's running on
their devices
</li>
<li>
<strong>Learning opportunities:</strong> Study and understand the
firmware
</li>
</ul>
<div class="warning">
<strong>Consequences of Non-Compliance:</strong> GPL violations are
legally enforceable. The community has both the right and standing to
pursue legal action if necessary, though everyone hopes Elegoo will
simply do the right thing voluntarily.
</div>
</div>
</section>
</div>
</main>
<footer>
<p>
This PSA was created by the 3D printing community to raise awareness
about GPL compliance. Learn more about Klipper at
<a href="https://www.klipper3d.org/" style="color: #fff"
>klipper3d.org</a
>.
</p>
<p class="footer-subnote">
<div class="last-update"></div>
Thank you to all community contributors who made this effort possible 💜
</p>
<p class="footer-subnote">
<button id="lite-toggle" type="button" aria-pressed="false" aria-controls="liteStylesheet">Enable Lite Mode</button>
</p>
<div class="info footer-info" id="traffic-note">
<strong>Note:</strong> A related but separate network traffic issue was discovered where the Centauri Carbon generates excessive data usage (70GB+ per month while idle). This has been moved to a <a href="https://redd.it/1mbhnmn" target="_blank" rel="noopener noreferrer">separate discussion thread</a> to keep the GPL compliance issue focused.
</div>
</footer>
</body>
</html>