Investigate, don't guess
Use available on-chain and market evidence to support research. A result is not a guarantee, and an unknown check must remain unknown.
CHIPPMUNK FIELD GUIDE PLATFORM MAP
Explore the system.
Understand every signal.
Your complete guide to what Chippmunk is, how its tools work together, how to use each area, and which capabilities are available, limited or planned.
01 Evidence over assumptions02 Clear access boundaries03 Security-first workflows
01 / START HERE
What Chippmunk stands for
Chippmunk is a Solana-focused data and developer workspace. It brings token metadata, market context, risk research and integration tools into one navigable ecosystem—while making source coverage and uncertainty visible.
Make token data useful
Organise token identity and metadata, review holder and liquidity signals, and understand where data came from before using it elsewhere.
Build responsibly
Use the developer documentation and controlled API access for integrations. Keep credentials private and only grant the permissions a workflow needs.
02 / TOOL DIRECTORY
Every area, explained
Choose a tool based on the job you want to do. Status labels describe the current website implementation and its documented limits—not a promise of completeness.
Token Explorer
LimitedBrowse public token records available to Chippmunk. Use it to inspect listed information; it is not a claim to index every Solana token or provide a complete live-market feed.
Open Token Explorer ↗Metadata Studio
AvailableOrganise token names, symbols, descriptions, logos and social links. Review each field carefully before sharing metadata publicly.
Open Metadata Studio ↗On-chain Metadata Update
AvailableCheck whether metadata is mutable, review the update authority, and submit an eligible update signed in your wallet. Always verify the selected mint and transaction details before signing.
Open On-chain Metadata ↗Market Data
LimitedLearn about market-data fields and sources. This page is not a trading feed; live provider ingestion is not enabled on this page according to its current description.
Open Market Data ↗Risk Intelligence
LimitedScreen available token evidence such as authorities, indexed market data, largest accounts, liquidity and activity. Coverage varies by provider and token; incomplete checks should not be treated as a clean bill of health.
Open Risk Intelligence ↗Risk Bot
Research onlyReview candidate tokens through read-only research and risk checks. It does not execute trades. A candidate result is not a recommendation or a guarantee of safety.
Open Risk Bot ↗Risk Research Engine
Evidence-basedReview staged checks covering token identity, authorities, holders, liquidity and market context. Results marked UNKNOWN mean that evidence was not verified by the available data path.
Open Research Engine ↗Developer & Rug-Pull Evidence
Evidence coverage variesInspect candidate signer addresses, available transaction history and recorded evidence. This cannot reliably identify a real person or independently prove that fraud occurred.
Open Developer Evidence ↗Developer API
Access controlledRead API documentation, examples and key-management guidance. Use only your own key, protect it as a secret, and revoke it if it may have been exposed.
Read Developer API Docs ↗Chippmunk Hub
Access controlledThe developer area supports eligible accounts with profiles, connection requests and project, service, launch or product listings. Listings are subject to access checks, slot limits and moderation. Review the Hub for the current account-specific options.
Discover Hub listings ↗ · Open your Hub workspace ↗Account & Dashboard
Account requiredManage your account and use the tools available to your access level. Never share login codes, passwords, wallet seed phrases or private keys with anyone.
Open Dashboard ↗ · View access options ↗03 / PRACTICAL WORKFLOWS
How to use Chippmunk
These paths help you move through the website in a sensible order. Your exact screens and permissions may depend on login state, access status and the selected tool.
01
Research a token
- Open the Token Explorer or Risk Intelligence.
- Enter or select the token information requested by that tool.
- Review the evidence, source coverage, timestamps and any UNKNOWN results.
- Cross-check important findings independently before acting.
02
Update token metadata
- Open Metadata Studio to review the intended fields.
- Use On-chain Metadata Update to check mutability and authority.
- Connect your wallet only through the expected wallet interface.
- Inspect the mint, fee and transaction in your wallet before signing.
03
Build an integration
- Read the API documentation and endpoint examples.
- Create an API key only for an intended purpose.
- Keep the secret on your server; do not embed it in public JavaScript or a repository.
- Test error handling, permissions, rate limits and key revocation.
04
Use the Developer Hub
- Sign in and confirm your account has the required access.
- Complete your profile and choose a unique handle.
- Send or respond to connection requests thoughtfully.
- Create a listing only when a slot is available; check its moderation status.
- Use the displayed payment flow for additional slots and verify on-chain confirmation.
04 / DEVELOPER HUB
A workspace for projects and people
The Hub is designed to help developers present useful work and find collaborators. Access is not public by default; server-side access checks decide which authenticated accounts may enter.
Developer profiles
Choose a handle and provide a short headline, biography and HTTPS website link. Avoid posting private or sensitive information.
Connections
Use friend or connection requests to build your network. Accept only people you recognise or trust, and be cautious with links and files they send.
Project listings
Present a project, service, launch or product with a clear title, summary and destination link. Listings may be reviewed before publication.
Ad-slot limits
The Hub's base allowance is designed around two listing slots. Additional slots are purchased in bundles of two for €25 payable in SOL, using the live quote and designated recipient shown by the payment flow. Confirm the quote and wallet address before signing.
Payment records
Payment requests and access changes should be traceable. Do not treat a wallet pop-up or submitted transaction alone as proof of payment; wait for the website to confirm the transaction.
Moderation & safety
Listings and submitted materials may be reviewed or restricted. Do not upload malware, stolen material, credentials, personal data or content you do not have rights to distribute.
Important about uploaded code and files
Do not assume an uploaded script is safe just because it has been submitted. Treat files from other users as untrusted. Do not run code directly on the web server or in your normal browser session. Only use a separately isolated, scanned and reviewed release process where available. If a feature does not explicitly offer secure code execution, it should be treated as storage or submission—not a sandbox.
05 / SECURITY & TRUST
Security is a workflow
Chippmunk tools provide research and access controls, but no website can promise perfect security or guarantee that every token, file, payment or user is safe.
Protect account access
Use a unique password, sign out on shared devices, and keep your email account secure. Access to paid tools should be checked on the server, not trusted from a browser flag.
Keep secrets private
Never submit seed phrases, private keys, API secrets or database credentials to profiles, listings, support messages or public code.
Verify wallet transactions
Check the network, recipient, amount, token or SOL value and transaction details in your wallet. Never sign a transaction you do not understand.
Understand risk results
PASS means only that a specific available check passed. UNKNOWN means unverified, not safe. A scan cannot predict future price action or guarantee sellability.
Handle files cautiously
Prefer non-executable formats for public sharing. File type checks alone are not enough; robust upload handling requires size limits, random storage names, storage outside the executable web root, malware scanning and access-controlled downloads.
Report suspicious activity
Do not open suspicious attachments or connect your wallet to unknown links. Keep transaction signatures or relevant evidence, but do not post sensitive personal data publicly.
06 / ROADMAP
Where the ecosystem is heading
This roadmap separates current areas from future ambitions. Planned items are directional and should not be interpreted as a delivery date or as already working functionality.
CURRENT FOUNDATION
Research, metadata & developer access
Maintain the existing token research tools, metadata workflows, account access, documentation and Hub experience. Improve evidence clarity, navigation, accessibility and operational reliability.
Current areasNEXT / HARDENING
Operational visibility & trust controls
Continue strengthening audit trails, moderation workflows, upload restrictions, payment reconciliation, abuse reporting and administrator review. Each capability should be enabled only after its implementation and tests are verified.
RoadmapFUTURE / ECOSYSTEM
Richer project collaboration
Potential improvements include richer project profiles, release and announcement workflows, ecosystem updates and additional developer services. Availability depends on implementation, security review and compatibility testing.
PlannedFUTURE / INTEGRATIONS
Controlled data sharing
Cross-platform publishing and additional integrations should go live only after authentication, endpoint permissions, field mapping, user consent, error handling and end-to-end tests are in place.
PlannedRoadmap integrity
This page is a guide to the current website and its stated direction, not a guarantee that every planned item is delivered. Actual availability is determined by the live page, account permissions and verified release notes.
YOUR NEXT STEP
Turn curiosity into useful work.
Start with the tool that matches your task, check its limitations, and use the developer docs before integrating data into your own product.