LEEQUID
  • 👋 Welcome
  • Navigating LEEQUID
    • 🌱 Staking
      • The staking protocol
      • Matching stake to unstake requests
      • Potential wait times while staking
      • Deposited LYX lifecycle
      • Importing sLYX to your wallet
    • 🍇 Collecting rewards
      • Reward distribution in the LEEQUID protocol
      • Auto-compounding
      • Withdrawing rewards
      • Reward calculation in Proof of Stake
    • 🍂 Exiting the protocol
      • Option 1: swapping sLYX for LYX
      • Option 2: unstaking through the staking pool
      • Matching unstake to stake requests
      • Potential wait times while unstaking
    • 🍷 Claiming
      • Claim queued stake
      • Claim unstaked LYX
      • Claim rewards
    • 🔄 Swapping
      • LYX for sLYX: An instant alternative to staking
      • sLYX for LYX: an instant alternative to exiting
      • Providing liquidty
      • Providing Liquidity: a practical example
  • LEEQUID in depth
    • 🔐 Protocol security and risks
      • Security overview
      • Smart contract code correctness
      • Slashing and unexpected validator behaviour
      • sLYX token: economic balance
      • Validator key management
    • 📃 Smart contracts
      • Oracles
      • Merkle Distributor
      • Rewards
      • Pool
      • StakedLyxToken
      • FeesEscrow
    • 💧 The sLYX token
      • Acquiring sLYX
      • 1:1 ratio with LYX
      • Potential unpeg of sLYX from LYX
    • 💦 The liquidity pool (DEX)
      • Implementation
  • Incident Response
    • Contacts
    • Vulnerability Disclosure Policy
Powered by GitBook
On this page
  • Introduction
  • Systems in Scope
  • Out of Scope
  • Our Commitment
  • Our Expectations
  • Official Channels
  • Safe Harbor
  1. Incident Response

Vulnerability Disclosure Policy

Introduction

LEEQUID welcomes feedback from security researchers and the general public to help improve our protocol's security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you.

This policy outlines steps for reporting vulnerabilities to us, what we expect, and what you can expect from us.

Systems in Scope

This policy applies to any digital assets owned, operated, or maintained by LEEQUID.

Out of Scope

  • Assets or other equipment not owned by parties participating in this policy.

Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

Our Commitment

When working with us, according to this policy, you can expect us to:

  • Respond to your report promptly, and work with you to understand and validate your report;

  • Strive to keep you informed about the progress of a vulnerability as it is processed;

  • Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and

  • Extend Safe Harbor for your vulnerability research that is related to this policy.

Our Expectations

In participating in our vulnerability disclosure program in good faith, we ask that you:

  • Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;

  • Report any vulnerability you’ve discovered promptly;

  • Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;

  • Use only the Official Channels to discuss vulnerability information with us;

  • Provide us with a reasonable amount of time (at least 45 days from the initial report) to resolve the issue before you disclose it publicly;

  • Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;

  • If a vulnerability provides unintended access to data: limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept;

  • You should only interact with test accounts you own or with explicit permission from the account holder; and

  • Do not engage in extortion.

Official Channels

Please report security issues via security@dropps.io, providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue.

Safe Harbor

When conducting vulnerability research (and as per this policy) we consider research conducted under this policy to be:

  • Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;

  • Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;

  • Exempt from restrictions in our Terms of Service (TOS) and/or Acceptable Usage Policy (AUP) that would interfere with conducting security research, and we waive those restrictions on a limited basis; and

  • Lawful, helpful to the overall security of the Internet, and conducted in good faith.

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.

Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.

Last updated 1 year ago