PYRA logo PYRA Protocol
Public security scaffold for counsel review

PYRA Security Reporting

PYRA handles sensitive identity, wallet, and barter-network records. Security reports must be handled through a controlled channel, without exposing private member data or creating new risk.

Do not send secrets: Never send seed phrases, private keys, passwords, ID images, selfies, utility bills, or social security numbers through public website pages, GitHub issues, chat, or screenshots.

Security Contact

Report suspected security issues privately to damondanner@gmail.com. Do not publish vulnerability details publicly and do not attempt to access, download, modify, or exfiltrate data.

Responsible Testing Boundaries

Do not test against KYC records, member records, payment records, private admin panels, local office systems, wallets, private keys, seed phrases, third-party accounts, or production infrastructure without written authorization from Pyramidion Cryptocurrency LLC.

Useful Report Contents

A security report should include the affected URL or component, a concise description, reproduction steps, potential impact, whether any data was exposed, screenshots with sensitive information removed, and reporter contact information for follow-up.

No Bug Bounty Yet

PYRA does not currently operate a bug bounty program. Submitting a report does not create an employment, contractor, reward, or compensation relationship.