Security
Review the security boundaries of Solana data access, transaction simulation and AI tool connections. These principles describe what to check in a service and wallet workflow before authorizing an action.
Your keys stay with you
The rule everything else is built on
Layers to review
From the outside in, ending at your own signature
Rate limits
A configured service should document request limits, payload sizes and retry behavior. Its hosting platform and RPC provider may impose separate limits. Handle rate-limit errors with bounded retries.
Validated inputs
Check the input schema, base58 address and signature formats, network and commitment before a call. A service should bound result sizes and reject invalid values rather than interpreting incomplete input.
Simulation and preview
Solana RPC can simulate serialized transaction bytes and report errors, logs and compute usage. The result depends on the selected state and signature checks. A successful simulation cannot guarantee later execution.
Plain warnings
Inspect token mints, program IDs, recipients, account permissions and fees. A warning is only as useful as its data source and coverage. An absent warning is insufficient evidence that an action is safe.
Data boundaries
Public chain records, AI prompts and locally held keys have different exposure. An AI client or RPC provider may retain off-chain request data. Review its policy before sending identifiers or transaction bytes.
Your own signature
A signature authorizes the actual message bytes. Check the fee payer, required signers, instructions and recent blockhash in the wallet application. Delegated authority depends on the selected program's permissions.
Public balance, account, token and transaction records can be read using public identifiers. The documentation explains these data types and how to interpret simulation results.
Transaction safeguards
Four complementary checks
Policy rules
Review which program enforces spending caps, permitted actions, expiry and revocation.
Risk signals
Identify token mints, authorities and program behavior using verifiable records and documented coverage.
Address context
Confirm the full public address, network and intended recipient. Treat labels as source-specific evidence.
Fresh data
Record the cluster, commitment and observation time. Recheck data that can change before submission.
These checks are design guidance. Any external service must document its implemented checks, limits and data handling.
If something looks wrong
Three steps, in this order
Revoke approvals
Inspect token delegates, spending authorities and program permissions in trusted wallet software. Revoke unwanted authorities through the appropriate Solana instruction after reviewing what it changes.
Check what happened
Look up the full signature in a trusted Solana explorer. Compare signers, program IDs, instructions and balance changes with the message you intended to authorize.
Report it
Prepare a report with the time, affected public addresses and transaction signatures. Check the contact page for available reporting details and keep wallet secrets out of the report.
What these protections cover
The limits worth knowing
Reads need no wallet
Public account and transaction data can be inspected with public identifiers. A provider still sees the request and may apply its own access policy.
An AI can misread a request
The model in your client can get things wrong. Read each preview and every warning before you sign.
Check finality
Finalized Solana transactions cannot be reversed by this website. Review the message before authorization and verify the execution result at the required commitment.
Reporting a vulnerability
Document the affected page, reproduction steps and public evidence. The contact page lists available reporting channels when configured.