Architecture is a starting point.
The technical paper describes the protocol design. It is not an audit of the current deployed network.
Read the sourcesSecurity
Confidence begins
with clarity.
Security reporting, verified information and a careful approach to network participation.
A direct reporting path
Found something
that needs attention?
Send an initial report to info@grap3.com with “Security report” in the subject. Describe the affected website or component and the impact you observed.
Include useful evidence.
- Affected URL or component and version, if known.
- A concise description and minimal reproduction steps.
- Expected behavior and observed impact.
- Your preferred contact details for follow-up.
Keep sensitive details out of public posts. Ask for a suitable channel before sharing personal data, credentials or confidential files.
Understand what you are using
Evidence before
assumptions.
Use verified parameters.
Confirm current network configuration, release information and official asset identifiers with the team.
Network resourcesKnow the two roles.
GRP is the core currency; GGT powers governance. Use official asset details before moving funds.
Understand GRPCheck the actual rules.
Proposal rights, voting and execution must follow the current published governance framework.
Explore GGTA reporting contact does not imply a bounty program, audit certification or guaranteed response time. Request current security and audit information from the team.