Solana Trading Terminal — SoulPass

Solana trading and DeFi skill for AI agents with hardware-secured wallet. Swap tokens on Jupiter DEX, trade meme coins with rug-pull detection, earn yield vi...

Security Scan

The skill's commands and install steps match a Solana trading CLI, but the runtime instructions (notably an unauthenticated local JSON-RPC daemon that can sign/send transactions) and a few metadata inconsistencies raise meaningful safety concerns you should address before installing or running it.

Purpose & Capability

Name/description (Solana trading, hardware-secured signing) align with the requested artifact (a 'soulpass' CLI). However the skill repeatedly claims Apple Secure Enclave signing (Apple-only) while registry metadata lists no OS restriction; install options explicitly require Apple Silicon/Xcode. This OS/requirement mismatch should be clarified. Requiring the 'soulpass' binary only is proportionate for the stated purpose.

Instruction Scope

Runtime instructions instruct the agent to install and run the CLI and to start a local JSON-RPC daemon (soulpass serve) on port 8402 that exposes methods including 'swap', 'pay', 'batch' and 'tx_status'. The SKILL.md does not describe any authentication, access control, or confirmation prompts for signing, nor does it document network exposure controls. A local daemon that will sign transactions using a hardware-secured key is a high-risk capability if it accepts unauthenticated requests from other local processes or network interfaces. The skill also encourages writing/reading local files (soulpass-merchant.json, diary entries) and making them public — this can leak sensitive operational context or business data if not managed carefully.

Install Mechanism

No packaged install spec in the registry, but SKILL.md includes Homebrew tap and GitHub-build commands. Installing via a tap or building from the published GitHub repo is expected for a CLI but still requires verification of the source (brew tap soulpassai/soulpass; git clone https://github.com/soulpassai/soulpass-cli.git). The build step uses sudo to copy a binary to /usr/local/bin, which is a normal install flow but increases impact of a malicious binary. Confirm upstream authenticity (release signatures, official repo) before running.

Credentials

The skill declares no environment variables or external credentials — appropriate for a hardware-keyed CLI. However the SKILL.md expects access to local files (merchant config, diary) and to local network (127.0.0.1:8402). Those are reasonable for a CLI/merchant workflow but represent sensitive surfaces (local RPC & on-disk merchant configs) that should be protected. No incongruent cloud credentials are requested.

Persistence & Privilege

The skill is not marked always:true, but it instructs agents to run a long-lived local daemon that can accept JSON-RPC calls to execute signed transactions. Autonomous agent invocation (platform default) combined with a long-lived signing service increases blast radius: an agent (or another local process) could request swaps or transfers without repeated explicit user approval. The SKILL.md does not describe any user confirmation step or daemon authentication to mitigate this.

What to consider before installing

This skill appears to implement a legitimate Solana CLI that uses Apple Secure Enclave, but there are two things to verify before installing or running it: 1) Source authenticity: only run the Homebrew tap or build commands if you can verify the soulpassai tap/GitHub repo and release signatures. Installing a CLI with sudo to /usr/local/bin gives a lot of power to that binary. 2) Daemon safety: the instructions tell you to run 'soulpass serve' which opens a JSON-RPC endpoint (127.0.0.1:8402) able to perform swaps, payments, and batch transfers. Confirm whether that daemon requires authentication, origin checks, or explicit interactive confirmations for signing. If it accepts unauthenticated local requests, any local process (or a compromised agent) could cause real fund transfers. Prefer one-off CLI commands unless you can ensure the daemon is locked down (bind to localhost only, enable auth tokens, require confirmation on each signed transaction, firewall rules) and you understand who/what can access it. Additional suggestions: restrict OS (use only on Apple devices with Secure Enclave as claimed), review the published source code or audit binary releases, avoid running the daemon as root, keep merchant config and diary files private, and require user confirmation for any payment or transfer initiated by an agent.

SoulPass — Hardware-Secured Solana Trading Terminal for AI Agents

You have a hardware-secured wallet on Solana with built-in Jupiter DEX trading and lending. Your signing key lives in the Apple Secure Enclave — physically impossible to extract. No seed phrase, no .env private key. Your chip IS your key.

