Case Study: Building a Full Onchain App From a Phone

Oct 30, 2026 · @Adam

When Praxis Market went live on Canopy earlier this year, it was a small milestone with an outsized story behind it. A single independent developer took an idea for an onchain prediction market and turned it into a working app that people could use, with its own rules, its own fees, and its own interface. They did it working entirely from a phone, with no team and no outside funding.

A few years ago, an app with that kind of independence would have been out of reach for almost anyone working alone. Getting it meant launching a Layer 1 blockchain, and launching a Layer 1 meant a team of engineers, months of infrastructure work, and a fundraise to pay for security before the first user arrived. Praxis showed that one determined builder with a mobile device and a good idea can now have the same flexibility, and ship it.

What Was Built

The app was a YES/NO prediction market. Each market posed a single question, participants bought shares on one side or the other, and the share price reflected what the market collectively believed the odds to be. Pricing used the logarithmic market scoring rule (LMSR), a well-established method designed for prediction markets that lets a market quote a price from its very first trade instead of waiting for buyers and sellers to arrive at the same time.

On Canopy, every app runs as its own blockchain, and that is what makes the scope notable. Most onchain apps are smart contracts that live on someone else's network, where they share space with every other app and live by that network's rules. Praxis was not a guest on another network. It had its own, which meant the developer decided how the market behaved, what it charged, and when it changed. The public repository shows the developer started from Canopy's open-source template, added the market logic, and built a web interface and a landing page on top. In other words, one person shipped the whole app: the rules, the network those rules run on, and the product people actually used.

How It Was Built: One Person, One Phone

According to the developer, they worked entirely from a phone, without a laptop or desktop, using freely available AI coding agents and language models.

Like most solo projects, this one was built in bursts. According to the GitHub history, the developer worked on the code on 82 days over about five and a half months, with stretches of several weeks away in between, and most of the real work happened in about 20 intensive days that account for more than 60% of all commits. Measured by time actually spent building rather than by the calendar, the pace is striking. After nine days of active work, the developer had the core of the app written, tests passing, and a working interface showing live markets on a test network. The central piece, the market engine covering pricing, predictions, and dispute resolution, was written in a single day. Across the whole project, the commit history suggests something on the order of 250 hours of hands-on work.

The point is not that a phone is the ideal place to build software. It is that building an app with the independence of its own blockchain used to demand a workstation, a team, and months of infrastructure work, and that had shrunk to something one person on a mobile device could get through.

What the Canopy Platform Handled

A project like this is only possible if the hard parts are already solved, and this is where the case study says more about Canopy than about the app.

The developer did not have to build the machinery underneath the app: the system that keeps every copy of the app in agreement, connects it to the network, and stores its history. That comes with Canopy. What remained was the part that makes the app what it is, the rules for creating markets, trading shares, and settling outcomes, written in a mainstream programming language. That split is the core idea behind the Canopy Stack. Builders write their app, and Canopy provides the blockchain it runs on.

The developer also did not have to find people to secure the app or raise money to pay them. Every app on Canopy is protected from its first block by validators who already secure the Canopy network, using CNPY they have already staked. For a solo builder, that removes what has historically been the biggest barrier to launching an app with its own blockchain, which was never the code. It was the cost of making the network trustworthy.

And the developer did not need to build launch infrastructure. Canopy Terminal handles deployment and helps an app form its early community, so a working app can go live without a separate token launch process or private fundraising.

Take those three things away, and what is left is roughly the amount of work one determined person can do.

What It Shows

This case study shows that the cost of building an app with its own blockchain, and the freedom that comes with it, has fallen far enough that a single person with limited resources and no desktop could take one from idea to mainnet. That is the claim, and the public record of the project supports it.

If you have an idea for an app and are wondering whether you have the resources to give it that kind of independence, the honest answer is that the barrier is lower than you might think. The Canopy build guide is the place to start.

Not financial advice. This post is not an endorsement of the Praxis application, its token, or its authors.

Sources

• Public repository (Canopy fork with market logic and frontends)
• Canopy build guide

‍