Security & Bug Bounty

IOST Security & Bug Bounty Program

Help protect the IOST L1 network and its node implementation.

Eligible reports may receive up to 500 USDT per unique vulnerability under the standard reward program. Critical vulnerabilities may qualify for higher rewards, subject to separate assessment and budget approval.

Standard reward
Up to 500 USDT
Per unique vulnerability
Critical vulnerabilities
May exceed 1,000 USDT
Subject to separate assessment and budget approval
Submit a report
dev@iost.io
Email subject[IOST Security] IOST L1 Blockchain — Brief Description

01Scope

This program covers only the following target:

IOST L1 Blockchain

IOST L1 node implementation, including transaction validation, signatures, consensus, authorization, and smart contract execution.

Only the target listed above is in scope. All other products and services are outside the scope of this program unless IOST provides prior written confirmation for a specific target.

02Vulnerabilities of Interest

We welcome reports demonstrating a meaningful security impact on the in-scope IOST L1 node implementation, including:

  • Unauthorized asset transfers, permanent freezing of assets, or other unintended asset movement caused by node-level validation, authorization, or execution flaws.
  • Transaction replay, duplicate execution, signature verification flaws, authorization bypasses, or permission-evaluation errors.
  • Consensus, block validation, fork-choice, finality, or state-consistency vulnerabilities.
  • Transaction or block-processing flaws that may cause inconsistent execution, invalid state transitions, or acceptance of invalid data.
  • Smart contract execution engine, gas-metering, system-contract, or native-contract vulnerabilities that affect the security or integrity of the IOST L1 network.
  • Remotely reachable node crashes, memory exhaustion, or other availability vulnerabilities with realistic attack conditions and material network impact.
  • Remote code execution or sensitive information disclosure within the IOST L1 node implementation.
Reports must explain realistic attack prerequisites and consequences. A theoretical possibility, code-quality observation, or crash reachable only through trusted local access does not by itself establish reward eligibility.

03Report Requirements

Please include:

  1. 01Summary

    The vulnerability type, affected functionality, and potential impact.

  2. 02Affected target

    The affected go-iost version, commit hash, component, and relevant source files or functions.

  3. 03Reproduction materials

    Clear reproduction steps and a minimal proof of concept, test case, or other sufficient evidence.

  4. 04Testing environment

    Specify the local, isolated, or explicitly authorized environment used.

  5. 05Supporting evidence

    Relevant logs, stack traces, screenshots, or transaction records, with sensitive information removed.

  6. 06Contact details

    Information allowing our team to follow up. Suggested remediation is welcome but optional.

Do not submit private keys, seed phrases, passwords, or unrelated personal information. If you discover exposed credentials, initially provide their location and redacted evidence.

04Responsible Testing and Disclosure

Inclusion in the reward scope does not authorize unrestricted testing.
  • Testing should take place in a local or isolated environment.
  • Active vulnerability testing against mainnet, public testnets, public nodes, or public RPC endpoints requires prior written authorization from IOST and must remain within the agreed scope.
  • Do not access or transfer other users' assets, alter other users' data, or obtain unnecessary private information.
  • Do not conduct denial-of-service attacks, stress testing, large-scale automated scanning, phishing, or social engineering.
  • If you unexpectedly encounter sensitive data, gain additional privileges, or cause disruption, stop testing immediately, retain only the minimum necessary redacted evidence, and report the issue.
  • Submit reports privately through the designated email address and coordinate disclosure with IOST to allow reasonable time for remediation and network protection.

05Rewards and Eligibility

Validated reports that meet this program’s requirements may receive up to 500 USDT per unique vulnerability under the standard reward program.

Critical vulnerabilities may receive rewards exceeding 1,000 USDT, subject to separate assessment and budget approval. Higher rewards are not guaranteed.

Rewards are assessed based on:

  • Demonstrated security impact and severity.
  • Exploitability, attack prerequisites, and affected scope.
  • Report completeness, evidence quality, and reproducibility.
  • Whether a currently supported version is affected.
  • Compliance with testing authorization and coordinated disclosure requirements.

Generally, only the first sufficiently detailed, reproducible report of a previously unknown vulnerability is eligible.

A single root cause producing multiple symptoms, triggers, or affected code paths will generally be assessed as one vulnerability. Issues with genuinely independent root causes may be assessed separately.

The following are generally not eligible for rewards:

  • Duplicate reports or issues already documented by the IOST team.
  • Reports concerning targets outside the scope listed in this policy.
  • Automated scan results without demonstrated security impact.
  • Code-quality observations, hardening suggestions, or best-practice recommendations without a verifiable exploitation impact.
  • Visual, documentation, translation, or ordinary functionality issues without security impact.
  • Issues affecting only unsupported versions, without evidence that a currently supported version remains affected.
  • Vulnerabilities requiring compromised administrator, validator, or private keys unless the report demonstrates an additional security-boundary failure.
Submitting a report does not guarantee a reward. IOST will communicate its assessment and any approved amount directly to the reporter. A receiving wallet address and network will be requested only after reward approval.

06Review, Remediation, and Recognition

IOST will review submissions, request additional information where necessary, and coordinate validation, remediation, and disclosure with the reporter.

With the reporter’s consent, IOST may publicly acknowledge their contribution following coordinated disclosure.

This policy takes effect upon publication and does not retroactively change the terms applicable to reports submitted before the revised policy was published.

Submit a report
dev@iost.io
Email subject[IOST Security] IOST L1 Blockchain — Brief Description
Developers
PayPIN Applications
others
Security & Bug BountySecurity & Bug Bounty
Purchased but havn't claimed your node?
Get Connected
This website does not provide service for the countries where crypto currency are prohibited.
© 2026 IOST Foundation