My journey trying to build something useful

Over the past year I've been thinking a lot about Web3. Not the trading, not the speculation, not the casino. I don't trade crypto. I don't follow the markets.

What fascinates me is the underlying idea: decentralized systems with code as the only authority. The technology itself.

I've been a backend engineer for over a decade. Rails, SQL, the usual stack. But like many engineers, I burned out. The excitement to build faded. You know the feeling. You're competent, productive, but not discovering anything anymore.

Then I looked seriously at blockchain. Not as an investor, but as an engineer. I asked myself: what would an application look like if built with absolute fidelity to what blockchain promises?

• Real utility (useful for the masses, not DeFi nonesense)
• NO off-chain layers (100% on-chain)
• NO insider advantages (fair economics)
• NO dependence on investors (self-sustaining)
• NO pointless tokenomics (ETH in, ETH out)

Those five principles became my compass. I tried to build something that never violated them. But the Web3 ecosystem is built around tokenomics and speculation. There's no blueprint to follow.

So I started pulling my own thread: I wanted to build something useful, deterministic, fully on-chain, with no complicated tokenomics.

A simple game like TicTacToe with real ETH stakes? Interesting, but too narrow.

Then the frame shifted. I wasn't building a game anymore. I was building a tournament layer. A universal competitive infrastructure that's fair, open-source, and 100% on-chain.

That's when the hard problems started. How do you handle draws on a decentralized platform? How do you stop players griefing opponents without central authority? These aren't just technical questions. They're moral ones. They forced me to think deeply about fairness, about building a system nobody controls and nobody can manipulate.

The answers surprised me. Forget Kubernetes, Redis, all that complexity. With these constraints (fully on-chain, truly open, completely decentralized) the legacy stack collapses into something elegant. A client talking directly to contracts. No servers. No databases. No company. Just code.

That freedom changed how I think about software.

So I built ETour

A 100% on-chain tournament protocol, now live on Arbitrum. Players pay an entry fee, compete, the best player wins and takes the pot. Code decides everything. No intermediaries.

As Web3 should be.

I open-sourced it so developers can build their own games on it and inherit all of its features for free.

I'm not here to tell you this is revolutionary. I built this because it felt like a problem worth solving. ETour is what came out the other side.

The code is public. The contracts are immutable. The logic is yours to verify.

PS: The technical docs are not final and will be updated soon.

https://etour.games

https://etour.games/whitepaper

https://etour.games/manual

https://etour.games/docs

TLDR: ETour is useful, it's live, and it's open-source. Go ahead and play on it, or build your own game using its 100% on-chain and open source tournament modules.