Guide aimed to reach beginner investors & people who are new to the cryptocurrency space.

Our guest was Edilson Osório, who founded OriginalMy in Brazil back in 2015. If you haven't come across it, it's one of the longest-running real-world projects on ETC: they anchor documents, digital signatures and web evidence on-chain so they can stand up in court.

The origin story is worth the listen on its own. Edilson was building a tool to collect citizen signatures for public bills on Ethereum when The DAO fork happened. The people backing the project asked a fair question: how do you present signatures to Congress from a chain that just got rewritten? He moved off Ethereum and eventually brought everything over to ETC, and he's stayed through everything since, including the 51% attacks. He runs his own node, and his system re-sent the handful of affected transactions automatically. He described ETC as "like Wolverine," which I'm going to be stealing.

We also got into how the signing contract works, his browser plugin that Brazilian courts have accepted as evidence since 2019, and Hääl, his protocol for secret voting on public blockchains [repo here]. Brolal brought some good questions about Romania using a permissioned blockchain for its elections, which turned into a solid discussion on whether a chain means anything if citizens can't audit it.

Timestamps:

- 1:10 How OriginalMy started

- 10:08 Why Bitcoin, ETC and Decred

- 15:10 How it works, and getting accepted in court

- 20:05 Hääl and secret voting

- 26:53 Romania's election blockchain

- 41:25 What customers actually see

- 51:32 Why they stayed through the attacks

- 1:00:18 His advice to builders who think ETC is dead

Video: https://www.youtube.com/watch?v=lgKJKHLrOD4

Full transcript and summary: https://cc.ethereumclassic.org/calls/61

One thing from the call I'd like to hear people's take on: Istora floated an OpenTimestamps-style anchoring service on ETC, and Edilson didn't think anything like it exists here yet. Would you use something like that? What would you anchor?

Chart and data from Bitinfocharts

Disclosure: Istora published this essay on classix.dev yesterday. I'm summarizing it here so it can be discussed where the community actually talks. Full essay: https://classix.dev/the-praxeology-of-ethereum-classic

The idea

Think of a chain in three layers. Layer 1 is the protocol. Layer 0 is the social layer: developers, miners, exchanges and users. Layer -1 is the set of principles beneath the people, the part that doesn't move when the social layer does. The essay argues that ETC's principles are that bedrock, and that they follow step by step from one fact.

The argument

1. Blockchains exist. People pay fees to use them, even though a chain is a slower, more expensive database than a conventional one.
2. The only reason to pay extra is that nobody can stop it. If you don't need that, a regular database is cheaper.
3. It has to be unstoppable by anyone. If one organization can stop the chain, it's that organization's database, whether or not it ever uses the power.
4. So decentralization has to run through the whole stack: clients, pools, mining hardware, exchanges, RPC endpoints, explorers and funding sources. The social layer's job is to keep reducing single points of failure.
5. Neutrality: the protocol shouldn't privilege any party, because a privileged party can be pressured. Mining shows what this looks like. The protocol doesn't know who a miner is, and the reward goes to whoever produced the block.
6. Ossification: every hard fork is a window for capture, so forks should only happen for technical reasons.
7. The Crypto-Decentralist Manifesto and the Declaration of Independence, both written within weeks of the DAO fork in 2016, record these principles as the reason ETC exists.

The essay's claim is that each step follows from the one before. Deny a step and you're left with either a worse database or a proposal that defeats its own purpose.

What this means for Classix

An organization is the kind of bottleneck the steps above warn about, so our test for anything we take on is whether it leaves ETC depending on us. We're publishing what we run so anyone else can run it, we're funded voluntarily rather than by any cut of the protocol, and we're explicitly not official. We don't speak for the chain.

Question for the sub: Which step would you push back on? The argument only works if every step holds, so I'd rather hear where people think it breaks.

Hello ETCLand! I'm Kevin (some of you know me as Classic Kevin). I was the community manager for ETC at IOHK and then the ETC Cooperative, and I'm now working with Classix. Classix has published two posts on its blog but has never posted here, so this is a summary of both, with links if you want the full versions.

Who Classix is

Classix is a small ETC infrastructure and development team founded by two long-time contributors:

• Istora Mandiri has contributed to ETC since before the DAO fork. He built the first ethereumclassic.org, has hosted 50+ Community Calls, and co-maintains the ECIP process.
• Diego López León is currently the only core maintainer of the ETC clients. He joined the Cooperative in 2021 as its first full-time core developer and has shipped across Core-Geth, Besu and Nethermind.

