The first cryptocurrency built for Corporate Survivors.

"This policy was reviewed during a meeting that should have been an email. It is, for once, the email."

Filing Ref.: SEC-001
Effective Date: Upon commit to main
Version: 1.0
Status: Active 🟢

This document defines how security issues, scam reports, and incident response work for the CubertCoin project — covering the GitHub repository, smart contract, official channels, and treasury infrastructure.

If you discover a security vulnerability — in this repository, the smart contract (once deployed), or any official CubertCoin channel (e.g. a compromised Discord bot, a defaced website, a hijacked social account) — please report it responsibly.

Preferred: Open a private security advisory on GitHub. This keeps the report private until it's resolved.

If the link above is unavailable, private vulnerability reporting may not yet be enabled for this repository — in that case, use the alternative method below.

Alternative: Contact the Founder directly via the official channels listed below. Do not disclose unpatched vulnerabilities publicly (Discord, Telegram, X, GitHub Issues) until the Founder has confirmed the report and a fix or mitigation is in place.

• A clear description of the issue
• Steps to reproduce (if applicable)
• Potential impact (funds at risk, contract behavior, etc.)
• Your contact information, if you'd like a response

Responsible disclosure helps protect the community. Anyone who reports a valid issue in good faith will be credited (if desired) once the issue is resolved.

This is the most common "security" issue a memecoin project faces — and the one most likely to affect holders directly.

CubertCoin operates a zero-tolerance policy for scams, impersonation, and contract address fraud, as defined in the Governance Charter (Article VI).

The official $CUBE contract address, announcements, and links will only ever be published via:

Any contract address, link, or announcement from any other source — including DMs, comments, or accounts impersonating the project — is unauthorized and should be treated as a scam.

🔑 **No one from CubertCoin will ever DM you first, ask for your seed phrase, private key, or wallet approval "to verify your wallet," or ask you to connect your wallet to a site outside cubertcoin.com. Any message claiming otherwise — even from an account that looks like an admin or moderator — is a scam.

1. Do not interact with the suspicious link, contract, or account.
2. Report it via GitHub Issues or the official Discord/Telegram.
3. Include screenshots, links, and contract addresses where possible.

Per the Governance Charter, Article VI:

1. Core Contributors flag and document the incident.
2. A community warning is issued within 2 hours across all official channels.
3. The Founder reviews and issues an official statement within 24 hours.
4. The incident is logged in a public registry (to be established at launch).

The security of project funds and the $CUBE token itself relies on verifiable, on-chain mechanisms rather than promises:

Once executed, all of the above will be verifiable on-chain via the On-Chain Verification table in the Tokenomics document — including direct links to Solscan/Solana Explorer for each contract and transaction.

While the project is in its current solo-founder phase:

• The Treasury multisig is self-custodied across separate physical devices, including at least one hardware wallet, to reduce single-device compromise risk.
• No single device or session has unilateral control over treasury funds.
• Liquidity and team token allocations, once locked via Streamflow, are governed by immutable smart contracts — not even the Founder can bypass them before the unlock date. As the project grows, the plan is to evolve toward additional independent signers on the Treasury multisig, per the Governance Charter, Article IV.

A dedicated security contact email may be added at launch.

• ❓ FAQ
• 📘 Brand Book
• 📋 Changelog
• ⚖️ Code of Conduct
• 📄 The Cubert Thesis
• 👔 Employee Handbook
• 📖 Glossary
• 🏛️ Governance Charter
• 🎨 Media Kit
• ⚠️ Risk Disclosure
• 🗺️ Roadmap
• 📊 Tokenomics
• 🤝 Contributing Guide

Proof of Burnout.

Another Meeting. Another Token.

CubertCoin Security Policy · v1.0 · Filed under: SEC-001