Skip to content
Mainnet betaPaxeer X is live on chain ID 125. Follow it on Paxscan.

Find a flaw.Get paid to report it.

Paxeer X handles authorization, accounting, custody, bridging and settlement of real value. Report a vulnerability privately by email and earn $500 to $100,000 USD.

A magnifying glass over a terminal window
  • $100,000Top reward per unique vulnerability, in USD
  • $500Minimum reward for an eligible finding
  • 3 daysTarget to acknowledge a report, in business days

What sets the reward.

Rewards range from $500 to $100,000 USD per unique vulnerability, paid once to the first reporter. Four things decide the amount.

  • 01

    Subsystem

    Which part of the code the vulnerability is in.

  • 02

    Role

    The role that subsystem plays in the network.

  • 03

    Severity

    How severe the issue is and how it affects core functions.

  • 04

    Funds at risk

    The risk the issue poses to user funds.

The repository text of SECURITY.md is the bug bounty policy. Where this page and that file differ, the file applies.

Three conditions for a reward.

A report that misses any one of them is handled as an ordinary report, with no reward.

  1. 01

    Email only

    Submit to security@sidioralabs.com, and only there.

  2. 02

    A full report

    A full and clear report covering every item in the list below, including an end-to-end reproduction.

  3. 03

    Credentials

    Show you are legitimate and competent: prior published disclosures or CVE credits, a professional or audit-firm affiliation, a verifiable identity, and how you found the issue.

Reports made through GitHub, including private vulnerability reporting, or any other public surface are fixed by the repair programme without attribution or reward.

What a report includes.

Treat any defect that can affect value conservation, authority, finality, replay determinism, withdrawal uniqueness, upgrade safety or private key handling as a security issue.

Include

  • 01The affected commit and component
  • 02Prerequisites and an end-to-end reproduction
  • 03The violated invariant and the plausible impact
  • 04The privileges exploitation needs, such as a validator, governance, attestor or operator key
  • 05Any proposed fix or test case
An open envelope releasing a blue card of code into a data stream

What is in scope.

The code in the Paxeer X Network repository. The chain node and kernel root directories move under core/ in a later release.

In scope

Chain node
The Paxeer X chain node and its modules, precompiles, RPC and storage: node/, modules/, precompiles/, rpc/, consensus/, storage/, engine/ and the other root Go packages.
LayerX kernel
The kernel, its programs and layerxctl: src/, include/, cmd/, programs/.
Vendored dependencies
The dependency trees the node builds from: core/deps/.
Contracts
The Solidity contracts: contracts/, contracts/bridge/, contracts/launchpad/.
Services, SDKs and apps
Off-chain services, SDKs and applications: services/, sdk/, apps/.

Supported: main and the current release named in tools/release/version.json. Fixes land on main and ship in the next chain node release.

Out of scope

  • Third-party services and integrations
  • Issues already known or reported
  • Social engineering
  • Defects that need a compromised validator, governance or operator key, unless the code fails to enforce a limit it claims to enforce
  • Denial of service by sheer traffic volume against hosted endpoints
  • Findings from automated scanners without a demonstrated impact
  • Defects in an upstream project that do not affect how this repository uses it; report those upstream

Response targets.

Best-effort commitments. Triage is counted from receipt, remediation from the severity decision.

Acknowledge
Within three business days of receipt.
Triage
A scope and severity decision within ten business days of receipt.
Status updates
At least every fourteen days while remediation is in progress.
Disclosure
Coordinated disclosure targeted within fourteen days of the fix being available.

Remediation, from the severity decision

Critical
30 days
High
60 days
Medium
90 days
Low
Next scheduled release

If a target is missed, follow up by email or in the private advisory. After two further business days without a response, email security@sidioralabs.com with the report or advisory identifier.

Rules of engagement.

Test only against systems and assets you own or have written permission to test. Stop at a proof of concept.

Do

  • Test only systems and assets you own or have written permission to test.
  • Stop testing at a proof of concept.
  • Keep the issue private until it is fixed and the advisory is published.

Do not

  • Probe public endpoints, validators, bridges or user data.
  • Move funds that are not your own.
  • Keep secrets you obtain during research.
  • Disclose a suspected vulnerability publicly.
A seal press leaving a seal on a sheet
Fig. 1 Published once fixed

What happens after you report.

The maintainers confirm receipt, assess scope and severity, and work on the fix in a private advisory fork when one is needed.

The fix
Lands on main. When it changes the chain node, it ships in a release.
The advisory
Published once the fix is available, crediting reporters who submitted by email only, unless they ask otherwise.
Out of scope
The report is closed with the reason given by email or in the advisory.
Until then
Keep details private until the advisory is published.

Questions.

Can I report through GitHub instead?

GitHub private vulnerability reporting stays open and only the maintainers see it, but reports made there, or on any other public surface, are fixed without attribution or reward. To be eligible for the bounty, report by email.

Open a GitHub report (no reward)
Two of us found the same issue. Who is paid?

Rewards are paid once per unique vulnerability, to the first reporter.

What counts as credentials?

For example prior published disclosures or CVE credits, a professional or audit-firm affiliation, a verifiable identity, and an account of how you found the issue.

Does an attack that needs a validator or governance key count?

Not if it depends on a compromised validator, governance or operator key, unless the code fails to enforce a limit it claims to enforce.

Is the wasmer advisory GHSA-55f3-3qvg-8pv5 a finding?

No. It is a known exemption: wasmer 4.2.2 is pinned by cosmwasm-vm 1.5.12 in wasm-runtime/libwasmvm, and the modules load without WASI filesystem access. The exemption holds until the next runtime upgrade, when it is reviewed.

Read the advisory
What about a conduct concern?

A conduct concern that is not a vulnerability follows the code of conduct in the repository.

Found something?

Email security@sidioralabs.com with the full report and your credentials. Keep it private until the advisory is published.

A canal lock: gates hold each reach at its own level