Ethereum Chain Swap Monitor: Read DEX Events, Routes and Price Estimates
The Ethereum Chain Swap Monitor displays available Ethereum DEX swap observations, pool information, and summary panels. Its scope is Ethereum. It should not be…
Read articleQuietly building useful things
Creative thinking —
in code and systems,
end to end
I am a hobbyist, curious how things work under the surface. I make and run software end to end — hands-on architecture, backends, real-time dashboards, standalone and web applications, WordPress themes and plugins, blockchain tooling, trading systems, media processing and monitoring. Code is art for me — a creative activity. I design it, write it, and put it where it fits: my own servers, a VPS, Docker stacks or the cloud — I am not limited to one. Then I keep it healthy — debug under real use, smooth what is slow, improve from real data.
- Standalone tools
- Python / FastAPI
- Node.js / TypeScript
- WordPress / PHP
- VPS · cloud · dedicated
- Real-time & WebSocket
- Blockchain & Web3
- React / Vite
How I work
Research, ship, measure, improve — in that order
How I approach every project, from a new idea to a bug fix.
Understand the domain first
Before writing code I research how the domain actually works: its protocols, data formats, rules and constraints. Building on wrong assumptions wastes more time than the research saves. I read specs, trace real traffic, and sometimes write throwaway prototypes to verify a constraint before committing to an architecture.
Ship a narrow version, then expand
I start with the smallest version that actually runs and handles real input — one data source, one screen, one use case. That gives a concrete baseline to measure and a real surface for feedback. Features are added on top of working code, not promised in a spec that never ran under real conditions.
Optimise what the data says is slow
I measure before I optimise. Structured logs and metrics from the start mean that when latency spikes or memory climbs there is a trace to read rather than a guess to make. Fixes target what the measurement shows — cache hit rate, a query, an async boundary or a front-end asset size — not the part of the code that merely looks suspicious.
Capabilities
What I build — no artificial limits
Web apps, standalone tools, backends, data pipelines, WordPress, blockchain integrations, monitoring, and more. I use whatever the project needs.
01
Web & standalone applications
I build web applications that run in a browser, standalone tools that run locally, and hybrid systems that use both: dashboards, analysis tools, management panels, monitors and custom tools built for a specific workflow. User interface, data layer, auth, and deployment are all part of the same deliverable.
02
Backend services and APIs
Python 3 with FastAPI and asyncio is my primary backend stack. I also write Node.js and TypeScript services when the project calls for it — real-time pub/sub, bot backends, or JavaScript-ecosystem integrations — and use Rust or C# when the target calls for them. I design REST and WebSocket APIs, background workers, aggregation pipelines and scheduled jobs. Services are structured to be testable and readable without a guided tour, and run fine on a single server without an orchestration layer.
03
Real-time data and blockchain
A significant part of my work involves live or near-live data: market and exchange feeds, on-chain events, large streams of measurements. I build the ingestion, normalisation, aggregation, and caching layers, then wire them to dashboards that update in real time. I also write on-chain execution logic, using Web3 tooling.
04
Data engineering and analysis
Raw event data from an API or a blockchain node arrives in a shape that is rarely directly useful. I design the transformation pipeline: time-bucketed aggregations, rolling windows, ranked lists, ratio calculations, anomaly signals, and structured exports. I use SQLite, PostgreSQL, DuckDB, and in-memory caches depending on the access pattern and hosting constraints. The output is something an operator can act on — not a chart that looks impressive but answers no specific question.
05
WordPress — themes, plugins, integrations
I build WordPress products from scratch: custom themes with no unnecessary dependencies, plugins with clean admin UIs and proper WP hook integration, REST endpoints for JavaScript consumers, and multi-layer caching that does not break on a publish event. I have built and maintain live WordPress plugins that bridge between a WP front end and a private Python or Node.js backend running on a separate server via Cloudflare tunnels.
06
Infrastructure, performance, and security
I run Linux servers myself — nginx, systemd, SSL, log rotation and firewall configuration — and keep my projects in git. When something is slow I measure it instead of guessing. I also care about application-level security: input validation, rate limiting, brute-force protection, nonce hygiene for on-chain transactions, and keeping secrets out of code.
Applications
Selected public work
Projects in very different stages: some run publicly, some are tools I use myself, some were test projects to learn something, some are prototypes. The story behind each one is on the projects page on GitHub; the public overviews cover what each project does. The code itself lives in private repositories.
MEXC — live trading statistics
Buy/sell volume and per-pair stats from the MEXC exchange, with a live dashboard on this site.
Open app
Ethereum Gas Tracker
Live Gwei, history charts, and a fee calculator for planning Ethereum transactions.
Open app
Dynex MEXC Balance Monitor
Real-time balance monitoring for Dynex (DNX) on MEXC exchange.
Open app
Celestial Lab
Seven space modules in one full-screen observatory: satellite tracking, space weather, solar imagery, orbital crews, exoplanets, asteroid encounters and launch countdowns.
Open Celestial Lab
Dynex large transactions monitor
Large Dynex transfers as they hit the chain — threshold filter and decoded fields.
Open app
Ethereum Chain Swap Monitor
Live DEX swap activity across Ethereum pools — volumes, buy/sell pressure, top tokens, and the biggest swaps as they land on-chain.
Open app
Rocinante Command Center
A fictional Rocinante-inspired ship simulator for entertainment and interface testing. Ship telemetry, contacts, crew and sensors use generated simulated data, not real mission observations.
Open app
European Electricity Monitor
European electricity intelligence — day-ahead prices, load, generation mix and cross-border flows across 40+ bidding zones.
Open app
Russian DC Observatory
Compare Russian Internet connectivity, service reports, infrastructure records and website-access observations while keeping sources and uncertainty visible.
Open observatoryBlog
General writing about the projects
Articles about the applications on this site and the data behind them.
European Electricity Prices: Zones, Day-Ahead Units and Delivery Intervals
The European Power Prices board makes available day-ahead observations easier to compare across bidding zones. It can help you understand a price curve or…
Read article
Sun Live in Celestial Lab: Solar Imagery, Wavelengths and the 3D Model
Sun Live combines solar imagery with active-region and flare information. Those panels are useful together, but they are not interchangeable observations. A solar image,…
Read articleStack
Technology choices — and why
Technologies I use and run myself. Each choice has a reason.
Backend
Python 3 with FastAPI and asyncio for APIs, background workers, and data services. Node.js where the ecosystem or project demands it, with TypeScript in some projects. They run on my own servers, a VPS, in Docker or anywhere else a project needs — I am not limited to one. I also use Rust and C# when the target is a native application, and I am not afraid to reach outside the comfort zone when the problem demands it.
Frontend
Operator dashboards and standalone tools are HTML, CSS, and vanilla JavaScript — no build step, instant iteration, easy to debug in a browser developer tools panel. React with Vite where client-side routing, component state, or dynamic document structure make the project genuinely cleaner. PHP and WordPress template system for CMS-driven public sites. TypeScript in some projects, where typed contracts between layers help.
Data & storage
SQLite for single-writer services where ACID guarantees matter and concurrency pressure is low. PostgreSQL with asyncpg for multi-user or high-write workloads. DuckDB for analytical queries over flat files. In-memory caches, pre-aggregated JSON artifacts, and RAM mirrors of chain head data for hot-read paths that cannot afford a round-trip to disk on every request. Storage is chosen by access pattern and hosting cost — not by what is fashionable.
Infrastructure
My own Linux servers for most things — direct access, systemd, nginx, Cloudflare tunnels. Docker and docker-compose where containerisation makes sense for a project. A VPS, a dedicated server or the cloud are fine too: I can deploy wherever a project needs it. Custom-built monitoring and hardware telemetry dashboards. Everything in git. The deployment approach follows the project requirements, not a fixed doctrine.
About
Builder — curious how things work
I am a hobbyist, not a professional developer — what drives me is curiosity about how things work under the surface. So I build projects end-to-end — hands-on architecture and craft across Python and Node.js backends, real-time dashboards, web and standalone applications, WordPress plugins, blockchain tooling, video processing, and the infrastructure underneath. Code is art for me — every project is something that works, holds up under real conditions, and is worth building.
A large part of my work is data-intensive: live feeds, event streams, analytics and services running continuously on my own servers. I also build tools because existing solutions did not fit or did not exist — one place to run and watch everything, monitors, media pipelines. The common thread: I learn fast, build what the problem needs, and keep it running.
The About page has a full breakdown of skills and how I work, and the projects page on GitHub tells why each project was built. Use Contact to discuss a project, a collaboration, or a technical problem.
Read more
Full stack
Backend, front end, infra, ops
Live
Running for real — not demo deployments
Data
Real-time feeds, analytics, operator tooling
Ops
Built to run, not just to launch