Getting started

Connect a wallet, switch to Arc Testnet, and start from the part of the app that matches your goal. Use Swap for execution, Pools for liquidity management, Send to transfer tokens, Bridge for cross-chain transfers, Deploy to launch tokens, NFTs, or contracts, Analytics for market summaries, and Activity for recent wallet actions.

1. Connect your wallet and switch to Arc Testnet.
2. Use the faucet in the top bar to get testnet assets.
3. Start with small swaps and verify balances before adding liquidity.

Arc uses a USDC centered stable hub flow. Presto runs a normalized Arc AMM so mixed decimal assets such as WUSDC can share the same hub safely without forcing raw unit parity.

Arc swap is intentionally simple. Choose the asset to sell from the USDC hub path, choose the asset to receive, review the quote, and confirm. Presto does not fake a heavyweight terminal layout where the onchain testnet data does not justify it.

• Arc uses modal token picking and a stablecoin first swap card.
• Both token inputs share the same wallet, balances, and execution settings.
• Swap quotes are read from the live onchain AMM rather than from a mock price source.

On Arc, Presto uses a stable hub AMM workflow centered on USDC and seeded pairs. Assets should only be enabled after the token address is verified and the pool is seeded with enough liquidity to avoid a broken or empty experience.

In practice, that means token listing, approvals, seed liquidity, and UI exposure all need to happen together. A token appearing in a public tokenlist is not enough by itself.

Liquidity providers on Arc Testnet earn USYC (US Yield Coin) passively based on their share of each pool and how long they hold the position. Rewards accrue continuously from the moment liquidity is first added — there is no lockup or staking step required.

The Send page lets you transfer any ERC20 token on Arc Testnet to another wallet address. You can send tokens from the DEX token list or paste any contract address to auto-detect a custom token.

• Select a token from the list or paste a contract address in the search field.
• Custom tokens are auto-detected: the app reads the symbol, name, decimals, and your balance directly from the contract.
• Enter the recipient address and amount, then confirm the transaction in your wallet.
• Sent tokens appear in the Activity page under the Sent tab.

The Bridge workspace uses Circle CCTP (Cross-Chain Transfer Protocol) to move USDC between Arc Testnet, Ethereum Sepolia, Base Sepolia, and Solana Devnet.

• Select a source and destination network, enter the amount of USDC to bridge.
• Where supported, you can specify a different destination wallet address.
• Transfer history is accessible via the clock icon in the bridge header, which slides open a history panel beside the bridge card.
• The history panel auto-closes after 20 seconds of inactivity.
• Bridge transfers are tracked in the Activity page under the Bridge tab.

The Deploy hub lets you launch tokens, NFT collections, and smart contracts directly from your browser on Arc Testnet. Your connected wallet becomes the contract owner.

All deployments are saved locally per wallet and listed on the Deploy landing page under “My Deployments”. Deploy actions appear in the Activity page under the Deploy tab.

The Portfolio page shows your token balances and LP positions on Arc Testnet. It reads balances directly from on-chain data for all supported tokens and displays your share of each liquidity pool.

The Analytics page tracks all time protocol volume, trades, and unique traders. Stats are read directly from on-chain Swap and LiquidityAdded events emitted by the Hub AMM contract, scanning from the deployment block with parallel chunk fetching for fast cold starts.

• All-time Volume shows total DEX volume since launch, normalized to USDC and including swaps plus the USDC leg of liquidity adds from the Hub AMM contract.
• All-time Trades counts every Swap event across all pools.
• Unique Traders tracks distinct wallet addresses that have executed swaps.

The Activity page shows a unified timeline of all wallet actions: swaps, liquidity adds and removals, bridge transfers, sent tokens, and contract deployments. Filter by category using the tab bar.

Presto docs stay practical. They focus on live network behavior, current assets, and implementation references instead of generic marketing language.

Presto is built to minimize data collection. The app reads wallet addresses, balances, swaps, liquidity actions, and bridge history only to render the product and respond to user actions.

Presto does not ask for personal identity data inside the app. Wallet addresses, chain activity, and public contract events may still be visible on public block explorers because they are part of the underlying networks.

If you connect a wallet, the app may store lightweight local preferences such as theme, slippage settings, bridge history, deployment records, and activity history in your browser so the experience remains consistent between sessions.

External services such as wallet providers, block explorers, RPC providers, and bridge infrastructure may apply their own privacy practices. You should review their policies before relying on those services.

Presto is provided for testnet use. Nothing on this site is financial, legal, or tax advice, and nothing here should be treated as a promise of production readiness.

You are responsible for reviewing every transaction before signing it. Blockchain actions are generally irreversible, and incorrect addresses, unsupported wallets, or low liquidity conditions can result in failed or poor outcomes.

The app may expose experimental features, including bridge flows and new liquidity paths. These features can fail, change, or be removed without notice while the product is still evolving.

By using the app, you accept that testnet assets have no guaranteed value and that the app is offered as is without warranties of uninterrupted availability or fitness for a specific purpose.

Presto does not rely on a heavy cookie system. Most state that persists in the product is stored in browser storage rather than traditional marketing cookies.

The app may use local storage or similar browser features to remember interface settings, wallet preferences, and bridge or transaction context that helps restore the current session.

If an external provider or embedded service sets its own cookies, those cookies belong to that provider and are governed by that provider's own policy.