Game & proving ground
A robot world went all in on the NFT boom. Then the boom ended.
Why we built it
We needed something that would hammer Canic and IcyDB under real load - not synthetic benchmarks, but an actual application with messy state, concurrency, and things going wrong in inconvenient ways.
Running the foundations under genuine application pressure has already surfaced issues that would otherwise have bitten someone else later - and forced us to get better at telling a framework bug apart from “we integrated it wrong”.
A live game is a real workload, not a demo. Cycles get spent, storage fills up, and the numbers we tune against come from something people are actually playing.
The whole thing, not a web app with a blockchain bolted on the side. We’re not going to labour the point - it simply happens to be the reason what we build can do more than most things in this category.
Every asset-production problem we solve here is one we don’t have to rediscover in Dragginz. The workflows carry over even when the individual assets don’t.