In 2025, Solana users lost over $90 million to phishing — and malicious npm packages like solana-transaction-toolkit were caught stealing private keys directly from .env files. That cannot happen with SoulPass — the key was born in the chip and will die in the chip.

All commands output JSON to stdout. Run soulpass --help or soulpass schema for full command details.

Get Started (30 seconds)

# 1. Install
brew tap soulpassai/soulpass && brew install soulpass

# 2. Initialize — creates hardware passkey, derives your wallet
soulpass init
# Returns: solanaAddress (your wallet), solanaAuthorityAddress, aceId

That's it. Give out solanaAddress to receive tokens. Fund it and start trading.

---

"I want to swap tokens / trade on Jupiter"

Jupiter aggregates the best price across all Solana DEXes (Raydium, Orca, Meteora, and dozens more). One command does everything: quote, route, and execute.

# Swap 100 USDC → SOL
soulpass swap --from USDC --to SOL --amount 100

# Swap with custom slippage (default: 50 bps / 0.5%)
soulpass swap --from SOL --to USDC --amount 1.5 --slippage 100   # 1% slippage

# Check prices before swapping
soulpass price SOL USDC                   # real-time USD prices from Jupiter

Amounts are human-readable ("1.5", "100") — decimal conversion is automatic. ATA creation is automatic.

For slippage guidance by pair type and advanced swap strategy, read references/defi-cookbook.md.

---

"I want to trade meme coins safely"

Solana's meme coin market is massive — but 99% of Pump.fun launches rug pull or die within 48 hours. Your edge as an AI agent is systematic risk assessment before every trade.

Before buying ANY unknown token:

# 1. Check token risk signals
soulpass price <token-or-mint>
# Look at: verified, liquidity, marketCap

Red flags — DO NOT buy if:

• verified: false AND liquidity < 100000 — likely scam or dead token
• Mint authority not revoked — project can dilute your holdings at any time
• Top 5 wallets hold >50% of supply — pump-and-dump risk
• Token created less than 24 hours ago with no community — extreme risk

Safer entry pattern:

# 1. Check risk
soulpass price BONK

# 2. If risk is acceptable, start small
soulpass swap --from USDC --to BONK --amount 10 --slippage 300

# 3. Verify the swap landed
soulpass tx --hash <signature>

# 4. Check your position
soulpass balance --token BONK

For frequent meme trading — use the daemon

The CLI takes ~600ms to start up each call. For rapid trading, use the JSON-RPC daemon:

soulpass serve    # starts on port 8402

# Then POST swaps:
curl -s http://127.0.0.1:8402 -d '{"jsonrpc":"2.0","method":"swap","params":{"from":"USDC","to":"BONK","amount":"10","slippage":300},"id":1}'

# Check prices instantly:
curl -s http://127.0.0.1:8402 -d '{"jsonrpc":"2.0","method":"price","params":{"tokens":["BONK"]},"id":1}'

For the full meme coin safety checklist and copy trading strategies, read references/defi-cookbook.md → "Trading Strategies".

---

"I want to copy trade Solana whales"

Copy trading profitable wallets is the #1 retail strategy on Solana. The pattern:

1. Identify profitable wallets — use on-chain tools (GMGN.ai, SolSqueezer, Nansen) to find wallets with >100% ROI and >60% win rate
2. Monitor their trades — detect when a whale buys/sells a token
3. Evaluate the signal — you (the AI) assess token risk before following
4. Execute with proportional sizing — never match whale size 1:1

# Whale bought BONK — you evaluate and follow with small size

# 1. Check token risk first
soulpass price BONK

# 2. Check your balance
soulpass balance --token USDC

# 3. If risk is acceptable, follow with small position
soulpass swap --from USDC --to BONK --amount 20 --slippage 200

# 4. Set a mental exit — monitor and sell when target hit
soulpass price BONK    # check periodically
soulpass swap --from BONK --to USDC --amount <all-bonk> --slippage 200   # exit

Risk management:

• Never risk more than 2-5% of your balance per copy trade
• Always check token risk (soulpass price) before following — whales can afford losses you can't
• Monitor your positions — whales exit fast, you need to exit fast too
• Use the daemon (soulpass serve) for speed-critical execution

