Contact Team & community channels

Contact & Community

CPUNK is a community-driven, post-quantum protocol. The best way to engage is through our open channels – whether you are a validator, builder, researcher, or just exploring the ecosystem.

Primary hub: CPUNK Telegram & cpunk.club For sensitive issues, use email or direct DM.
Community

Official CPUNK channels

These are the primary places where CPUNK communicates. Always verify URLs to avoid phishing or impersonation.

Community Chat

Telegram

Real-time discussions, Q&A, and announcements. This is the fastest way to reach the community and often core contributors.

@chippunk_official

Beware of DMs pretending to be team members. Always double-check usernames and never share private keys or seed phrases.

News & Updates

X (Twitter)

High-level updates, release announcements, and ecosystem news around CPUNK, DNA Identity, and DNA-Messenger.

@OfficialCpunk

Follow for new videos, articles, exchange listings, and roadmap milestones.

Web Portal

CPUNK.CLUB

Community & validator portal for delegation, treasury information, and network stats. Designed as the operational layer of the ecosystem.

cpunk.club

Use CPUNK.CLUB for on-chain related views: treasury balances, validator data, delegation, and infrastructure metrics.

Code & Development

Repositories

Core protocol and application code for CPUNK and DNA-Messenger are developed in public repositories.

gitlab.cpunk.io

Refer to the repositories for technical details, issues, and contribution guidelines.

Direct Contact

Partnerships, media & security

Use email for topics that should not be handled in public chat: listings, media, legal, and security disclosures.

General & partnerships

For exchange listings, integrations, collaborations, and partnership proposals, please contact us via email with a short description of:

  • Who you are and which organization you represent
  • What type of collaboration you are interested in
  • Any relevant links or supporting material

Please avoid sending sensitive personal data by email. For strictly confidential topics, mention this clearly so the team can suggest a more appropriate channel.

Security & responsible disclosure

If you believe you have found a security issue in CPUNK, DNA-Messenger, or related infrastructure, we ask that you disclose it responsibly.

  • Include a clear description of the issue and potential impact
  • Provide step-by-step instructions or proof-of-concept, if possible
  • Do not publicly share the vulnerability before it is mitigated

At this stage we do not promise formal bug bounties, but good-faith researchers are highly appreciated and may be recognized by the community.

Impersonation & safety

CPUNK is a permissionless ecosystem. Anyone can create accounts using our name, themes, or imagery.

  • Always double-check URLs and usernames before interacting.
  • CPUNK team members will never ask for your seed phrase, private keys, or remote access to your device.
  • When in doubt, verify information through the official Telegram and X accounts listed above.