seeker-genesis-token
Verify Seeker Ownership Securely
Client-only token gates can be bypassed or replayed. This skill combines wallet signatures, server-issued nonces, and Token-2022 checks for reliable Seeker verification.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "seeker-genesis-token" from https://skillstore.io/skills/solana-mobile-seeker-genesis-token.md and its manifest at https://skillstore.io/api/skills/solana-mobile-seeker-genesis-token/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "seeker-genesis-token". Explain why checking only the wallet address is unsafe.
Expected outcome:
A public address does not prove control. Verify a fresh SIWS signature, then inspect the SGT held by the verified signed address.
Using "seeker-genesis-token". How should one-claim-per-device state be stored?
Expected outcome:
Store the verified SGT mint address as the device identity. Enforce uniqueness atomically so wallet transfers and concurrent requests cannot create duplicate claims.
Using "seeker-genesis-token". What should happen when the Solana RPC is unavailable?
Expected outcome:
Return a temporary service failure. Do not convert an RPC outage into a false statement that the user lacks an SGT.
Security Audit
Medium RiskThe reported command-execution and reconnaissance patterns are Markdown formatting, JavaScript strings, or normal authentication checks. The intended RPC request is a low network dependency, while the uncapped pagination example creates a medium availability risk.
Confirmed security concerns (1)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (28)
๐ Network access (5)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/solana-mobile-seeker-genesis-token/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/solana-mobile-seeker-genesis-token?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/solana-mobile-seeker-genesis-token?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/solana-mobile-seeker-genesis-token/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/solana-mobile-seeker-genesis-token.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
solana-mobile. (2026). seeker-genesis-token security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/solana-mobile-seeker-genesis-token/audits/1BibTeX citation
@techreport{solana-mobile-solana-mobile-seeker-genesis-token-2026,
author = {solana-mobile},
title = {seeker-genesis-token security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/solana-mobile-seeker-genesis-token/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "seeker-genesis-token security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "solana-mobile"
date-released: "2026-08-27"
url: "https://skillstore.io/skills/solana-mobile-seeker-genesis-token/audits/1"
identifiers:
- type: other
value: "skillstore:solana-mobile-seeker-genesis-token:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Gate Seeker Features
Add server-verified Seeker access to mobile application features without trusting a client-supplied wallet address.
Distribute Device Rewards
Record each SGT mint once to prevent repeated claims after tokens move between wallets.
Review Verification Designs
Evaluate nonce handling, signed-address binding, token identity checks, and zero-balance filtering before deployment.
Try These Prompts
Explain why secure Seeker verification requires both Sign-in-with-Solana and an SGT ownership check. Summarize the server responsibilities.
Design an SGT verification flow for my Solana mobile application. Include nonce issuance, signature verification, domain validation, and signed-address binding.
Adapt the SGT verification guidance for one reward claim per device. Store the mint identity and describe transaction boundaries for concurrent requests.
Review my SGT verification design for replay, address substitution, stale token accounts, RPC failures, unbounded pagination, and concurrent claim races.
Best Practices
- Generate short-lived nonces on the server, verify them once, and bind signatures to the expected domain and mainnet chain.
- Check SGT ownership only for the address recovered from the verified SIWS payload.
- Apply RPC timeouts, pagination limits, rate limits, and atomic uniqueness constraints around device claims.
Avoid
- Do not grant access from a client-computed hasSGT value or an unsigned wallet address.
- Do not accept reusable nonces or omit domain, version, and chain validation.
- Do not treat zero-balance token accounts as current ownership or use wallet addresses as permanent device identities.
Frequently Asked Questions
Why must verification run on a server?
Can I test SGT verification on devnet?
Why use the signed address?
Why filter zero-balance token accounts?
Why store the mint address for claims?
Does the skill require a paid RPC provider?
Developer Details
Author
solana-mobileLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
ba20ff01500daeacf8b388cd781507b37a0f87e8
Maintenance freshness
8/28/2026
Usage
1 downloads ยท 0 views
File structure