Loading route...
Swap>
Swap SOL to PEPE
Route overview
SWAPSOL to PEPE
This is a direct asset-to-asset route where the operational route definition matters more than forcing the pair into a stronger narrative family. The source asset is a major ecosystem token, so the route reflects a transfer of value out of an established crypto network position. The destination asset is a meme token, so the terminal position carries a materially higher speculative component than a BTC or stable-value destination.
Non-custodialLive routeNetwork-aware routing
Route note: this asset is currently supported through a single send network, so the preset shown here reflects the only available source rail: Solana.
Route profile
This route is generally more relevant as a specific asset conversion than as a repeatable macro-style allocation pattern. This profile is generally associated with portfolio reallocation or ecosystem rotation from one major asset into another destination. This profile is generally associated with taking on higher directional risk rather than with preserving capital or maintaining treasury liquidity.
Send
SOL on Solana
Receive
PEPE on Ethereum
Live swap card
Swap SOL to PEPE with the route prefilled.
Current rate
Select a valid pair to fetch a live variable rate
You send
Network
Select network
Variable rate creates the shift first. The shift page shows the deposit range before funds are sent.
You receive
NetworkSelect network
Live unit rate
--
Current live rate before the shift is created.
Deposit rule
[warning] Select a pair to see the live min and max deposit range before you create the shift.
Status note
After you create the order, the app redirects to a dedicated shift screen with the QR code, countdown, waiting state, and live status polling.
Live route context
Builder first, then route-specific timing and limit context.
Send
SOL on Solana
The route starts with the exact deposit asset and network selected for this page.
Receive
PEPE on Ethereum
Settlement is sent to the destination asset and network defined by this route.
Timing
Provider-driven
Timing depends on deposit detection, provider routing, and final settlement on Ethereum.
Deposit limits
Live minimums
Minimums and maximums are route-specific, and higher-volatility destinations should always be checked again on the live shift page before sending funds.
How this swap works
1
Choose SOL as the asset you send and PEPE as the asset you receive.
2
Confirm the route starts on Solana and settles on Ethereum before creating the shift.
3
Enter a PEPE receiving wallet that matches the destination network exactly.
4
Create the shift, follow the deposit instructions, and track settlement until PEPE lands on the destination side.
Route-specific notes
Because this is a long-tail direct route, the live builder and final shift page remain the authoritative source for route definition before funds are sent.
This route relies on a compatibility-oriented rail, which generally implies broader wallet support and more predictable address handling.
Related routes
Reverse route
Looking for the reverse path?
Move in the opposite direction while keeping the same pair context available from a dedicated route page.
Another route that still settles into BTC, with a different send asset or deposit network before Bitcoin delivery completes.
Use the same send asset but redirect value into a different destination asset and ecosystem.
Use the same send asset but redirect value into a different destination asset and ecosystem.
Land in the same destination asset through a different source route, useful when the starting wallet or source network changes.
Explore tokens and networks
Pair FAQ
What should I verify before swapping SOL to PEPE?
Verify the send asset, receive asset, destination wallet, and exact network path shown by the live builder, because the route definition is pair-specific.
Why is SOL to PEPE treated as a direct route?
Some token pairs are more accurately described as exact asset-to-asset conversions than as members of a stronger route family. In those cases, the pair definition itself carries the most relevant context.
Why is this route described as compatibility-first?
Because the selected network is chosen primarily for wallet support and address-format predictability rather than for minimum transfer cost alone.
Route disclaimer
Rates, minimums, and maximums are provider-driven and can change before the shift is created.
Always verify the deposit instructions on the shift page before sending funds.
The selected receiving network must match the destination wallet and asset route.
For SOL to PEPE, the live builder and shift page remain the final source of truth.