Ethereum Classic

<p><strong>Ethereum Classic Core Developers — Olympia Development Series (Part 2)<br>Welcome to the Gorgoroth Trials: Community Alpha Testing for Fukuii, Ethereum Classic’s New High-Performance Client<br>December 8, 2025</strong></p>
<h2 id="welcome-to-the-gorgoroth-trials">Welcome to the Gorgoroth Trials</h2>
<p>The Ethereum Classic community is invited to participate in the <strong>Gorgoroth Trials</strong> - a comprehensive alpha testing campaign for Fukuii, a high-performance Scala 3 implementation of the Ethereum Classic protocol. This is your opportunity to help validate Fukuii's compatibility and readiness before mainnet deployment.</p>
<p>Named after the volcanic plateau in Mordor where Sauron trained his armies, the Gorgoroth Trials represent a crucible through which Fukuii must pass to prove its mettle alongside battle-tested clients like Core-Geth and Hyperledger Besu.</p>
<h3 id="what-are-the-battlenets">What Are the Battlenets?</h3>
<p>The <strong>Battlenets</strong> are specialized testing environments designed to validate different aspects of Fukuii's implementation. Each Battlenet isolates a specific dimension of client behavior, allowing testers to observe how Fukuii performs under controlled but realistic protocol conditions. Together, these environments create a structured pathway for validating networking, mining, consensus, and interoperability before advancing toward mainnet readiness.</p>
<h3 id="gorgoroth-the-multi-client-proving-ground">Gorgoroth — The Multi-Client Proving Ground</h3>
<p><strong>Gorgoroth</strong> is a private test network where Fukuii faces off against Core-Geth and Hyperledger Besu in controlled combat scenarios. Here we validate:</p>
<ul>
 <li><strong>Network Communication</strong> - Can Fukuii shake hands with diverse peers?</li>
 <li><strong>Mining Compatibility</strong> - Do blocks mined by different clients achieve consensus?</li>
 <li><strong>Protocol Compatibility</strong> - Does Fukuii speak the same language as Core-Geth and Besu?</li>
 <li><strong>Faucet Service</strong> - Can testnet tokens flow to those who need them?</li>
</ul>
<p><strong>Configurations Available:</strong></p>
<ul>
 <li>3nodes - 3 Fukuii nodes (baseline validation)</li>
 <li>fukuii-geth - 3 Fukuii + 3 Core-Geth nodes</li>
 <li>fukuii-besu - 3 Fukuii + 3 Besu nodes</li>
 <li>mixed - 3 Fukuii + 3 Core-Geth + 3 Besu nodes (ultimate test)</li>
</ul>
<p>Estimated time: 1–2 hours for basic validation.</p>
<h2 id="why-community-validation-matters">Why Community Validation Matters</h2>
<p>Community testing ensures Fukuii is evaluated under real-world conditions that no internal environment can fully replicate, revealing compatibility issues and stability concerns early. By running Fukuii on diverse machines, networks, and configurations, testers expose edge cases that only emerge outside controlled lab scenarios. This collective effort accelerates maturity, strengthens client reliability, and builds confidence ahead of broader ecosystem adoption.</p>
<h3 id="the-stakes-are-high">The Stakes are High</h3>
<p>Fukuii aims to join the ranks of production-ready Ethereum Classic clients. Before we can confidently recommend it for mainnet use, we need to know:</p>
<ol>
 <li><strong>Does it work as advertised?</strong> - Theory meets practice in the Battlenets</li>
 <li><strong>Does it play well with others?</strong> - Multi-client networks are ETC's strength</li>
 <li><strong>Will it survive in the wild?</strong> - Real-world conditions reveal hidden issues</li>
 <li><strong>Is it ready for your infrastructure?</strong> - Different setups expose different challenges</li>
</ol>
<h3 id="why-your-testing-is-essential">Why Your Testing Is Essential</h3>
<p>The Fukuii development team has done extensive internal testing, but nothing replaces the diversity of real-world scenarios that community testing provides:</p>
<ul>
 <li><strong>Different Operating Systems</strong> - Your Linux, macOS, or Windows setup might reveal OS-specific issues</li>
 <li><strong>Different Network Conditions</strong> - Your internet connection, firewall rules, and ISP matter</li>
 <li><strong>Different Hardware</strong> - Your CPU, RAM, and disk configurations create unique scenarios</li>
 <li><strong>Different Use Cases</strong> - How you want to use Fukuii might differ from our assumptions</li>
