Know what
crosses.

Last reviewed 6 September 2026. CROSSING is an independent project. Names of chains and protocols describe technical integrations; they do not imply endorsement.

What works today

• Inspect a Solana mainnet mint using finalized on-chain account data. Read supply, decimals, token program, mint authority and freeze authority.
• Read an indexed market label and liquidity figure when available from DexScreener. Market data may be delayed or absent.
• Calculate exact proposed token amounts and an indicative initial token / ETH pool ratio.
• Connect an installed Solana or EVM wallet to include its public address in your plan.
• Save a plan in this browser, export it as JSON, or import a saved plan. Imported token data must be re-inspected before export.

The two-way route

For an existing SPL token, a lock/unlock adapter can hold original tokens on Solana while a corresponding omnichain fungible token (OFT) circulates on the destination chain. Burning the representation can send an authenticated message to release originals.

This requires a deployed Solana OFT program and escrow, a destination OFT contract, trusted peer configuration in both directions, and correctly configured messaging verification and execution. A 1:1 quantity relationship does not guarantee dollar value, a trading market, instant delivery or uninterrupted redemption.

The engineering package follows the LayerZero Solana OFT architecture. Existing tokens with revoked mint authority require the adapter approach; a native mint/burn OFT requires mint authority.

The permanent route

A permanent migration retires participating holders’ original tokens and issues a configured replacement. Burning is irreversible. Holders who do not participate remain on Solana.

Permanent-mode calculations are provided for planning only. A permanent burn-to-destination protocol is separate engineering work and is not implemented in this release. It is not enabled by changing a two-way OFT route’s label.

Liquidity is a separate job

Bridging a token does not transport an existing pool’s reserves. A destination market needs separately funded tokens and a paired asset. The planner divides proposed ETH reserves by proposed token reserves to show an indicative opening price. Concentrated-liquidity ranges, pool fees, trades and deployment details can materially change the actual market.

Supply, market capitalization and pool liquidity are different quantities. No displayed number is a promised price, return or valuation.

What opens a project route

1. Choose the source mint, supported token program and migration model. Review all token authorities and extensions.
2. Provide operator public addresses and fund deployment and message fees in SOL and ETH. Private keys remain with the operator.
3. Deploy the project’s Solana program/escrow and Robinhood OFT using the pinned upstream deployment package.
4. Configure both peers, endpoint IDs, verification networks, executor settings, ownership, rate limits and pause/recovery procedures.
5. Verify the deployed code and configuration. Perform an independent security review and a test-token rehearsal covering forward transfer, return, delayed delivery and retry.
6. For a live token, complete a controlled end-to-end trial with explicit authorization, reconcile backing and supply, and confirm any separately funded pool.
7. Publish the verified contract addresses, custody/upgrade powers, fees, supported wallets, operational contacts and route limitations. Only then enable public transfers.

Network references

Robinhood connection documentation lists mainnet chain ID 4663 and testnet chain ID 46630, with ETH for gas. Public RPC endpoints can be rate limited and should not be treated as a production service guarantee.

LayerZero Robinhood deployments provides messaging network information. Mainnet endpoint ID is 30416; Solana mainnet endpoint ID is 30168. Chain IDs and messaging endpoint IDs are different identifiers.

Film credits

The film uses original animation and music with offline synthetic narration. Read voice model and license attribution.

Data & privacy

Plans live in local browser storage until cleared. Mint inspection sends a public address to the CROSSING API, Solana RPC providers and DexScreener. Infrastructure providers may log requests. No account is created and nothing is submitted to a project team. Exported plans include public addresses and planning inputs; they contain no credentials.

Source references: Solana account API, DexScreener API, EIP-6963 wallet discovery.

Plan your crossing ↗