United Starship

United Starship is a powerful EVM wallet that does exactly what you tell it. Published by Callister Inc. It is a full BIP-39 HD wallet - multiple accounts, import by Secret Recovery Phrase or by private key - with complete control over every network, RPC endpoint and token it touches. Point it at a local node, a fork, or a live chain: it connects to the JSON-RPC endpoint you configure and passes your calls through verbatim, cheat and dev methods included. It never substitutes hosted data, and it applies no address, network, or token blocklist. The responsibility that comes with that control is stated on every screen rather than buried. A slim caution bar reads "Verify the RPC URL and chain ID before you connect or sign. No network or phishing checks stand in the way." It sits on every popup, every approval, and every onboarding screen. Each approval names the chain ID and the RPC URL the request will be sent to. This wallet does not claim to vet any of it for you, and it will not pretend to have checks it does not have. If you have ever watched a wallet refuse a custom network, swallow a node cheat call, or quietly answer a balance query from someone else's server, this is the wallet that does not do that. CREATE YOUR WALLET Generate a 12- or 24-word Secret Recovery Phrase, back it up, and confirm it - exactly like the wallets you already know. There is nothing exotic about the key handling here, and that is deliberate: your phrase restores this wallet on any BIP-39 device, and any BIP-39 phrase restores into this one. You can also import an existing HD wallet by Secret Recovery Phrase, or bring in a standalone account by private key. Both live in the same encrypted vault. At any point you can reveal the Secret Recovery Phrase again, or show an individual account's private key, behind your passphrase. Your keys are not held hostage by the software that stores them. MULTIPLE ACCOUNTS Derive as many HD accounts as you want from the one phrase, import standalone keys alongside them, and switch the active account whenever you like. Accounts can be renamed, and imported ones are labelled as imported so you always know which are derived from your phrase and which are not. Each account shows its own balance on the network you have selected, read from the endpoint you configured. ANY NETWORK A catalog of common EVM chains is one click away, each with a locally bundled logo, because the wallet fetches no remote assets. Beyond the catalog you can add any chain ID and any HTTP or HTTPS RPC host. Duplicate chain IDs are allowed. Mainnet is not reserved. There is no allowlist and no blocklist. If your node answers JSON-RPC, this wallet will talk to it. EVERY NETWORK IS YOURS TO CONFIGURE Every network is editable - including the ones the wallet shipped with. Rename it, change the chain ID or the symbol, set an explorer URL, and reset it back to the shipped defaults whenever you want. Each network holds a list of RPC endpoints and you choose which one is live. Endpoints are added and removed rather than edited in place, so an entry you are relying on cannot silently become a different endpoint under you. Switching the live endpoint re-reads your balances immediately, and there is an explicit refresh whenever you want to pull again from whichever endpoint is currently selected. This is the difference between a wallet that offers you networks and a wallet that hands you the network layer. YOUR KEYS, YOUR ENDPOINT Native and ERC-20 balances are read with eth_getBalance and balanceOf from the endpoint you configured - local, forked, or live. There is no hosted balance API and no price API, not even on chain 1. What the wallet shows you is what your node said. The balance card names the endpoint the number came from, and the chain ID it came from, right beneath the figure. When you are running three forks and a local node, that line is the difference between confidence and guesswork. GRAB ANY CONTRACT ADDRESS A bundled catalog of widely used ERC-20 tokens, each with a locally bundled logo and a copyable contract address. The address is copyable from the common list as well as from your watched tokens, so you can take a token's address without adding it first. Any ERC-20 can be added by contract address, with symbol and decimals read from the contract itself. SEND ON ANY CHAIN YOU CAN REACH Send the native coin, any watched ERC-20, and any ERC-721 or ERC-1155 item you hold, straight from the wallet. The recipient is checked for shape and EIP-55 checksum. That is all it is checked for - there is no address book, no name resolution, and no scam list, and the wallet says so on the send screen rather than letting you assume otherwise. Max is derived from the same gas and fee numbers the transaction is actually built with, so it does not leave you a few wei short. Amounts are scaled by the asset's own decimals and never pass through a floating-point number; an amount with more precision than the asset can represent is refused outright rather than quietly rounded. Before signing you get an exact review: the amount, the recipient in full, the network and chain ID, the RPC URL, the gas, the fee ceiling, the total debit, and the call itself. Then pending, then confirmed with the transaction hash, and a balance re-read from chain. Everything is signed by your own keyring and broadcast through your configured RPC. There is no hosted relayer standing between you and the node. RECEIVE, WITH THE CHAIN IT IS REALLY ON A Receive action shows the active account as a scannable QR code, with the address in full and a copy affordance. The code carries an EIP-681 payment URI - address plus chain - so a mobile wallet scanning it picks up the chain as well as the address. One tap switches to a bare address for scanners that understand nothing else, and the screen always states which of the two the visible code is carrying. The code is generated inside the extension. No QR service is contac…