</ul>
<h3 id="building-trust-through-transparency">Building Trust Through Transparency</h3>
<p>By validating Fukuii publicly and documenting the results, we:</p>
<ul>
 <li>Build confidence in the implementation</li>
 <li>Create a knowledge base for future users</li>
 <li>Identify issues before they affect production users</li>
 <li>Demonstrate ETC's commitment to multi-client diversity</li>
</ul>
<h2 id="how-to-participate-in-the-gorgoroth-trials">How to Participate in the Gorgoroth Trials</h2>
<p>Participation is simple: choose a trial configuration, run the test suite, record your experience, and share your results to help refine the client before mainnet readiness. Before starting, ensure your environment includes Java 21, SBT for building and managing the Scala project, and Python 3 for running the supporting test scripts. Testers should also confirm they have a reliable network connection, adequate disk space, and permission to execute local scripts, as these setup factors often surface edge cases that help strengthen Fukuii’s real-world robustness.</p>
<h2 id="1-choose-your-trial">1. Choose Your Trial</h2>
<p><strong>For Most Testers - Start with Gorgoroth:</strong></p>
<blockquote>
 # Clone the repository<br>git clone https://github.com/chippr-robotics/fukuii.git<br>cd fukuii/ops/gorgoroth <br><br># Start a test network<br>fukuii-cli start 3nodes <br><br># Wait 60 seconds for initialization<br>sleep 60 <br><br># Run the automated test suite<br>cd test-scripts<br>./run-test-suite.sh 3nodes
</blockquote>
<h3 id="2-document-your-experience">2. Document Your Experience</h3>
<p>We need to know:</p>
<ul>
 <li><strong>What worked</strong> - Success stories help us understand what's stable</li>
 <li><strong>What didn't work</strong> - Failures help us fix bugs before release</li>
 <li><strong>What was confusing</strong> - Documentation gaps need to be filled</li>
 <li><strong>What surprised you</strong> - Unexpected behavior reveals design issues</li>
</ul>
<p>Even small details can be deeply informative.</p>
<h3 id="3-submit-your-field-report">3. Submit Your Field Report</h3>
<p>Submitting a structured field report allows the development team to analyze results consistently, identify patterns, and prioritize fixes across different testing environments.</p>
<h4>Option 1 — GitHub Issues with Field Report Template (Preferred)</h4>
<p>Visit the <a href="https://github.com/chippr-robotics/fukuii/issues/new/choose" rel="noopener noreferrer nofollow">Fukuii GitHub Issues</a> and select the <strong>"Gorgoroth Trials Field Report"</strong> template.</p>
<p>This template will guide you through submitting:</p>
<ul>
 <li>System information</li>
 <li>Test duration and configuration</li>
 <li>Test results (pass/fail for each area)</li>
 <li>What worked well</li>
 <li>Issues encountered</li>
 <li>Performance metrics</li>
 <li>Suggestions for improvement</li>
</ul>
<p>Quick Link: <a href="https://github.com/chippr-robotics/fukuii/issues/new?template=gorgoroth_field_report.md&amp;labels=gorgoroth-trials,validation-results" rel="noopener noreferrer nofollow">Submit Field Report</a></p>
<h4>Option 2 — GitHub Discussions (For General Feedback)</h4>
<p>For less formal feedback or questions, use <a href="https://github.com/chippr-robotics/fukuii/discussions" rel="noopener noreferrer nofollow">GitHub Discussions</a> in the "Gorgoroth Trials" category.</p>
<h4>Option 3 — GitHub Issues (Specific Bugs)</h4>
<p>If you discover a specific bug unrelated to your field report, create a GitHub issue:</p>
<ol>
 <li>Go to <a href="https://github.com/chippr-robotics/fukuii/issues/new/choose" rel="noopener noreferrer nofollow">https://github.com/chippr-robotics/fukuii/issues/new/choose</a></li>
 <li>Select "Bug report" template</li>
 <li>Add label: gorgoroth-trials</li>
 <li>Include:Steps to reproduce<br>Expected behavior<br>Actual behavior<br>Log snippets<br>System information</li>
