π How Our Architecture Works
1. Wallet Connection (Phantom) β Read-Only Access Only
When you connect a Phantom wallet, we receive only your public wallet address
Private keys never leave your wallet β technically impossible under Solanaβs cryptography
Phantom uses the standard Web3 connection flow β we cannot execute transactions without your explicit approval
A connected wallet gives BagSensei read-only access to balances and token lists
2. Wallet & Token Scanning
All information BagSensei displays comes from the public Solana blockchain
Anyone can view any wallet on public explorers β we use the same publicly accessible data
We do not store scanned wallets, transactions, or portfolios on our servers
The analytics layer runs in real time using public on-chain endpoints
Your browser handles the heavy logic β sorting, risk checks, token breakdowns, holder maps, etc.
3. Zero-Data Architecture
Your Browser β Public On-Chain Data
β
Our backend never sees your wallet or your scansClient-side processing: risk scores, token parsing, distribution checks, and behavior flags run locally
Our API only provides generic metadata and routing β never wallet-specific data
We do not log addresses, do not create user profiles, and do not track scanning behavior
4. Future Accounts
Planned system: Sign-In with Wallet (message signature, no emails or passwords)
We will store only:
your public wallet address
UI preferences (theme, language, saved view settings)
No personal data
No KYC
No seed phrases
No access to funds
Accounts = convenience layer, not a surveillance layer
π« What We Cannot Do (Technically Impossible)
β Access your private keys β Read your seed phrase β Execute a transaction without confirmation β Move, swap, or send tokens β Track you across scans
β
What We CAN Do
β Read public blockchain data β Build analytics based on on-chain information β Show token, LP, and wallet forensics β Allow optional account preferences (future) β Keep all wallet information local to your browser
π§© Verifiability
Core logic is being prepared for open-source publication on GitHub
Anyone will be able to verify that we do not collect user data
Future smart contract modules will undergo independent audits
Last updated