Security research
Cyberscope Solana audit evidence: unresolved initial findings
The UnclaimedSOL example is an initial Solana/Rust report with a named revision and file scope. It records one medium and six minor findings as unresolved in that version. A later project may have changed the code; the initial artifact alone cannot establish a fix. Request the final report and compare its scope with the proposed deployment.
An initial report is not a final remediation record
Use this question to examine the evidence below before carrying an earlier observation into a new engagement.
Separate the historical observation from a current decision
The earlier analysis recorded a $4,700 test-project quote and described marketing distribution alongside the report. These are historical editorial observations, not a current quotation or evidence that findings were fixed. Price and promotional reach do not identify the reviewed code revision.
This editorial revision replaces unsupported general praise and does not reproduce the old aggregate rating. DSA has not assigned a new technical score.
Unclaimed SOL: the evidence boundary
Read the source report. Initial audit: .
- Reviewed scope
- lib.rs in the unclaimed-sol-close-token-program repository; Solana token burning and account closure.
- Revision evidence
- ddfc570b1a21e2a2ae0a59eca11d0aca0f455241
- Follow-up
- This version lists one medium and six minor/informative findings as unresolved. Only an initial audit date is listed.
- Limit of the observation
- This is a dated report version, not a claim about whether the project later fixed or deployed the code.
Build the release decision around traceable evidence
- Pin the proposed source revision and identify the contracts and dependencies included in the review.
- Choose a material finding in the relevant report. Trace its affected code and record the final disposition.
- Compare the reviewed revision with the intended deployment. Document subsequent changes and unresolved assumptions.
- Confirm the retest scope, assigned reviewers and current commercial terms directly.
Use the Cyberscope profile for field-level sources and the solana guide to plan the related technical checks. A tool result supplements the evidence packet; it does not replace a scoped audit.
Prepare an audit request with Cyberscope or compare other providers.
Sources
Checked . Local examples include their inputs and limits.
About this revision
Rebuilt the legacy company analysis around source scope, dated evidence and limits of historical claims. The URL is preserved. This is a DeFiSec editorial revision, not a new assessment by the provider or an expert committee.
Suggest a correction with evidence