I build small analytics products for crypto markets, and publish what I find while building them.
The products are narrow on purpose: one question, answered from market or on-chain data, shipped as a standalone thing rather than a module of a platform.
Bitcoin Risk Brief — a daily Bitcoin risk signal that shows its own data freshness on the page. A deterministic 0–1 metric, a scenario price ladder, seven locales, and a documented surface for AI agents. Analytics and research context, not financial advice. source
What DAOs actually fund — a survey of 93 funding proposals across 29 governance forums: what gets funded, for how much, and through which channel. The collector, the raw data and the analysis are all in the repository, so the numbers can be checked against their source threads instead of taken on trust.
Both live under minihub.app.
Backend and distributed systems, mostly Java.
metacfg4j — a configuration library that puts a business abstraction over CRUD services, a DSL and MVP. crypto-scout — an event-driven microservice set that ingests crypto market and on-chain events: collector, message queue, analyst, TimescaleDB stack.
I write the method down next to the result. If a number is published here, the code that produced it and the data it ran on are published with it — a disagreement should be with a rule you can read, not with a figure you have to believe.
Limits go in before conclusions, not in a footnote.