Token Launches Have Always Been Priced in Something That Moves. On Arc, They Aren't.
Every token launch of the past decade carried a flaw that had nothing to do with the token being launched.
It was the gas.
When a team deploys a token contract, locks liquidity behind a timelock, or releases a vesting tranche to contributors, each of those actions costs money denominated in an asset whose own price is in motion. A launch budgeted at a fixed dollar figure on Monday costs something different by Thursday. Transactions that fail during volatility cost real money and return nothing at all. A distribution schedule running eighteen months forward forces a treasury to hold a reserve of a volatile asset for no reason other than paying to move its own tokens.
The industry absorbed this the way you absorb weather. It is not weather. It is a design decision, and Arc is the first Layer-1 arriving at institutional scale to make a different one.
As of today, TrustSwap is live on Arc.
The unit of account was always the part that was broken
Arc is an open, EVM-compatible Layer-1 built for real financial markets, and its defining choice is that transaction fees are denominated in dollars rather than in a volatile network asset. Stablecoins are gas, starting with USDC.
That sounds like a convenience feature. It is closer to a change in the unit of account, and units of account decide what kinds of businesses can exist on a platform.
Consider what becomes possible when the cost of an onchain action is a known dollar figure eighteen months out. A vesting contract can be budgeted the way a payroll run is budgeted. A launch can be quoted to a client as a fixed cost rather than an estimate with a volatility disclaimer attached. A treasury can stop holding an unrelated asset purely as an operating expense buffer. None of that is exotic. It is how every other category of financial software already works, and crypto has spent a decade pretending the alternative was acceptable because there was no alternative.
Arc pairs that with deterministic finality in under 500 milliseconds — a block that closes is final, not probabilistically final — and a fee model that smooths demand across a weighted moving average rather than adjusting block by block. Execution runs on Reth. Consensus runs on Malachite, a Byzantine Fault Tolerant engine derived from Tendermint. The engineering is deliberately unglamorous. That is the point.
What TrustSwap turned on this morning
Our products are live on Arc from the first block, and each addresses a different part of what a new chain immediately needs.
Team Finance brings token creation, vesting schedules, and liquidity locking to Arc on audited, production-tested contracts. Any project deploying on the network can lock liquidity and vest team allocations onchain from day one, verifiable by anyone, without commissioning custom contracts or waiting on an audit cycle. The thing a new chain lacks most in its first weeks is not liquidity. It is a credible way for anyone to check whether a team has actually locked what it claims to have locked. That gap is what kills early trust on a young network, and it is closed on Arc as of today.
TrustSwap Launchpad supports Arc with vetted, structured primary issuance. Teams raising on Arc get a launch path with real diligence attached rather than an open contract and a hope. Predictable dollar-denominated fees matter more here than anywhere else in our stack, because a raise is the one moment where a project has the least margin for a surprise operating cost.
The Crypto App supports Arc from launch, which means market data, news, and portfolio tracking for Arc assets sitting inside an app crypto investors already check daily. For teams building on the network, that is retail distribution available on day one rather than something to be negotiated for six months later.
The common thread is not that we ported three products to a new chain. It is that the tooling a chain needs on day one is the least interesting and most load-bearing category of software in crypto, and it is almost always absent when a network opens.
The strongest argument against all of this
Here is the case against, made properly.
Day-one partner lists are marketing artifacts. Every chain launch produces one. Most of the names on most of those lists ship a deployment, publish a post, and never touch the network again. Skepticism toward a company announcing it is live on a new chain is well-earned skepticism.
The technical claim is also less novel than it sounds. Paying gas in a stablecoin has been possible through paymasters and account abstraction on other networks for years. Arc is not inventing dollar-denominated fees so much as making them the default rather than a workaround.
And the sharpest objection is one we should not dodge: Arc's validator set is permissioned. Participation is currently selected on operational resilience, geographic distribution, and regulatory compliance, and the eleven institutions announced in August — among them BlackRock, DTCC, ICE, Mastercard, Standard Chartered, and Visa — are not a set anyone would describe as permissionless. If your position is that a chain validated by regulated financial institutions is a database with extra steps, that position is coherent. It is not a strawman and it should not be waved away.
Why we built anyway
We take the permissioning objection seriously, and our answer is not that it does not matter. It is that it is a real trade, openly made, and different applications will weigh it differently.
A memecoin launch has no reason to care about a geographically distributed institutional validator set. A tokenized treasury product or a corporate payroll run in stablecoins cares enormously, because the counterparties involved cannot transact on infrastructure that settles probabilistically and prices its fees in an asset their auditors will question. Those two use cases were never going to share a chain, and the past four years of everyone pretending otherwise produced a lot of infrastructure that served neither well.
Our position is the boring one. We do not need to know which chain wins. Team Finance has shipped across many networks for years precisely because the token management problem is identical everywhere and the chain underneath is an implementation detail. Being live on Arc from block one is not a bet on Arc displacing anything. It is a bet that a chain where a dollar costs a dollar will attract a class of builder who was never going to show up otherwise, and that those builders will need liquidity locks and vesting schedules exactly like everyone else.
If Arc succeeds, the infrastructure is already there. If it does not, we built tooling for a network in a week and learned something. That asymmetry is why you support a chain on day one instead of waiting for the data.
The question worth sitting with
The interesting thing about Arc is not the chain. It is what becomes buildable when the cost of an onchain action stops being a variable.
Subscription billing settled onchain. Payroll with an eighteen-month forward cost model. Vesting contracts a CFO can put in a budget without a hedging line item. None of those were impossible before — they were just unattractive enough that almost nobody built them, and the ones who tried spent most of their engineering effort abstracting away a problem that should not have existed.
That constraint is gone as of today. What gets built in its absence is the part nobody can predict, including Circle.
Start with the network at arc.io. If you are deploying a token there, lock it at team.finance.