No private keys
Default ArkheionX workflows do not need private keys, seed phrases, wallet credentials, or signing material.
Safety model
ArkheionX creates review context. It does not make the final security judgment.
ArkheionX is designed to help humans organize protocol review surfaces. It can preserve evidence, assumptions, fixture output, and drift context, but every security conclusion still requires careful human review.
ArkheionX does not confirm vulnerabilities, assign final severity, prove protocol safety, submit reports, or stand in for security researchers.
Core boundaries
What the system is designed not to do.
No RPC by default
The public review workflow is designed around local files and deterministic artifacts, not live-chain calls.
No exploit execution
ArkheionX should not be treated as an exploit runner or transaction automation system.
No automatic security verdict
Outputs are review context. They are not final vulnerability confirmations, severity decisions, or audit conclusions.
Human review required
A human reviewer must inspect assumptions, evidence, test gaps, and context before making security decisions.
Authorized use only
Use ArkheionX only on systems, repositories, and review engagements where you have appropriate permission.
Responsible workflow
Use outputs as review evidence, not as final truth.
- Read source locally before trusting any generated context.
- Treat every artifact as a starting point for review, not a conclusion.
- Verify assumptions against code, tests, docs, and protocol behavior.
- Do not publish sensitive security details without responsible coordination.
- Do not submit reports directly from tool output without human validation.
- Do not claim protocol safety based on ArkheionX output alone.
Default operation
Local-first by default.
Input Local repository files
Network No RPC required by default
Secrets Private keys not required
Output Review context for human inspection
Disclosure
Handle sensitive findings carefully.
If ArkheionX helps you organize evidence around a possible security issue, verify it manually before sharing it. Avoid posting sensitive exploit details publicly. Follow the protocol’s responsible disclosure process or the agreed engagement process.
If you are reporting an issue in ArkheionX itself, use the project security policy and avoid placing sensitive operational details in public issues.
Summary