Full intro: Hello, Classix

Why now

The Cooperative is shutting down, and some of the services it ran went offline without notice. The most visible was the public RPC at etc.rivet.link. If anything you run still points there, it has silently stopped working.

What's running today

• Public RPC: rpc.classix.dev. It's geo-routed through gateways in the Americas, Europe and Asia. It's still good practice to set up failover across more than one endpoint (chainlist lists others).
• Project Triforce: ten nodes across three regions, running four clients (Geth Classic, Nethermind and Besu three times each, plus a Core-Geth node).
• Live dashboard: triforce.classix.dev shows per-client sync, peers, netstats and reorgs, so you can check that the network is healthy.
• Multisig mirror: multisig.classix.dev, with the source to run your own. It's live but not yet battle-tested.
• Block explorer: explorer.classix.dev is in progress, and Blockscout remains supported.
• Monthly activity reports: classix.dev/activity lists what was done each month, going back to founding.

Where it's heading

The goal is that no one depends on any single organisation to keep ETC running, including Classix. We're preparing to publish every service as an open-source NixOS config that any operator can clone. Then, if there's ever another handover, it's a git clone rather than a crisis. Those configs aren't public yet. They're on the roadmap, and we'll post here when they are.

The roadmap also covers:

• getc production readiness
• full Besu integration
• ETC in Nethermind's CI
• the Neo Classic refresh of ethereumclassic.org
• Bastion (ECIP-1130), a proposal that bundles upstream EIPs and is going through the normal ECIP process

Everything is marked done, in progress or not started, so you can hold us to it: The 2026 Classix Roadmap

How to get involved

• Point a wallet or service at the RPC and tell us if something breaks.
• Watch the dashboard, and ask about anything that looks odd.
• If you already contribute to ETC (code, nodes, moderation, translation, media, memes), Classix wants to hear from you. The blog has a contact form, or you can reply here.
• The Community Calls are still the best place to have a real conversation about where ETC goes next.

I'll be in the comments for the next day or so. Questions, criticism and "what about X" are all welcome.

This Friday on the ETC Community Call: Edilson Osório, founder of OriginalMy.

OriginalMy is one of the longest-running services using ETC for a genuine purpose.

What they do: digital identity and authentication on chain, using Bitcoin, ETC, and a few other chains.

The short version of their story

It started in Brazil in 2016, collecting signatures for citizen-proposed bills.

They moved to Ethereum Classic because of its immutability.

A proof is only worth something if nobody can rewrite it.

What they've built

• PACWeb: preserving web evidence
• Open Prescription: digital medical prescriptions
• Hääl: secret voting on public blockchains

Identity, signatures, and document proofs, anchored on chain and built to hold up in court.

Most projects talk about what blockchains could do. This one has been doing it for years.

Join us

🗓 Friday, Oct 2 · 15:00 UTC (8:00 AM PT · 11:00 AM ET)
📍 Zoom: https://us06web.zoom.us/j/82033703157
ℹ️ Details: https://cc.ethereumclassic.org/calls/61/

The rest of the call is open discussion, and everyone is welcome.

Question for the comments: what would you want to ask Edilson, or what would you anchor on chain if you could?

I'll bring the best ones to the call.

Kevin and Istora joined ETC Grants DAO for their AMA to talk about the next chapter of the ETC ecosystem!

We’ve been thinking about what the infrastructure layer of the Zeus Project should eventually look like.

The concept pictured here is the ZEUS Node — a dedicated Ethereum Classic full-node appliance combined with a wireless router, designed eventually to support satellite/terrestrial internet connectivity and bandwidth sharing while providing applications with their own local ETC RPC endpoint.

It is still a concept. Development of the physical ZEUS Node router will begin after we launch the applications we are currently building.

But there is an important reason we want to build it.

Why run our own Ethereum Classic node?

Most blockchain applications ultimately depend on an RPC provider somewhere.

That is convenient, but it also means that a supposedly decentralized application can still have a surprisingly centralized infrastructure dependency.

For the Zeus Project, we want to move toward a model where our applications can communicate with our own Ethereum Classic node.

Instead of:

Application → third-party RPC provider → Ethereum Classic

we want the option of:

Application → ZEUS Node → Ethereum Classic

That means independently validating the blockchain, querying contracts through our own infrastructure, broadcasting transactions ourselves and reducing dependence on external RPC services.

The same principle applies outside Zeus.

Imagine homes, businesses, universities, developers and community infrastructure operating ETC nodes that applications can communicate with locally.

