Requirements
tools, endpoints, wallets.
What to install, which services SLUICE reads from, what you bring to each round, and what it costs to run.
01Tools on your computer
| Tool | Version | Why |
|---|---|---|
| Flutter SDK (includes Dart) | 3.41 or newer, stable | pubspec.yaml needs Dart ^3.11.1. These docs were checked with Flutter 3.41.4. Install |
| Xcode | 26 or newer | macOS and iOS builds. Needs a Mac. Checked with Xcode 26.4.1 and Xcode 27.1 (see Troubleshooting for a universal macOS release build on Xcode 27). |
| Google Chrome | current | Runs the web build locally. |
| Android Studio | current stable | Only for Android builds. compileSdk and targetSdk are 36. |
| A terminal | — | macOS Terminal or a Linux shell. On Windows: PowerShell for flutter commands, WSL or Git Bash for the tool/*.sh scripts. |
flutter --version
flutter doctorNo Node.js, database or server is needed. SLUICE has no backend.
02Services SLUICE reads from
| Service | Used for | |
|---|---|---|
| A Solana JSON-RPC endpoint | Reading mints, balances, signatures. Default: https://api.mainnet-beta.solana.com, which rate-limits hard and often refuses getProgramAccounts. | Your own, before a real round |
| Helius API key, free tier | Paginated holder enumeration (DAS). Without it SLUICE falls back to getProgramAccounts, the first thing to fail on a large holder set. | Recommended |
| Dexscreener (keyless) | Pool venue labels for exclusions | Built in |
| Solscan (or another explorer) | Signature links | Links only |
SLUICE does not need a price source.
03What you bring to each round
| Thing | Why | |
|---|---|---|
| The funding wallet | Holds the pool and signs every batch. SLUICE never holds its key. | Required |
| Signing tooling you control | SLUICE hands over unsigned instructions as JSON. You need a way to put them into transactions and sign with the funding wallet (for example your own script or a multisig tool). | Required |
No on-chain program is needed: every round is paid with direct SPL token transfers from the funding wallet.
04Platforms
| Platform | Minimum | Notes |
|---|---|---|
| macOS | 12.0 | The main operator target. See the network note in Deployment. |
| Web | Current browsers | flutter build web --release works; --wasm does not. |
| iOS | 15.0 | Builds; the console is designed for wide screens. |
| Android | Flutter's default | Same. |
| Linux, Windows desktop | — | Not configured as app targets. You can still develop on Windows and build the web and Android targets there. |
05Costs not included in the price
The item price covers the source code and this documentation. SLUICE itself costs nothing to run, because there is no server. The services below are third-party: each one is billed by its own provider, on your own account, and you pay for your own usage above any free tier. Check each provider's current pricing.
| Service | When you need it | Who pays |
|---|---|---|
| Solana JSON-RPC provider (Helius, QuickNode, Alchemy or your own node) | Before a real round | You, above the provider's free tier |
| Helius API key | Recommended for large holder sets | You, above the Helius free tier |
| Static web hosting and a domain | Only if you host the web build | You |
| Apple Developer Program, Google Play Console | Only to publish the iOS or Android app | You |
| Solana network fees and token-account rent | Every round | Your funding wallet; the dry run estimates them first, including the priority fee each batch bids |
SLUICE ships no API key and no paid plan.
06Setting up the services, step by step
Two accounts are worth opening before your first real round. Both have a free tier; you pay the provider directly if you go above it. The click paths below use each provider's labels as of October 2026; if a provider renames a menu, its linked guide is the reference.
Helius: create an API key
- Sign upOpen dashboard.helius.dev and sign up with your own email. Plans and limits: Helius docs → Billing → Plans.
- Open API KeysHelius dashboard → API Keys in the left sidebar. A key is created with the account; for a separate one, click Create New API Key and name it, for example "sluice". Copy the key (the value after
api-key=). Helius's own steps: Helius docs → Authentication → Create your API key. - Copy the mainnet RPC URL (optional)Helius dashboard → RPCs in the left sidebar → the Mainnet URL,
https://mainnet.helius-rpc.com/?api-key=…(format: Helius docs → Solana RPC URLs and endpoints). - PasteIn SLUICE: Settings → Endpoints → the key into Helius API key, the RPC URL into JSON-RPC endpoints, one per line → Save endpoints and explorer. The key is used for holder enumeration with Helius DAS
getTokenAccounts(Helius docs → DAS → getTokenAccounts).
Helius: restrict the key to your domain (web build only)
- Open the access rulesHelius dashboard → RPCs → Access Control Rules.
- Add your domainUnder Allowed Domains, add the domain of your hosted web build (for example
sluice.example.com), one per line, so a key typed into that build works only there. Helius's guide: Helius docs → Protect your keys → Access control rules.
Any other RPC provider
QuickNode, Alchemy and others work the same way: create a Solana mainnet endpoint, copy its HTTPS URL, and paste it into JSON-RPC endpoints, one per line. Then press Test the endpoint; the state and the current slot appear.
- QuickNode: dashboard.quicknode.com → Endpoints → New Endpoint → choose Solana and Mainnet → open the endpoint → Overview tab → HTTPS tab under API access → copy the URL. To restrict it to your domain: endpoint → Settings tab → Whitelists → Referrer Whitelist. QuickNode's guide: QuickNode guide → How to use the dashboard → Endpoints.
- Alchemy: dashboard.alchemy.com → Apps → create or open an app with Solana Mainnet enabled → copy its HTTPS endpoint URL. To restrict it: the app's Security tab → Allowlist Domains (Alchemy docs → Add allowlists to your apps). Solana API reference: Alchemy docs → Solana API quickstart.