Across is live on Arc Testnet: day-one crosschain transfers for builders
# Partner Spotlights
# Spotlights
# Crosschain
# developer tools
# Day One Architects
Day-one crosschain transfers for builders
Tim Baker
Across is now live on Arc Testnet, with contracts deployed and available for developers today.
For most real apps, crosschain compatibility is core infrastructure. If you are evaluating Arc, building an early prototype, or pressure-testing user flows, you almost always hit the same wall: you need assets to arrive on Arc without turning onboarding into a scavenger hunt.
Across is currently live on testnet to enable devs to build while preparing for mainnet launch.
Crosschain transfers are available to test on testnet immediately. This enables you to build against the protocol and be ready for day 1 of mainnet.
USDC and other Circle-issued assets live across many supported blockchains, so smooth cross-chain experiences matter.
Across’s deployment on Arc testnet lets you test end-to-end cross-chain flows without risking real funds.
Teams get a familiar, battle-tested bridging experience many builders already know.
It reduces friction when moving assets onto Arc during evaluation and early builds.
What you can do with this:
Onboard users with fewer steps
If your flow starts with "get funds onto Arc", a live bridge removes a bunch of hand-holding and weird workarounds.
Test real product paths earlier
Instead of mocking balances or relying on single-chain assumptions, you can test the parts that actually break in production: deposits, withdrawals, rebalances, treasury moves, and "move funds then do X" flows.
Build composable apps that assume liquidity can move
Arc is designed for composability and real economic activity. Crosschain connectivity is part of that story, and Across is one of the crosschain options participating in the Arc testnet ecosystem.
Where Across fits
Across is an intents-based interoperability protocol that supports bridging and crosschain swap-style flows.
The important part for builders is not the internals. It is that you can treat "assets need to move in and out of Arc" as a solved integration problem while you focus on your actual product.
Common Patterns for Builders:
Funding and onboarding: move assets onto Arc so users can start doing the thing your app does.
Treasury and ops: move assets in/out for treasury management, payouts, and operational flows.
DeFi and exchange flows: deposits/withdrawals and crosschain liquidity access as part of a larger workflow.
Across’s support for Arc Testnet means crosschain is available immediately for teams building and testing on Arc. This reinforces the "day-one readiness" theme: builders can start with real flows.
Are you building on Arc? How do you plan to use Across in your Apps? What kind of experiences do you have with this? Tell us in the comments below!