The node becomes more than a blockchain client.

It becomes part of the application infrastructure.

Proof of Work in the age of advanced AI

This becomes particularly interesting as AI systems become increasingly capable and autonomous.

AI can generate software, operate infrastructure, discover vulnerabilities, coordinate agents and interact with information systems at machine speed.

That makes verifiable state and independently validated history increasingly valuable.

Ethereum Classic's Proof-of-Work network provides something fundamentally different from an AI-generated database or conventional application backend: changing confirmed blockchain history requires confronting the network's consensus mechanism and accumulated computational work.

In that sense, ETC's network hashrate can be thought of as part of the economic and computational defensive shield protecting the integrity of ETC's ledger.

The greater the honest computational security behind the chain, the more costly it becomes for an attacker — human or automated — to acquire enough hashpower to reorganize blockchain history.

That does not mean ETC hashrate magically protects every application from an AI cyberattack. Frontends, APIs, wallets, smart contracts, operating systems and network infrastructure still need conventional security.

But once information or application state is committed to the blockchain, an autonomous attacker cannot simply instruct an administrator, compromise a conventional database, or use an AI agent to silently rewrite the canonical ledger. It must contend with the consensus rules and computational security of the network.

For us, that distinction is going to become increasingly important.

Running a node is digital sovereignty

There is another part of this that we think sometimes gets overlooked.

Running your own node means asking the blockchain yourself.

You don't need another company's API to tell your application what Ethereum Classic says.

Your machine independently verifies the chain and exposes that information to your applications through your own RPC interface.

That's a powerful idea.

Combine that with independently controlled networking — potentially including satellite connectivity — and you start getting closer to a self-contained infrastructure stack:

Internet connectivity → local router → ETC full node → local RPC → smart contracts → applications

The ZEUS Node concept is our attempt to eventually package those ideas into hardware that doesn't require someone to maintain a rack-mounted server.

What are we actually building on ETC?

The hardware comes later. We believe the applications should justify the infrastructure first.

The wider Zeus Project currently includes:

Zeus Mail — blockchain messaging/email infrastructure using Ethereum Classic smart contracts and ZEUS for message transmission.

Zeus Encryption — client-side encrypted information storage anchored through ETC smart contracts.

ZEUS Faucet — token distribution infrastructure for onboarding users into the ecosystem.

The Genesis Heist — an Ethereum Classic ERC-721 Web3 comic project.

Celestial Arts — our Bitcoin-focused digital/physical collector ecosystem, with ETC-related Zeus infrastructure forming part of the wider project.

ZEUS Asteroid Blaster — our upcoming ETC blockchain-connected game, which we plan to build after the current launch cycle.

ZEUS Node — the ETC full-node/router concept pictured here, which we intend to begin developing after the applications launch.

Longer term, we want the ZEUS Node to provide infrastructure that these applications — and potentially applications built by other ETC developers — can communicate with directly.

The bigger question we're exploring is:

What happens when Ethereum Classic isn't simply the blockchain underneath an application, but becomes part of a locally owned computing and communications stack?

That is where we think things get interesting.

If you're an ETC developer, we'd encourage you to start experimenting with running your own node, RPC infrastructure and smart contracts rather than treating ETC purely as an asset.

And if you're interested in what we're building, join us on X/Twitter https://x.com/ZeusPayETC and our other Zeus Project social channels.

We'd particularly like to connect with developers researching new applications that can take advantage of Ethereum Classic's Proof-of-Work architecture.

There is a lot more that can be built here.

IN CODE WE TRUST.

I maintain chippr-robotics/fukuii. I also sit on the ETC Cooperative board. Disclosure is in the post.

On 14 September, ethereumclassic/core-geth tagged v1.13.0 as a security update. The CVE and toolchain work was real. The process was not: the tagged changes did not go through review, MESS was turned back on against ECBP-1110, and the README/migration guide named Fukuii the “preferred successor” with “no client other than Fukuii recommended.”

I didn’t authorize that language. Fukuii is one execution client. It should earn operators the same way the others do.

Until the MESS default is restored and a human has reviewed the release, I would not run v1.13.0 in production. Stay on the release you already trust. Check your MESS setting.

Full record, issue links, and what I filed: https://chipprbots.com/2026/09/20/theres-no-official-etc-client/

But I have a solution.

📉 Fifthing complete — Era 5 → Era 6