</ol>
<h3 id="4-help-other-testers">4. Help Other Testers</h3>
<p>Join the Ethereum Classic Community <strong><a href="https://ethereumclassic.org/discord" rel="noopener noreferrer nofollow">Discord</a></strong>. The Gorgoroth Trials are a community effort. If you figure something out:</p>
<ul>
 <li>Share your solutions in discussions</li>
 <li>Help troubleshoot others' issues</li>
 <li>Document workarounds you discover</li>
 <li>Suggest improvements to documentation</li>
</ul>
<h2 id="testing-timeline">Testing Timeline</h2>
<p>The timeline below outlines the alpha testing window and the sequence of review and refinement phases leading into the planned beta release. These milestones are part of the broader preparation for the Olympia upgrade, where reliable multi-client support becomes essential for testing EVM compatibility changes and validating BASEFEE-related improvements. As Fukuii progresses through alpha, beta, and production-readiness stages, its stability and interoperability will directly strengthen the network’s ability to adopt Olympia with confidence and maintain ETC’s commitment to a diverse and resilient client ecosystem.</p>
<h3 id="alpha-testing">Alpha Testing</h3>
<p><strong>Start</strong>: December 8, 2025 (00:00:00 UTC)<br><strong>End</strong>: December 31, 2025 (23:59:59 UTC)</p>
<h3 id="what-happens-next">What Happens Next?</h3>
<ol>
 <li><strong>January 1-7, 2026</strong> - Development team analyzes all field reports</li>
 <li><strong>January 8-14, 2026</strong> - Critical bugs are addressed</li>
 <li><strong>January 15, 2026</strong> - Beta testing phase begins (if alpha is successful)</li>
 <li><strong>TBD</strong> - Production release recommendation to ETC community</li>
</ol>
<p>Your feedback during the alpha testing period directly impacts the timeline and quality of the beta release.</p>
<h2 id="documentation">Documentation</h2>
<p>Comprehensive guides and testing references are available to help you navigate the Gorgoroth Trials, troubleshoot issues, and explore advanced validation paths like Cirith Ungol.</p>
<h3 id="gorgoroth-resources">Gorgoroth Resources</h3>
<ul>
 <li><strong><a href="https://github.com/chippr-robotics/fukuii/blob/main/ops/gorgoroth/QUICKSTART.md" rel="noopener noreferrer nofollow">Gorgoroth Quick Start</a></strong> - Get running in 5 minutes</li>
 <li><strong><a href="https://github.com/chippr-robotics/fukuii/blob/main/docs/testing/GORGOROTH_COMPATIBILITY_TESTING.md" rel="noopener noreferrer nofollow">Compatibility Testing Guide</a></strong> - Detailed test procedures</li>
 <li><strong><a href="https://github.com/chippr-robotics/fukuii/blob/main/docs/testing/GORGOROTH_FAUCET_TESTING.md" rel="noopener noreferrer nofollow">Faucet Testing Guide</a></strong> - Test token distribution</li>
 <li><strong><a href="https://github.com/chippr-robotics/fukuii/blob/main/docs/validation/GORGOROTH_VALIDATION_STATUS.md" rel="noopener noreferrer nofollow">Validation Status</a></strong> - Current progress</li>
</ul>
<h3 id="cirith-ungol-optional-advanced-trial">Cirith Ungol (Optional Advanced Trial)</h3>
<ul>
 <li><strong><a href="https://github.com/chippr-robotics/fukuii/blob/main/docs/testing/CIRITH_UNGOL_TESTING_GUIDE.md" rel="noopener noreferrer nofollow">Cirith Ungol Testing Guide</a></strong> - Real-world sync validation</li>
