🤖
LNS Documentation
  • Introduction
  • Terminology
  • Frequently Asked Questions
  • Tokenomics
  • LNS Deployments
  • Registrar Frequently Asked Questions
  • Deploying LNS on a Private Chain
  • DNS Registrar guide
  • Bug Bounty Program
  • ENS Improvement Proposals
    • ENSIP-1: ENS
    • ENSIP-2: Initial Hash Registrar
    • ENSIP-3: Reverse Resolution
    • ENSIP-4: Support for contract ABIs
    • ENSIP-5: Text Records
    • ENSIP-6: DNS-in-ENS
    • ENSIP-7: Contenthash field
    • ENSIP-8: Interface Discovery
    • ENSIP-9: Multichain Address Resolution
    • ENSIP-10: Wildcard Resolution
    • ENSIP-11: EVM compatible Chain Address Resolution
    • ENSIP-12: Avatar Text Records
  • Dapp Developer Guide
    • LNS Enabling your DApp
    • LNS Libraries
    • Working with LNS
    • Resolving Names
    • Managing Names
    • Registering & Renewing Names
    • LNS Front-End Design Guidelines
    • LNS as NFT
  • Contract API Reference
    • Name Processing
    • Registry
    • ReverseRegistrar
    • PublicResolver
    • .bch Permanent Registrar
      • Registrar
      • Controller
    • DNS Registrar
  • Contract Developer Guide
    • Resolving Names On-chain
    • Writing a Resolver
    • Writing a Registrar
    • LNS Support Chat
Powered by GitBook
On this page
  • ENS Specific Bugs
  • LNS Specific Bugs
  • Rules
  • Submitting a Bug
Edit on GitHub

Bug Bounty Program

The LNS bug bounty program rewards anyone who finds a bug in covered LNS smart contracts.

ENS Specific Bugs

Please report according to ENS rules described here https://docs.ens.domains/bug-bounty-program

LNS Specific Bugs

Rules

  • Issues that have already been submitted by another user or are already known to the LNS team are not eligible for bounty rewards.

  • Public disclosure of a vulnerability makes it ineligible for a bounty. This includes exploiting the bug on mainnet or any public test network.

  • The LNS team, employees and all other people paid by LNS project, directly or indirectly, are not eligible for rewards.

  • Only the smart contracts listed below are eligible for rewards. Websites and other infrastructure are not covered by the bounty program.

  • The LNS bounty program considers a number of variables in determining rewards. Determinations of eligibility, score and all terms related to an award are at the sole and final discretion of the LNS team.

Covered Contracts

The following smart contracts are covered by the bounty:

  • All deployed non-test contracts in bchdomains/bch-domains-tokens.

Submitting a Bug

Bugs should be submitted via email to bugs@bch.domains, or on Discord to @mainnet_pat#7609.

PreviousDNS Registrar guideNextENS Improvement Proposals

Last updated 3 years ago