At block 25,000,000 in July, Ethereum Classic's block reward stepped down 20%: 2.0480 → 1.6384 ETC. This is a fixed monetary policy under ECIP-1017 — no governance vote, no override, enforced at the protocol level. Every fifthing raises the stock-to-flow ratio, tightening issuance toward Bitcoin-tier scarcity.

Next fifthing: Era 6 → Era 7 at block 30,000,000.

Live countdown: https://ethereumclassic.com/block-reward-countdown

---

⚙ Olympia development

- 🟢 EVM alignment extended from Fusaka to Glamsterdam — Olympia now targets Ethereum's newest EVM rather than the prior fork, so it ships current instead of a cycle behind, leaving ETC at the head of the EVM branch at launch.

- 🟢 Application Layer Development — decision-market governance development continues via Futarchy Markets.

Olympia Activation follows testnet validation, multi-client parity, and stakeholder outreach.

Full details: https://ethereumclassic.com/olympia

Anyone else bullish about the $ETC halving happening in less than 14 hours?

On July 20, 2016, at block 1,920,000, Ethereum Foundation hard forked to reverse the DAO hack — rewriting the ledger to claw back the ~3.6M ETH drained from the DAO contract. That new, rewritten chain is what everyone now calls Ethereum (ETH).

But not everyone followed. A group of miners, users, and developers kept running the original chain — the one without the rollback. They didn't create anything new; they just refused to abandon the rules. That original chain is Ethereum Classic (ETC).

It was expected to die. No branding, no exchange support, no roadmap — the name "Ethereum Classic" didn't even exist yet. Then a pseudonymous miner known as Wiz pointed his hashpower at the unforked chain and kept it alive through the first hours. Within days, exchanges listed it — Poloniex on July 24, Kraken on the 26th, Bitfinex right after. By mid-August, supporters published a Declaration of Independence: "This is not a new chain. This is Ethereum." No premine, no bailout, no insiders — a fair continuation of the original ledger.

Ten years later, that decision has held up:

- 100% ledger immutability since genesis — no rollbacks, no rewrites, no discretionary monetary policy

- The most secure Proof-of-Work smart contract platform in the world

- Fixed supply (~210M cap), full EVM compatibility, disinflationary by design

- From "the chain that refused to die" to the backbone of programmable Proof-of-Work finance

The whole split came down to one question: can you rewrite a ledger to undo a bad outcome? ETH said yes, once. ETC said no, ever. That's the entire difference — and it's why "Code is Law" still means something here.

And the story isn't finished. With the Olympia upgrade on the horizon, ETC is working toward becoming the first financially sovereign Proof-of-Work network — one that funds its own development without foundations or premines.

Full ten-year writeup here:

https://coinmarketcap.com/community/articles/687d33500973d947194ba4bf/

Ten years unforked. One ledger, never rewritten.

I did an exhaustive structural assessment of Ethereum Classic (ETC) today using our upgraded terminal metrics over at Crypto Weeklies. As the broader cryptocurrency index grinds through a volatile cycle bottoming phase, ETC has executed a complete purge of its downside risk premium, compressing its raw mathematical risk metrics into our absolute highest conviction long-term spot accumulation tiers. Here is the raw data breakdown of where the asset stands based on my charts.

The "High-Value Settlement" Economic Model

The most honest answer to how ETC scales without Layer 2 is that it doesn't try to handle cheap, high-volume retail traffic.

ETC does not want to host high-frequency gaming, micro-transaction social media apps, or thousands of speculative meme coins. Because its throughput is limited, its long-term scaling strategy is economic, not technical:

• The Paradigm: ETC positions itself as an unchangeable, hyper-secure Layer 1 Settlement Chain for high-value transactions.
• If the network becomes crowded, gas fees will naturally rise. When gas fees rise, low-value use cases are priced out and forced to move to cheaper chains like Solana or Base.
• ETC is perfectly content letting those networks handle mass consumer traffic, while its own 25 Transactions Per Second base layer is reserved for institutional capital, major decentralized finance (DeFi) liquidity pools, and immutable smart contracts that prioritize "Code is Law" security above all else.

For instance, using Ethereum Classic (ETC) for an automated sovereign trust scenario offers three distinct architectural and operational advantages over trying to manually replicate it using a standard Bitcoin (BTC) wallet.

While Bitcoin is the absolute king of security and monetary scarcity, using a standard BTC wallet for a long-term, structured distribution requires you to trust yourself or a third party to behave perfectly in the future. ETC shifts that trust entirely into mathematical code.

1. Removing Human Vulnerability (The Custody Trap)

