Non-custodial wallet use
Slingzero does not ask for or store your seed phrase or private key. Connect only through your wallet’s own interface, read every prompt, confirm the selected network, and reject any transaction you do not understand.
Verify addresses
Names and ticker symbols are not unique. Confirm the complete token contract, mint, package, coin type, pool, and recipient address on the relevant block explorer before acting. Never rely on a logo alone.
Authorities and ownership
Mint, freeze, update, TreasuryCap, UpgradeCap, ownership, and tax controls differ by network and template. Transferring or revoking a capability may permanently remove your ability to mint, edit, freeze, change taxes, or upgrade.
Liquidity is a separate risk
Creating a token does not guarantee a market, price, liquidity, or LP lock. Pool creation and liquidity management are separate transactions. Verify pool pairs, fee tiers, price ranges, and token approvals before signing.
Metadata and public pages
IPFS content is designed to be persistent, while third-party gateways and explorers can take time to update. User-published Token Pages are not audited or endorsed by Slingzero. Treat project links and claims as unverified user content.
Report a security issue
Email [email protected] with “Security report” in the subject. Include the affected URL, network, transaction or address, impact, and reproduction steps. Do not include private keys, seed phrases, or sensitive credentials.
Responsible disclosure scope
Useful reports include reproducible problems in Slingzero’s website, transaction construction, access controls, or data handling. Third-party wallets, RPC providers, explorers, protocols, and user-published Token Pages should normally be reported to their operators. Avoid testing that moves another person’s assets, degrades the service, or exposes private data.
What to expect after a report
We review reports for reproducibility and impact, may request additional detail, and prioritize fixes according to risk. Slingzero does not currently promise a public bug bounty or payment unless a separate program explicitly says otherwise. Please allow time to investigate before publishing an unresolved vulnerability.
Before every transaction
- Use the intended wallet and blockchain network.
- Check the full address and transaction amount.
- Review service and network fees.
- Understand which permissions remain afterward.
- Save the transaction hash and verify it on an explorer.
- Test unfamiliar workflows with a low-value wallet first.
- Read the Terms of Service and relevant tool documentation.