Practical overview
When it fits
Use Kana when you want a locally run command-line bot to monitor eligible Solana token routes and manage configured buys. It must remain open to keep the sniper bot running.
Who it is for
- Solana users who want to configure automated token buys from a CLI.
- Users who want to monitor selected positions and set take-profit or stop-loss values.
Documented uses
- Monitor a token address for an available swap route and execute a configured buy.
- Set a buy amount, slippage, take-profit and stop-loss for a token.
- Watch a selected trading position and edit its wallet or trade settings.
Requirements & limits
The README specifies Python 3.11, installing dependencies from requirements.txt, and starting with python main.py. It says private keys are stored in wallets.json.
- The README labels the sniper bot experimental and subject to change.
- The README says monitored tokens must be listed through Jupiter’s API, have on-chain metadata, at least $250 liquidity and buy/sell price impact below 30%.
- The bot stops when Kana is closed.
- Private keys are stored in a local wallets.json file.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up Kana and start its CLI
Install the project’s requirements and launch its Python command-line application.
Before you start
- Python 3.11
- The Kana repository
Steps
Download the repository.
Install the required libraries with the command below.
pip install -r requirements.txtStart the application with the command below.
python main.py
Expected outcome
The Kana CLI starts; the README describes token-sniping features in the application.
Guide limitations
- The README describes the sniper bot as experimental and subject to change.
- The sniper stops when Kana is closed.
- Private keys are stored in
wallets.json. - The documented token workflow is limited to tokens listed through Jupiter’s criteria: at least $250 liquidity and buy/sell price impact below 30%.
Configure a token for sniping
Add a token and configure its purchase and position settings in Kana.
Before you start
- Kana is running in the CLI.
- The token address and intended purchase and risk settings.
Steps
Provide the token or project name and token address.
Set the purchase amount, take-profit amount, stop-loss amount, and slippage percentage.
If the token has a launch date, enter its month, day, hour, and minute.
Allow time for eligible tokens to be added; the README says this can take a few minutes.
Expected outcome
The token is configured for sniping, and Kana checks for a route and executes it when one is available.
Guide limitations
- Only tokens meeting Jupiter’s stated listing criteria are supported: at least $250 liquidity and buy/sell price impact below 30%.
- The bot is experimental, and it stops when Kana is closed.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- KanaDevv/Solana-sniper-bot · Official homepage title · retained in its source language