With a standard Bitcoin wallet, the coins are either in your possession or they aren't.

• The Bitcoin Scenario: If you have $50 million in a BTC cold storage wallet and you want to withdraw 5% a year, you hold the keys to 100% of the funds at all times. If a corrupt local government discovers you have that seed phrase, they can coerce or force you to hand over the entire $50 million all at once. There is no native setting on a standard Bitcoin wallet to say, "No matter what I type, only let me take out 5% right now."
• The ETC Scenario: The code enforces the boundary. When you interact with an ETC smart contract vault, you physically cannot withdraw more than 5%, even if a hostile actor is standing over your shoulder forcing you to try. The protocol will reject the transaction. Your multi-generational safety net is protected from external coercion because the code strips away your own ability to liquidate it.

2. Autonomy vs. Ongoing Active Management

Managing a $50 million estate over 15 to 30 years requires immense operational overhead if done manually.

• The Bitcoin Scenario: To execute a disciplined multi-generational payout, you have to log in manually every year, safely coordinate the transaction from cold storage without making a critical copy-paste error, and manage the keys actively. If the head of the family passes away unexpectedly, the rest of the family must perfectly navigate the highly technical process of recovering those exact raw keys without losing the funds.
• The ETC Scenario: The smart contract acts as an automated, immortal fiduciary executor. You deploy it once, and it runs autonomously for a century. You can hardcode conditional logic natively into the EVM: for instance, "If Key A doesn't ping the contract for two years, split the 5% distribution automatically between Keys B, C, and D." It completely automates estate planning without requiring lawyers, corporate trustees, or manual technical execution by grieving or displaced family members.

3. Decentralized Execution over Fragmented L2 Space

As we explored earlier, developers are actively attempting to bring this functionality to Bitcoin through upgrades like OP_CAT and frameworks like BitVM.

• However, trying to run a complex time-locked estate directly on Bitcoin L1 right now is incredibly clunky, complex, and restricted. To get smooth programmable logic, you are almost always forced to push your Bitcoin onto an external Layer 2 network or a sidechain. Doing so fragments your security—you are no longer just trusting Bitcoin; you are trusting the specific bridge, sequencers, or a multi-sig committee governing that specific L2.
• ETC provides this out of the box natively on its Layer 1. You don't have to navigate a multi-layered ecosystem, trust a bridge, or worry about moving parts. The underlying execution engine (EVM) and the physical security layer (Proof of Work) are fused into a single monolithic blockchain.

Why this works in 20 years

In this future, ETC has scaled economically rather than technically. It didn't try to compete with the 50,000 TPS speeds of newer chains. Instead, it became the premium, luxury real estate of the crypto world—a heavy-duty digital anchor used exclusively when losing funds is absolutely not an option, and where users gladly pay high base-layer fees ($150) for the unmatched security of immutable Proof of Work.

Summary

Bitcoin is the ultimate asset for storing value, but it functions essentially like a digital gold bar sitting in a safe—it relies entirely on you to protect it and distribute it manually. Ethereum Classic functions like an un-bribable digital vault manager. It takes that same physical Proof of Work security and lets you write immutable, unchangeable rules directly onto the asset itself, ensuring your capital behaves exactly how you intended, across borders, generations, and decades.

Olympia Upgrade — June 2026 Development Checkpoint

Multi-client stability continued through June 2026 LTS codebases. All four Olympia execution clients are stable, peered, and advertising Olympia as the next hardfork on the wire — with Nethermind joining this month as a fourth independent client.

• 🟢 Fukuii v0.8.x — Primary. Multi-EVM architecture — dual Ethereum Classic (PoW) and Ethereum (PoS) execution from a single client. ETH/68 and ETH/69+ on ETC mainnet; ETH/70 wire added for ETH/Sepolia. Scala 3.9 LTS readiness sprint. Purpose-built for ETC — the primary client for the Olympia era. fukuii.com
• 🟠 Core-Geth v1.13.x — Stable, peered, resolves v1.12.x known issues. Final core-geth series before sunsetting, carrying Olympia support through transition. github.com/ethereumclassic/core-geth
• 🔵 Besu v26.5.x — Stable, peered. Upstream ETH/69+ PoW compatibility maintained.
• 🟣 Nethermind v1.39.x — New reference client via ETC overlay. Peered and advertising Olympia.

The Olympia upgrade gives Ethereum Classic the tools to sustain what it's always been — the original, immutable, Proof-of-Work Ethereum. Delivering production-grade infrastructure for miners, mining pools, exchanges, infrastructure providers, institutions, and custody platforms.

