Catch mistakes early.
Invalid addresses, repeated recipients and unsupported decimals are caught before a transaction is built.
Rust-powered. Community-driven.
Compare swap routes. Distribute community tokens. Explore staking positions. Build your next launch.
Rust-powered workers for Solana communities, funded together through $SWARM.
SCpumpxxxxxxxxAt launch

$SWARMRust-powered workers for Solana communities.
The workspace
Choose a worker. Add your inputs. Review the result before taking action.
Choose two tokens and an amount to compare live routes.
SWARM checks the same pair across an aggregated route, Orca and Raydium. Review expected output and price impact, then swap here through Jupiter.
Quotes use 0.5% slippage. The swap panel fetches a fresh quote before you sign.
Compare the same amount and pair across available routes. No wallet needed for this check.
Give SWARM your token and recipients. Rust validates the list and exact amounts. Mainnet checks compare standard and compressed delivery before you simulate, sign and track each batch.
Invalid addresses, repeated recipients and unsupported decimals are caught before a transaction is built.
Check which recipients need token accounts, calculate deposits, and check Light pool eligibility.
Review each batch in Phantom. Follow its transaction receipt before moving to the next batch.
Works with supported SPL and Token-2022 assets, including migrated Pump.fun tokens. Compatibility is checked on Mainnet.
Start distribution βSee how liquid staking options differ, compare live SOL-to-token quotes, and review how to exit. SWARM brings acquisition and distribution into one workflow.
These are market quotes to acquire staking tokens, not APY estimates or direct staking deposits. Different token counts do not mean higher returns.
SWARM can check whether the chosen token has a Light pool and compare recipient-account costs. Compression changes how balances are stored. It does not increase staking yield, and DeFi use may require decompression.
Create a community website, test Mainnet RPCs, prepare a token launch kit, or generate a Rust program starter. Your inputs become a preview, a file or a verified network response.
Check signer addresses and an approval threshold before creating a multisig. Export the configuration for your team and use the official Squads setup flow.
You approve transactions in your wallet. SWARM never asks for a seed phrase. How funding and fees work β
The engine behind the work
SWARMβs validation engine runs Rust in your browser through WebAssembly. It checks addresses, detects repeated recipients, and converts token amounts into exact units before a distribution is prepared.
Rust powers the validation core. Jupiter routes swaps. Light Protocol provides on-chain compression. SWARM connects these steps in one workspace.
Inspect our Rust distribution source βHow SWARM uses Rust βFunded together
SWARM tools carry no added service fee. The planned $SWARM model supports development and operation of the workers. Network and third-party protocol costs remain visible in each flow.
Planned allocation from the initial purchase, intended to be locked for one month after launch. Lock proof will be published when executed.
Planned token allocation for holders. Eligibility, snapshot and distribution dates will be published before the airdrop.
Planned token allocation for worker development, RPC and hosting costs, integrations and community tooling. It is an ecosystem budget.
Proposed for $SWARM trading, subject to launch-venue support. This is not a fee charged to use these workers and is not active here.
Launch allocation plan. Contract: pending. No $SWARM payment or holding requirement is currently enabled. Funding and trading-fee details will be published before activation.