Torch Market
PassAudited by ClawScan on May 10, 2026.
Overview
Torch Market is a disclosed Solana trading and margin skill with high-impact wallet actions, but the artifacts frame those actions as user-directed and provide read-only/unsigned modes.
Install only if you understand Solana transaction risk. Prefer unsigned transaction building or wallet-confirmed signing, never provide a vault authority or high-value private key, and independently verify any transaction before approving it.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If a user signs or authorizes the wrong transaction, funds, vault authority, loans, or positions could be changed irreversibly on-chain.
The skill exposes user-invocable actions that can submit blockchain transactions and make irreversible financial or administrative changes. This is aligned with the crypto protocol purpose, but it is high-impact.
"TORCH_SEND_BUY", "Build + submit vault buy via signAndSendTransaction" ... "TORCH_BORROW" ... "TORCH_TRANSFER_VAULT_AUTHORITY", "Transfer vault admin (authority only, irreversible)"
Use quote/preview flows, verify destination accounts and amounts, and sign only transactions you intentionally requested.
Providing a private key gives the skill signing authority for that wallet, so misuse or misconfiguration could authorize on-chain transactions.
The skill can use a Solana private key for direct signing, but the artifact discloses that it is optional and specifically recommends a disposable controller key rather than a valuable authority key.
OPTIONAL: SOLANA_PRIVATE_KEY (disposable controller keypair -- fresh key, ~0.01 SOL for gas, NEVER a vault authority key). ... Without SOLANA_PRIVATE_KEY, operates in read-and-build mode: queries state, returns unsigned transactions.
Prefer read-and-build mode or a wallet approval flow. If direct signing is needed, use only a fresh low-balance controller key as the documentation recommends.
Installing from npm could fetch code that differs from the bundled copy if versions resolve differently.
The skill references an optional npm SDK install using a version range, while also bundling SDK files. This is a normal distribution pattern but introduces dependency provenance/version drift considerations.
package: torchsdk@^10.7.1 ... "Install Torch SDK (npm, optional -- SDK is bundled in lib/torchsdk/ on clawhub)"
Use the bundled reviewed SDK where possible, or pin and verify the npm package version before using it with signing keys.
Transaction identifiers or related activity may be shared with an external reputation service when this action is used.
The artifacts disclose an external reputation-reporting action for transactions. This appears purpose-aligned, but it is an external data flow users should notice.
"TORCH_CONFIRM", "Report tx to SAID for reputation tracking"
Use transaction reporting only if you are comfortable with that external reputation data flow.
A user could over-trust the protocol if they read only the headline verification claims and not the stated limitations.
The project includes strong audit/formal-verification claims, but this artifact also states the limits of verification. Users should not treat the verification claim as a complete security guarantee.
This is not a security audit. It proves the arithmetic is correct, but does not cover access control, account validation, or economic attacks.
Treat the audits and formal verification as useful but limited evidence; still apply normal financial risk controls.