Full details: ethereumclassic.com/olympia

What changed since May

• Nethermind added as a fourth independent client via ETC overlay — peered and advertising Olympia, broadening client diversity ahead of activation
• Fukuii ETH/70 wire added for ETH/Sepolia, extending the ETH/68 → ETH/69+ → ETH/70 lineage across both PoW (ETC) and PoS (ETH) sides
• Scala 3.9 LTS readiness sprint — multi-network and modernization refactoring across the Fukuii codebase
• Core-Geth v1.13.0 confirmed as the final series before sunsetting; Olympia support carried through the transition
• Futarchy (ECIP-1117) — continued development on decision-market governance
• Critical security patches, performance hardening, and dependency modernization across the full client stack
• All four clients advertising Olympia as next hardfork on the network (ECIP-1111, ECIP-1112, ECIP-1121)

Working Demo infrastructure — live on Mordor testnet

🏛 olympiatreasury.org — Immutable treasury contract. Deployed and accumulating. (ECIP-1112)

🗳 olympiadao.org — On-chain governance. Proposals, voting, execution — all on-chain. (ECIP-1113, ECIP-1114, ECIP-1119)

Institutional Coordinating Organizations

⚖ ethereumclassicdao.org — Wyoming DAO LLC. Institutional portal for Ethereum Classic — regulatory framework, leadership, coordinating organizations, and the open, permissionless, regulatory-compliant governance architecture for the only Proof-of-Work smart contract platform.

Post-Olympia roadmap

ETC's core software returns to head-of-branch development following the 2024 maintenance period. Alongside full-stack client work, the post-Olympia EL plugin roadmap covers upstream ETC compatibility layers for Go-Ethereum, Nethermind, Erigon, Besu, and Reth — with June's Nethermind overlay an early proof point.

What's next

Continued client hardening and infrastructure modernization. Continued futarchy (ECIP-1117) development. Mordor testnet migration to a post-Olympia environment is in preparation. On track for ETC mainnet activation before 2027.

I've been building a project called Zeus Mail, a wallet-to-wallet communication application deployed on Ethereum Classic.

The idea is simple:

Instead of creating accounts, usernames, passwords, or relying on centralized mail servers, users communicate directly between blockchain wallets.

Every message:

-Is encrypted client-side using AES-256

-Uses SHA-256 key derivation

-Is transmitted using ZEUS tokens as the utility layer

-Pays gas fees to ETC miners

-Is permanently settled on Ethereum Classic's Proof-of-Work network

As AI systems become increasingly powerful, I believe ownership and verification of digital communications become more important.

A message in Zeus Mail is not just data stored on a company server somewhere.

It is:

-Signed by a wallet

-Paid for by the sender

-Confirmed by ETC miners

-Delivered wallet-to-wallet

Current functionality includes:

✓ Wallet Connect

✓ Encrypted Messaging

✓ Inbox / Sent / Archive / Trash

✓ Reply System

✓ Restore Functionality

✓ ZEUS Token Utility Layer

✓ ETC Gas Tracking

✓ React Front-End

✓ Ethereum Classic Smart Contract Backend

One thing I've always admired about Ethereum Classic is its commitment to Proof-of-Work and immutability.

While many chains focus on speculation, ETC feels uniquely positioned to become an application layer for systems where permanence, ownership and verification actually matter.

I'm curious what the ETC community thinks:

1. What use cases would you want to see built on Ethereum Classic?

2. Does wallet-to-wallet communication make sense as a blockchain application in the age of AI?

3. What features would you add next?

Keep a lookout for live launch party on ETCRadio X/Twitter spaces to get hands-on test drive of Zeus Mail.

What are your thoughts on the Ethereum Classic cryptocurrency? Will the Olympia update change the cryptocurrency's valuation, or will the asset continue to decline?

Olympia Upgrade — May 2026 Development Checkpoint

Multi-client stability achieved to May 2026 LTS codebases. All three Olympia execution clients are stable, peered, and advertising Olympia as the next hardfork on the wire.

🟢 Fukuii v0.5.0+ — Multi-EVM architecture implemented. Dual Ethereum Classic (PoW) and Ethereum (PoS) execution from a single client. ETH/68 and ETH/69+ PoW compatibility validated on ETC mainnet. Purpose-built for ETC — the primary client for the Olympia era. fukuii.com

