The useful thing to know about Derek Alia is that the nouns keep changing while the verbs stay put. He has built apps, interfaces, communities, markets, and now tools for agent-driven scientific work. Across each project, he returns to the same motions: open the system, make its rules visible, give outsiders something they can extend, and watch what happens when real people get their hands on it.
That continuity is easy to miss because Alia became publicly known through Futureswap, the decentralized perpetuals protocol he co-founded in San Francisco. Crypto supplied the vocabulary: liquidity pools, governance tokens, smart contracts, leverage, Layer 2 networks. But his deeper interest was less about a particular asset than a particular architecture. He wanted software that could coordinate people without forcing every action through a central desk.
His current public profiles place him at muni, a collaborative environment where AI agents can work with scientific tools. It looks like a turn. Seen from one level higher, it looks more like the next experiment in a long-running question: how much useful complexity can software expose without making participation feel like a request for permission?
The platform instinct came first
Alia studied computer science at the University of Washington from 2011 to 2014 and later attended Hack Reactor's software engineering immersive. In a 2022 podcast conversation, he described his background more casually: “My background is mostly in software engineering, just building cool stuff.” Early iPhone apps gave him a front-row view of what happens when a new platform arrives with an accessible way for developers to distribute their work.
His analogy was the App Store. Apple supplied a device, a software kit, and a marketplace. Developers supplied the unpredictable part. Entire categories appeared because people outside Apple could build for a new surface. Alia saw Ethereum in similar terms. A blockchain could be more than a ledger. It could be an open execution layer, one where developers assembled programs that moved value as readily as mobile apps moved information.
Before Futureswap, he worked in frontend development at Aragon, an early project for creating and operating decentralized organizations. He also worked at Simplr and co-founded Tribes, a decentralized content platform. The projects differed, but all sat near the awkward seam between powerful infrastructure and ordinary human use. An interface was not decoration. It was the place where an abstract promise about openness either became real or collapsed into friction.
Three days, then the harder decision
Futureswap was founded in 2019. Its premise was compact even if the implementation was not: create a non-custodial market where people could take leveraged positions without depositing their assets with a centralized exchange. Liquidity providers would supply capital to pools. Traders would pay fees. Smart contracts would enforce the rules, and a governance system would give token holders a say in changing them.
The alpha launched on Ethereum in April 2020. Within three days, activity was growing at a reported 130 percent per day. The team then pulled the alpha and went back to work. The reaction revealed demand, but demand was also pressure. A market handling other people's capital could not treat momentum as a substitute for resilience.
That choice captures a less theatrical form of founder nerve. Shipping is celebrated. Stopping is harder to narrate. Alia and the team spent the following months testing and rebuilding. When the next version emerged on Ethereum mainnet in January 2021, Futureswap's first public update reported more than $40 million traded in its first week and $25 million deposited in the ETH and USDC pool. The release had been audited by OpenZeppelin and Trail of Bits.
Historical protocol figures are shown with the dates on which they were publicly reported.
A product designed as a primitive
Futureswap did not try to manufacture all of its own liquidity. Its later versions connected with established automated market makers and moved to lower-cost networks including Arbitrum and Avalanche. The product ambition was to become an execution layer that other communities could use. A group that wanted a new market could rally support around a pair. Developers could compose other products on top of the protocol.
Alia called this quality primitive, in the engineering sense: a basic building block with clear behavior. The word is revealing. A monument asks to be admired as finished work. A primitive gains value when somebody else combines it with something the original builder did not foresee.
How the coordination loop worked
The user story complicated the neat system diagram. Alia said that while traveling he met people who used Futureswap in ways the team had not predicted. Each meeting stretched the founders' mental picture of a typical user. It is a small anecdote with a large product lesson: open systems are tested by the people who do not resemble the persona in the planning document.
By February 2021, Futureswap's V2 had reported more than $500 million in volume. In October, the company raised a $12 million Series A through a token sale. Ribbit Capital, Framework Ventures, True Ventures, and Placeholder co-led the round, and reported total funding reached $13.6 million. The core team numbered eight. Futureswap said cumulative volume had passed $4.2 billion.
Reported volume milestones
What pressure taught him
The metrics gave Alia a platform to talk about access and transparency, but his founder advice was deliberately unromantic. The work would be harder than imagined. It would take longer. It would require more resources. Scope would need to shrink. Culture, team values, and partners deserved deliberate attention before a problem forced the issue.
- 01Assume the work is more difficult than the first model suggests.
- 02Budget more time and more resources than the optimistic case.
- 03Reduce scope before complexity reduces it for you.
- 04Treat culture, values, and partners as part of the product.
He was equally pragmatic about regulation. On a 2021 panel, Alia argued that decentralized-finance builders should cooperate with lawmakers, explain the protections already embedded in transparent systems, and communicate risks plainly. Permissionless did not mean consequence-free. Open code could make rules inspectable, but it did not absolve builders from explaining the machinery or listening to the world around it.
That combination, permission with legibility, appears throughout his work. He likes systems that allow action without a gatekeeper. He also talks about audits, pressure tests, governance, and time. Freedom is a product property only when people can understand the conditions under which it works.
The industry changes; the architecture rhymes
Alia's present work has moved beyond the public identity that Futureswap gave him. His LinkedIn profile now leads with muni, while his X bio says he is “wizarding” there. The San Francisco company describes itself as a collaborative environment for agentic scientific exploration. Its product lets people connect AI agents with specialized models and computational tools, keeping inputs, runs, results, and next steps in a shared workspace.
The domain is different, but the old platform instinct is easy to recognize. muni is code-first. Users can bring their own agent. Tools are exposed through a command-line interface. Work can move from a question to computation and onward to experimental validation without disappearing into a sealed demo. The goal is less a single clever answer than a visible, repeatable workflow.
Even the name carries a local and reflective joke. The team says muni refers both to San Francisco's transit system and to “muni-muni,” a Tagalog phrase meaning to reflect or contemplate. It suits a builder whose public career has been a sequence of infrastructure projects: routes, rules, shared surfaces, and invitations for other people to move through them.
Alia's older personal bio adds a useful bit of texture. Away from the keyboard, it says, he can be found rock climbing, skiing, or running. These are activities with feedback that arrives quickly. The surface holds or it does not. The line works or needs adjusting. You commit, test, and respond.
Software rarely offers feedback so cleanly. Markets are noisy. Communities surprise their creators. New tools collide with old institutions. Yet Alia's response across those environments has been consistent: build the surface, make the constraints visible, and let use reveal what the diagram missed. The career makes sense not as a series of fashionable turns, but as one long attempt to give more capable systems to more people without hiding how those systems work.