</ul>
<h3 id="general-documentation">General Documentation</h3>
<ul>
 <li><strong><a href="https://github.com/chippr-robotics/fukuii/tree/main/docs" rel="noopener noreferrer nofollow">Fukuii Documentation</a></strong> - Full documentation index</li>
 <li><strong><a href="https://github.com/chippr-robotics/fukuii/blob/main/docs/architecture/architecture-overview.md" rel="noopener noreferrer nofollow">Architecture Overview</a></strong> - How Fukuii works</li>
</ul>
<h3 id="getting-help">Getting Help</h3>
<ul>
 <li><strong>GitHub Discussions</strong>: Ask questions, share findings</li>
 <li><strong>Documentation</strong>: Check the guides linked above</li>
 <li><strong>Issue Tracker</strong>: Report bugs with reproduction steps</li>
 <li><strong>Community</strong>: Help each other succeed</li>
</ul>
<h2 id="recognition-for-testers">Recognition for Testers</h2>
<p><strong>Hall of Fame. </strong>Participants who submit detailed field reports will:</p>
<ul>
 <li>Be included in CONTRIBUTORS.md</li>
 <li>Receive recognition in release notes</li>
 <li>Be acknowledged in community channels</li>
</ul>
<h2 id="a-note-on-cirith-ungol-the-bonus-trial">A Note on Cirith Ungol (The Bonus Trial)</h2>
<p>Cirith Ungol represents the next level of validation - testing Fukuii against the real Ethereum Classic network. This is <strong>optional</strong> but highly valuable:</p>
<p><strong>Why Test with Cirith Ungol?</strong></p>
<ul>
 <li>Validates sync performance with 20M+ real blocks</li>
 <li>Tests peer diversity (public network has many client types)</li>
 <li>Reveals issues that only appear with substantial state</li>
 <li>Measures real-world resource usage</li>
</ul>
<p><strong>When to Try Cirith Ungol:</strong></p>
<ul>
 <li>After successfully completing Gorgoroth trials</li>
 <li>When you have 4-8 hours for sync to complete</li>
 <li>If you have 100GB+ available disk space</li>
 <li>If you're comfortable with longer-running tests</li>
</ul>
<p><strong>What We Learn:</strong></p>
<ul>
 <li>SNAP sync performance and reliability</li>
 <li>Fast sync completion and state verification</li>
 <li>Long-term stability (24+ hour continuous operation)</li>
 <li>Memory usage patterns with large state</li>
 <li>Disk I/O characteristics</li>
</ul>
<p>Even if only a handful of testers attempt Cirith Ungol, the data will be invaluable for understanding Fukuii's production readiness.</p>
<h2 id="final-thoughts">Final Thoughts</h2>
<p>The Gorgoroth Trials are more than just testing — they are a collective statement about the values that define Ethereum Classic and the future we are building together. They showcase a community willing to roll up its sleeves, validate its own infrastructure, and ensure that every upgrade stands on a foundation of open participation and technical rigor. In helping Fukuii take shape, we reinforce the ethos that has carried ETC through a decade of challenges:</p>
<ul>
 <li><strong>Decentralization</strong> - Multiple independent client implementations</li>
 <li><strong>Quality</strong> - Thorough validation before production use</li>
 <li><strong>Transparency</strong> - Open testing and public results</li>
 <li><strong>Collaboration</strong> - Community-driven development</li>
</ul>
<p>Your participation, whether testing for 15 minutes or running week-long stability tests, contributes to a stronger, more resilient Ethereum Classic network.</p>
<p>The gates of Gorgoroth are open. The trials have begun.</p>
<p><strong>For the glory of Ethereum Classic!</strong></p>
<p><strong>— The Fukuii Development Team <a href="https://github.com/realcodywburns" rel="noopener noreferrer nofollow">@realcodywburns</a> | <a href="https://github.com/chippr-robotics/fukuii" rel="noopener noreferrer nofollow">@chippr-robotics/fukuii</a></strong></p>
<h2 id="next-in-the-series">Next in the Series</h2>
<p>The next installment in the Olympia Development Series will be announced once the community and core developers determine the most meaningful milestone to document next.<br>👉 Olympia Development Series (Part 3) - TBD</p>

Olympia Development Series — Part 2: Welcome to the Gorgoroth Trials

Table of Contents

EthereumClassic

Other articles published on Dec 9, 2025

Join our free newsletter for daily crypto updates!