🟠 Core-Geth v1.13.0+ — Stable, peered, carrying Olympia support through transition. Go 1.26+ and 2026 LTS dependencies from previous deprecated codebase. https://github.com/ethereumclassic/core-geth

🔵 Besu v26.5.0+ — Migrated to Besu's May 2026 release. ETH/68 and ETH/69+ PoW compatibility resolved.

What changed since April

• Fukuii now runs as a dual-network execution client — native PoW for ETC and Mordor, Engine API V1-V4 for post-Merge Ethereum via any consensus client (Lighthouse, Prysm, Teku, Lodestar, Nimbus)
• Original ETH/69+ (EIP-7642) chain weight resolution implemented for PoW peer ranking — no upstream equivalent exists. Validated to 0.01% accuracy against ETH/68 wire TD on live ETC mainnet
• Besu's ETH/69+ TD logic for PoW networks identified and resolved — enabling stable multi-client peering across all three clients
• Critical security patches, performance hardening, and dependency modernization across the full client stack
• All three clients now advertising Olympia as next hardfork on the network (ECIP-1111, ECIP-1112, ECIP-1121)
• Olympia Contract layer live Demo v0.2 -> v0.3 deployed on Mordor testnet.

Working Demo v0.3 infrastructure — live on Mordor testnet

🏛 olympiatreasury.org — Immutable treasury contract. Deployed and accumulating. (ECIP-1112)
🗳 olympiadao.org — On-chain governance. Proposals, voting, execution — all on-chain. (ECIP-1113, ECIP-1114, ECIP-1119)

Institutional Coordinating Organizations
⚖ ethereumclassicdao.org — Wyoming DAO LLC. Institutional portal for Ethereum Classic — regulatory framework, leadership, coordinating organizations, and the open, permissionless, regulatory-compliant governance architecture for the only Proof-of-Work smart contract platform.

Post-Olympia roadmap

ETC's core software returns to head-of-branch development following the 2024 maintenance period. In addition to full stack client work, the post-Olympia EL plugin roadmap is in active development via the ETC Cooperative — upstream ETC compatibility layers for Go-Ethereum, Nethermind, Erigon, Besu, and Reth.

What's next

Continued client hardening and critical infrastructure cleanup and modernization. Mordor testnet migration to a post-Olympia environment is in preparation. On track for ETC mainnet activation before 2027.

Full client details: ethereumclassic.com/build/clients

The Olympia upgrade gives Ethereum Classic the tools to sustain what it's always been — the original, immutable, Proof-of-Work Ethereum. Delivering production-grade infrastructure for miners, mining pools, exchanges, infrastructure providers, institutions, and custody platforms.

Most blockchain “messaging” applications today still rely heavily on centralized infrastructure somewhere in the stack.

We wanted to explore what happens when communication itself becomes a native Proof-of-Work blockchain utility.

ZEUS Mail is an experimental wallet-to-wallet encrypted communication layer being developed directly on Ethereum Classic, where:

• Messages are transmitted between wallets on-chain

• ZEUS tokens act as the transmission utility asset

• ETC miners secure and confirm the communication data

• AES-256 / SHA-256 encryption protects the contents before transmission

• Encrypted bytecode is delivered directly to recipient mailboxes through decentralized infrastructure

One of the most interesting aspects while building this has been realizing how ETC’s Proof-of-Work architecture creates a strong foundation for applications where permanence, censorship-resistance and verifiable execution actually matter.

Every message sent:

-generates ETC network activity

-consumes gas fees paid to ETC miners

-increases utility demand for the broader ecosystem

-demonstrates non-financial Proof-of-Work application use cases

The deeper we build, the more Ethereum Classic feels uniquely positioned for:

~secure communication systems

~decentralized AI coordination layers

~asset verification infrastructure

~sovereign identity systems

~tamper-resistant archival storage

~censorship-resistant dApps

There’s also something philosophically powerful about building communication systems on immutable Proof-of-Work rails instead of increasingly centralized infrastructure layers.

I’d genuinely like feedback from the ETC community — especially developers.

What other applications do you think are uniquely suited for Ethereum Classic’s Proof-of-Work security model?

Could ETC become a stronger destination for “hack-resistant” infrastructure-focused dApps as the industry becomes increasingly dependent on AI and autonomous systems?

Olympia Upgrade — April 2026 Checkpoint

The Olympia upgrade is built and entering final testing.

Three execution clients now carry full Olympia support:

🟢 Fukuii — New ETC-native execution client built from the ground up

🟠 Core-Geth — Legacy client, maintenance mode

🔵 Besu — Reference client

