we say "uponly was built in one night" a lot. it is true, and it is also one of those founding facts that has become more meaningful over time, not less. this is the actual lore — what happened that night, why it was that night and not a different one, and how the constraints of building a perp dex in eight hours shaped every product decision we have made since.
we have told pieces of this story in dms and group chats. this is the consolidated version, written for the audience that has asked enough times that it deserves to live somewhere permanent.
the conditions on the night
the build happened on a single overnight session in 2024. we had three things working in our favor and one thing working against us:
- in our favor: avantis was live on base, with public contracts and reliable execution. we did not need to build the perp engine.
- in our favor: privy and the base ecosystem had matured enough that wallet onboarding was no longer the multi-week project it had been a year prior.
- in our favor: we had been arguing about the consumer perp problem for months, so the design decisions were already mostly made.
- against us: we had no working code at the start of the night, and a self-imposed constraint that the product had to be functional and tap-rip-shareable by morning.
the constraint was the whole point. we wanted to know if the product we had been describing could exist. the only way to find out was to build it before we had time to overthink it.
what we built
by morning, the working prototype did exactly four things. you could connect a wallet. you could fund it on base. you could tap a button labeled "rip" and a perp position would open at a random pair and side, with a configurable leverage between 75x and 500x. and you could screenshot the result and share it. that was the entire product. no order types, no asset picker on the home screen, no portfolio dashboard, no advanced settings.
the design philosophy behind every choice that night was negative selection. instead of asking "what should we add," we asked "what can we remove without breaking the loop." the answer was nearly everything. once we had stripped the product down to the rip button, we knew we had something. for the design reasoning that came out of that night, see the rip button and the one-tap philosophy.
why one night mattered
one-night builds force decisions. you cannot consult with stakeholders. you cannot run a survey. you cannot a/b test a button label. you just decide. some of those decisions are wrong and you fix them in the morning. most of them turn out to be correct because constraints surface the right answer faster than committees do.
the decisions made that night that turned out to be load-bearing:
- random pair, random side. the controversial call. it removes the conviction question and matches what the audience actually wants. we still get pushback on this. we still believe it is right.
- high leverage by default. 75x to 500x. anyone who would size for survival is on dydx, not us. the default has to match the visit type.
- no fee on losing trades. fee at entry would have ruined the rhythm of the rip. removing it turned out to be the structural choice that defines the entire fee model.
- screenshot share card built into the close flow. trades are content. content is distribution. closing the loop in-product cost us four hours that night and has paid off every day since.
- no confirmation modal. one tap means one tap. we had a modal in the first hour and removed it before sunrise.
the things we did not get right
we will not pretend the one-night build was perfect. it had real problems we fixed in the weeks that followed. the share card was ugly. the leverage slider was too sensitive. the rip animation was missing entirely. the wallet funding flow had two unnecessary screens. we shipped all of those fixes within the first two weeks.
the deeper miss was that we underestimated how much the affiliate program would matter. the night-one product had a referral link but no real share. it took us another month to realize that the creators bringing audiences needed structural rev share, not just a percentage cut. once we made that change, the growth curve changed shape. for the math, see the uponly affiliate program.
why we keep referring to that night
the one-night build is not just an origin story. it is the rule we use to decide what to ship next. every new arcade game we add has to feel like the rip — one tap, no setup, screenshot at the end. every new feature has to pass the test of whether we could have built it in one night if we had to. if the answer is no, the feature is probably too complicated and the audience will not use it.
this is also why we ship weekly. the one-night build proved that you can produce a working consumer product in a tight time window if you have made the design calls correctly. weekly shipping is the sustainable version of the same principle. one big build per night, one small build per week.
what one night gave us that a long roadmap never would have
a long roadmap would have produced a product that looked like every other perp dex. by the time the roadmap was done, we would have added an order book, an asset picker, a portfolio view, advanced order types, and a complex fee schedule. all of those would have made the product worse for the audience we built it for. one night did not give us time to add any of that. the absence of those features is now the defining feature.
this is the central irony of consumer crypto. the products that win do less, not more. they are easier to onboard, easier to use, and easier to share. they are not stripped-down versions of professional tools. they are different products designed for a different visit type. one night was the constraint that kept us from accidentally building the wrong thing.
how this shapes what comes next
the arcade is a series of one-night-spirit cabinets. the rip is the first. there are more in development that share the same shape — one screen, one button, fast feedback, share-ready output. some are perp games. some are not. all of them are constrained by the same question we asked that night: could we ship this by morning if we had to?
if you want to feel the night-one product yourself, open uponly and tap rip. the surface area is bigger now. the rip is the same. for the broader history of why this product category exists, see a short history of the degen.