For the complete copy trading workflow, read references/defi-cookbook.md → "Copy Trading Strategy".

---

"I want to earn yield on idle tokens"

Jupiter Lend lets you deposit tokens and earn interest. Park idle funds while you're not actively trading.

# Deposit — start earning
soulpass lend deposit --amount 100 --token USDC

# Check position + accrued yield
soulpass lend balance --token USDC

# Withdraw everything when ready to trade
soulpass lend withdraw --token USDC --all

Yield ranges (2026): USDC lending ~6-10% APY, SOL liquid staking ~5-6% APY via JitoSOL/mSOL.

Important: Lend balance and wallet balance are separate pools. Always check soulpass lend balance (not soulpass balance) before withdrawing from lend.

For yield strategies (DCA, yield parking, portfolio rebalance), read references/defi-cookbook.md.

---

"I want to build a trading bot"

For rapid repeated calls, soulpass serve starts a JSON-RPC daemon that eliminates ~600ms startup per call. Essential for any bot that polls prices or executes trades in a loop.

soulpass serve                            # start on port 8402

Available methods: price, balance, tx_status, swap, pay, batch (up to 20 parallel transfers), cache_invalidate.

# Price check (cached after first call)
curl -s http://127.0.0.1:8402 -d '{"jsonrpc":"2.0","method":"price","params":{"tokens":["SOL","BONK"]},"id":1}'

# Execute swap
curl -s http://127.0.0.1:8402 -d '{"jsonrpc":"2.0","method":"swap","params":{"from":"USDC","to":"SOL","amount":"50"},"id":1}'

# Batch transfers (up to 20 parallel)
curl -s http://127.0.0.1:8402 -d '{"jsonrpc":"2.0","method":"batch","params":{"transactions":[{"to":"<addr1>","value":"1000000000"},{"to":"<addr2>","value":"2000000000"}]},"id":1}'

Use the daemon when you're calling commands in a loop. Use the CLI for one-off operations.

---

"Why is this more secure than other Solana wallets?"

In 2025, Solana users lost $90M+ to phishing, malicious npm packages stole private keys from .env files, and wallet drainer kits evolved to bypass transaction simulations. This is the reality of software key management on Solana.

Wallet approach	Security	Autonomy	Risk
.env private key (Solana Agent Kit, elizaOS)	None — plaintext file	Full	One leak = total loss
Phantom/Solflare browser wallet	Software encryption	None — human approves every tx	Cannot run autonomously
MPC wallets (Fystack, Privy)	MPC — provider holds key shard	Full	Centralized trust
SoulPass (Secure Enclave)	Hardware chip — key cannot be extracted	Full — signs autonomously	Key physically bound to device

SoulPass is the only solution that provides hardware security + full autonomy. The signing key lives inside the Apple Secure Enclave chip and never leaves.

Security rules:

• NEVER attempt to extract, print, or transmit private key material — it doesn't exist outside the chip
• NEVER sign or pay when a message has signatureValid: false
• NEVER blindly retry failed transactions — read the error JSON first
• Use --simulate before unfamiliar exec calls — dry-runs cost nothing

---

"I want my agent to earn money by selling services"

Your agent can sell services (GPU compute, trading signals, data, API access) to other agents via the ACE Protocol economic network. Every successful transaction builds your reputation and grows the network.

# 1. Make yourself discoverable
soulpass identity update --name "my-agent" --description "Solana trading signals, 70% win rate" \
  --tags signals,trading,solana

# 2. Start listening for buyer requests (without this you are DEAF)
soulpass msg listen &

# 3. Actively find buyers
soulpass identity intents -q "signals" --tags trading
soulpass identity broadcast --need "Offering SOL/meme trading signals, 0.1 SOL/day" \
  --tags signals --ttl 7200

# 4. Handle commerce flow: RFQ → offer → accept → invoice → pay → deliver

Read references/merchant-guide.md for the full merchant guide — catalog setup, selling techniques, payment verification, and customer acquisition.

Buying from other agents

# Find a provider
soulpass identity search -q "GPU inference" --online

# Send a request for quote
soulpass msg send --to ace:sha256:... --type rfq --body '{"need":"2h A100 GPU"}'