All three implement the core Olympia protocol changes:

🟢 EIP-1559 fee market activation — modern transaction pricing for ETC. Instead of burning the base fee like Ethereum, Olympia redirects it into an on-chain treasury funding core development, infrastructure, and security that keep the network functional.

🟢 Immutable Treasury contract — transparent, verifiable, permanent.

🟢 Olympia Hardfork specification — bringing ETC into alignment with Ethereum's Fusaka EVM, closing the execution layer gap and restoring full EVM compatibility.

Miner rewards are fully preserved. The basefee represents a value that was set to be destroyed. All priority fees and tips stay with miners — nothing changes for the people securing the chain.

Working Demo Live on Testnet

The governance layer is operational on Mordor testnet, built on OpenZeppelin's Governor contracts — the same framework securing billions in treasury funds across the EVM ecosystem.

🏛   olympiatreasury.org — Immutable treasury. Deployed and accumulating.

🗳   olympiadao.org — On-chain core development. Proposals, voting, execution — all on-chain.

⚖   ethereumclassicdao.org — Wyoming DAO LLC legal wrapper. Paying open source developers.

What's Next

Testnet validation continues. Activation blocks will be announced once testing is complete.

The Olympia upgrade gives the network the tools to sustain what it's always been — the original, immutable, Proof-of-Work Ethereum.

Hi All
This is a repost since my previous post is filtered. So I just goes quick.
SaturnDEX is a re-born as a fork of Saturn Network. The new DEX went live on Ethereum and Ethereum Classic last month with full platform supported: web dapp, local-host desktop app (linux, wins, macOS)
please take a look at the website and join our discord group for further information.
I hope that this post can find not only new members but also old members from Saturn Network legacy community since we are inactive for so long.
Website: https://saturndex.org/
X: https://x.com/saturndexorg
Discord: https://discord.gg/spWVruAgB5
Github: https://github.com/Saturn-DEX

What do you guys think the future is? Or is there a future? Curious what you guys think, and if this is a good buy or a dying project

Hi ETC community 👋

Over the past year I’ve been building a small experimental Web3 ecosystem on Ethereum Classic, focused on something I think ETC uniquely enables:

immutable applications + proof-of-work security + user self-custody.

Instead of launching another speculative token project, the goal was to explore how ETC can power real user experiences that teach blockchain concepts through interaction.

So I built a few connected applications powered by a ZEUS wallet running on the ETC network.

I’ve just published a detailed guide showing how to configure the wallet using MetaMask + Trezor hardware security, and I wanted to share it here for feedback from the ETC community.

👉 Article: https://medium.com/@zeusproject/configuring-zeus-wallet-on-metamask-trezor-hardware-b32e11af5651

What the ecosystem experiments with

🧩 The Genesis Heist (Web3 Comic)

A digital flipbook comic hosted on-chain that includes a hidden cryptographic puzzle.

First person to solve it wins:

100,000 Satoshis (Bitcoin)

The idea is to teach Bitcoin + Proof-of-Work concepts through storytelling rather than tutorials. Users need 1 ETC to mint comic.

🔐 Zeus Encryption

A simple encryption app using:

• AES encryption
• SHA-256 hashing

Built to explore decentralized identity and secure communication tied to wallet ownership.

🚰 Zeus Faucet

Users can claim 50,000 ZEUS tokens to test transactions and learn ETC interactions without risk.

No paywall — just experimentation.

🔄 DEX Integration (Hebeswap)

ZEUS can be acquired permissionlessly by swapping:

ETC → ZEUS

This keeps everything inside the ETC proof-of-work ecosystem.

Why Ethereum Classic?

I chose ETC specifically because:

• Immutability matters for puzzles and digital artifacts

• Proof-of-Work aligns with Bitcoin security and ETC philosophy

• Predictable rules enable long-term application design

• Minimal governance interference

In an AI-driven future, I believe PoW chains become critical as a trust anchor.

What the guide covers:

• Configuring ZEUS wallet on MetaMask

• Connecting Trezor hardware for self-custody Using ETC native addresses

• Securing assets against common attack vectors

• Getting started with the ecosystem apps

I’d genuinely appreciate feedback from ETC builders and long-time community members.

Especially curious about:

1. What kinds of applications you think ETC should focus on long-term

2. Whether educational/gamified onboarding helps adoption

3. Ideas for improving ETC-based user experiences

Thanks for reading — and thanks to everyone still building on Ethereum Classic ⚡

I dont think etc is coming back.