Pilgrim Documentation
  • Pilgrim Overview & Concepts
  • White Paper
    • Pilgrim White Paper
    • Valuation & Trading Algorithm
  • Resources
    • Pilgrim Web App
    • Forum
    • Discord
    • Telegram
    • GitHub
  • The Pilgrim Token
    • Tokenomics Overview
    • Token Distribution
    • Trading Fee
  • Trader's and Creator's Guide
    • The Bidders Queue
    • Arbitraging Positions
    • Earning Yield
  • The Pilgrim DAO
    • Governance & Operations
    • Development & Key Stakeholders
  • Security
    • Protocol Security
  • Signature
    • Signed off by Test in Prod
Powered by GitBook
On this page
  • Smart contract audits
  • Bug reports and bounty policies
  1. Security

Protocol Security

PreviousDevelopment & Key Stakeholders

Last updated 3 years ago

Smart contract audits

Pilgrim Protocol's core smart contracts were audited by , with plans to request additional audits from more firms as the protocol matures.

Note that the audit report listed here was targeted for an internal development version of Pilgrim core contracts that is slightly different from the version targeted for final release.

Bug reports and bounty policies

While the Pilgrim Protocol team have made all efforts necessary to secure all smart contracts involved, there may be undiscovered vulnerabilities that puts users' funds at risk.

Please do not hesitate to contact the Pilgrim core development team at , with a public PGP encryption key available if necessary. Bug bounties will be given out in PIL tokens on a per-case basis, depending on severity of the reported vulnerability.

The Pilgrim team is planning to work with DeFi bug bounty platforms, such as , to streamline our bounty policies in the near future.

SOOHO
security@pilgrim.money
here
Immunefi
438KB
[ENG]Pilgrim_Security_Assessment.pdf
pdf
476KB
[KOR]Pilgrim_Security_Assessment.pdf
pdf