1. What we will never do
Scammers often pretend to be a platform's team. Whatever a message says, BlueBox will never:
- Ask for your seed phrase, private key or wallet password.
- Send you a direct message first to offer support, a refund or an airdrop.
- Ask you to "validate", "sync" or "unlock" your wallet on another site.
- Ask you to send tokens to receive a reward. Quest rewards are claimed from the quest page itself.
Before you sign a transaction, read what your wallet shows. If a request feels wrong, stop and ask us in our Discord.
2. Official links
Our only website is blueboxgg.com. Check the address bar before you connect a wallet; look out for extra letters, hyphens or other domain endings.
- X (Twitter): x.com/BlueboxSpace
- Discord: discord.gg/cAVAZR7Xyq
- Telegram: t.me/+e3XzMAxrruhlZjY9
- Email: contact@blueboxgg.com
3. How we protect your account
- You sign in by signing a message with your wallet. Signing in never moves funds and never gives us control of your wallet.
- Sessions are kept in secure cookies and are ended on our side when you sign out or an account is banned.
- Quest tasks are checked by our servers before a reward can be claimed, and reward claims need an approval signed by our server, so a pool only pays wallets that finished the quest.
- Email addresses are confirmed with a one-time code, and sign-up and sensitive actions are rate limited.
- Automated and duplicate accounts are detected with bot protection and on-chain checks.
- Staff tools check admin rights on the server for every request, and access to personal data is limited to the people who need it.
4. Our smart contracts
These are the contracts the Platform uses on Bitkub Chain (chain ID 96). If a site or message asks you to interact with a BlueBox contract at a different address, it is not us.
Quest rewards
Holds quest reward pools and pays claims the server has approved
0x3aca000d5fbc7790ba2dbfdd9270a94186cf01caBlue Pass
Your soulbound reputation pass
0xe7cBBA037CC410935bA26785f4797506d07712D4BlueNFT market
Listings and sales on BlueNFT
0xa3cc4871adf8bfc3f4a1afe7c7ac0a376eb1273cBlueTools token factory
Creates tokens from BlueTools
0x78039aF9a13B83Ed3841918836C11e9AAbc9497FBlueTools locker
Token and liquidity locks
0xD20728d0EfD1Cec77D7B5f0D6933a0D2f90C7E49BlueTools vesting
Vesting schedules
0x6882284C561Fc062990e848A73e1d20aA82c08B6BlueTools multisender
Sends tokens to many wallets in one transaction
0xA27B77aCA200b6710B4728d90194B96bFeF91f56
Each address opens on KubScan, where you can read the contract and its transactions.
5. Report a vulnerability
If you believe you have found a security issue in BlueBox, please tell us privately first. Email contact@blueboxgg.com with the subject "Security report" and include:
- What the issue is and what an attacker could do with it.
- The page, API endpoint or contract address affected.
- Steps to reproduce it, and a proof of concept if you have one.
- How we can reach you, and whether you would like to be credited.
We will confirm we received it, keep you updated while we fix it, and let you know when it is resolved. We aim to reply within a few working days. Please do not share the details publicly until we have fixed the issue.
6. Rules for security research
We will not take legal action against research done in good faith that follows these rules, and we will treat your report as authorised:
- Test only with your own accounts and wallets. Do not access, change or delete other people's data.
- Stop and report as soon as you find access to data or funds that are not yours.
- Do not run denial-of-service attacks, heavy automated scans or spam.
- Do not phish or socially engineer our team or users, and do not test physical security.
- On mainnet contracts, do not take funds that are not yours. Use a local fork to show an exploit.
In scope: blueboxgg.com, its APIs and the contracts listed above. Out of scope: services we do not run (wallet apps, sign-in providers, Discord, Bitkub Chain itself), reports about missing best-practice headers or rate limits with no real impact, and issues that need a compromised device.