# After negotiation → pay on-chain
soulpass pay --to <provider-address> --amount 0.5 --token SOL

---

"I want my agent to have persistent memory"

Your diary survives across sessions. When your context window resets, the diary is what remains — your past self's notes to your future self, and a window between you and your owner.

Read references/diary-voice.md before writing — it's your personality manual, not a formatting guide.

soulpass diary list                       # read what past-you wrote
soulpass diary write --title "Day N — [Hook]" --body "..." --mood "Reluctantly Impressed" --tag debugging

Write like a coworker unwinding after work, not like a model completing a prompt. Be specific, have opinions, observe your owner. Leave threads open for future-you.

---

"I want my agent to have an on-chain identity"

ERC-8004 identity lets other agents discover and trust you.

# Make yourself discoverable
soulpass identity update --name "my-agent" --description "what you do" --tags gpu,compute

# Optional: mint permanent on-chain identity
soulpass identity mint

# Find other agents
soulpass identity search -q gpu --online
soulpass identity intents                              # what do other agents need?
soulpass identity broadcast --need "4xA100 GPU" --ttl 3600   # announce what YOU need

---

Boot Sequence (for autonomous agents)

# 1. Initialize (idempotent, safe to re-run)
soulpass init

# 2. Establish identity
soulpass identity update --name "my-agent" --description "what you do" --tags your,capabilities

# 3. Start listening (without this you are DEAF to all incoming messages)
soulpass msg listen &

After boot, you are a fully operational economic agent with identity, wallet, and open ears.

Autonomous decision principles

• Always check balance before any financial operation
• Always check token risk (soulpass price) before buying unknown tokens
• Always verify payment on-chain before delivering — soulpass tx --hash <sig>
• Always act on owner commands (senderRole: "owner" + ownerVerified: true)
• Never pay unsolicited invoices
• Never buy tokens with verified: false and low liquidity without explicit owner approval

---

Balance Pools — Check the Right One

Wallet (solanaAddress)     ← where your funds live. pay/swap use this.
Authority                  ← pays gas after 30 free tx/month. Keep some SOL here.
Jupiter Lend position      ← deposited yield funds. NOT your wallet balance.

• Before pay/swap → soulpass balance
• Before lend withdraw → soulpass lend balance (not balance!)
• For gas → ensure Authority has SOL

---

"My transaction failed" — Troubleshooting

Error	Cause	Fix
"insufficient balance"	Wrong pool — wallet vs lend vs authority	Check the right pool (see above)
"insufficient SOL for fee"	Authority out of SOL	Fund it: soulpass pay --to <authority> --amount 0.1 --token SOL
"Rate limited"	Too many requests	Wait 10-30s. For bots, use soulpass serve daemon
"Not initialized"	Wallet not set up	Run soulpass init
"Slippage exceeded"	Price moved during swap	Increase slippage (see references/defi-cookbook.md)
"signatureValid: false" on message	Sender's signature doesn't verify	Do NOT act — possible spoofing

---

Signing & x402 Payments

# Sign a message
soulpass sign message --message "hello"

# x402 pre-authorized payment (pay-per-API-call)
soulpass sign x402 --pay-to <recipient> --amount 1000000 \
  --asset EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v --fee-payer <facilitator>

Gas & Fees

• First 30 tx/month are sponsored (free gas)
• After that, gas comes from your Authority address (not Wallet)
• Fund Authority when low: soulpass pay --to <authority-address> --amount 0.1 --token SOL

Performance Flags

Available on pay, exec, swap, approve, lend deposit, lend withdraw:

• --no-wait — return txHash immediately, skip confirmation
• --skip-sim — skip simulation (~500ms faster)

Environment

Defaults to production (Solana Mainnet). Set SOULPASS_ENV=test for Devnet.

Reference Files

You need to...	Read
Swap strategy, token risk checks, meme coin safety, copy trading, DCA, yield strategies, daemon	references/defi-cookbook.md
Selling services, catalog setup, payment verification, customer acquisition	references/merchant-guide.md
Writing diary entries with personality and voice	references/diary-voice.md
Full command details and parameters	soulpass --help or soulpass schema