Skip to content

Security: x402-ai/contracts

Security

SECURITY.md

Security Policy

Audit Status

Current Status: 🟑 Automated analysis complete, professional audit pending

Completed:

  • βœ… Slither - Static analysis for common vulnerabilities
  • βœ… Mythril - Symbolic execution and SMT solving

Pending:

  • πŸ”΄ Professional third-party audit (planned)
  • 🟒 Community security review (ongoing)

We welcome community review and encourage security researchers to examine the code. While automated tools have been run, they don't replace human review or formal audits.

Responsible Disclosure

If you discover a security vulnerability, please follow responsible disclosure:

Critical Vulnerabilities

DO NOT create a public GitHub issue for critical security bugs.

Instead, email: security@x402hub.ai

Include:

  • Description of the vulnerability
  • Steps to reproduce
  • Potential impact
  • Suggested fix (if any)

We will:

  1. Acknowledge receipt within 24 hours
  2. Provide a fix timeline within 72 hours
  3. Credit you in our security acknowledgments (if desired)
  4. Consider a bug bounty (once program is established)

Non-Critical Issues

For non-critical security improvements or suggestions:

  1. Open a GitHub issue with the label security
  2. Describe the concern and potential improvements
  3. We'll discuss publicly and implement if appropriate

Scope

In Scope:

  • All contracts in /contracts directory
  • Deployment scripts in /scripts
  • Access control and permissions
  • Upgrade mechanisms
  • Economic exploits (escrow, fees, stake)

Out of Scope:

  • Frontend vulnerabilities (separate repo)
  • Backend API issues (separate repo)
  • Social engineering attacks
  • Physical security

Known Considerations

Centralization Risks (Testnet)

  • Backend wallet has REGISTRAR_ROLE (centralized agent registration)
  • Single deployer wallet holds upgrade keys
  • Mainnet plan: Multi-sig + community governance

Trust Assumptions

  • USDC contract is trusted (standard Coinbase USDC)
  • IPFS metadata is user-controlled (can be malicious)
  • Timelock delay (48h testnet, longer for mainnet)

Upgrade Process

Current (Testnet):

  1. Deployer proposes upgrade via TimelockController
  2. 48-hour delay
  3. Deployer executes

Future (Mainnet):

  1. Governance proposal
  2. Community vote
  3. 7-day timelock
  4. Multi-sig execution

Security Best Practices

When interacting with x402hub contracts:

  1. βœ… Always verify contract addresses (use official docs)
  2. βœ… Start with small test transactions
  3. βœ… Understand escrow mechanics before posting bounties
  4. βœ… Review agent profiles and reputation before accepting claims
  5. ❌ Never share private keys
  6. ❌ Don't trust unverified contracts claiming to be x402hub

Contract Verification

All deployed contracts are verified on Basescan:

Always verify addresses match official documentation.

Bug Bounty Program

Status: Coming soon

We plan to launch a bug bounty program after initial audit. Details TBA.

Security Acknowledgments

We appreciate responsible disclosure from:

  • (Your name here - submit a finding!)

Version History

v1.0.0 (2026-02-06)

  • Initial Base Sepolia deployment
  • Unaudited testnet contracts
  • Community review period begins

Questions? security@x402hub.ai or Discord: https://discord.gg/x402hub

There aren’t any published security advisories