Enosys

Ēnosys pioneers research and development in blockchain technology, offering a suite of innovative products for seamless access to various applications across multiple chains. From the Flare Network to a multi-chain landscape, Ēnosys empowers blockchain communities worldwide.

For more information about Ēnosys, please visit https://enosys.global/

Ēnosys provides rewards in USDT. For more details about the payment process, please view the Rewards by Threat Level section further below.

Responsible Publication

Enosys adheres to category 1: Transparent. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.

Primacy of Impact vs Primacy of Rules

Enosys adheres to the Primacy of Impact for the following severity levels:

• Smart Contract - Critical
• Smart Contract - High
• Smart Contract - Medium

If a category’s severity level is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program as long as it involves an impact under that respective severity level. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi. Testnet and mock files are not covered under the Primacy of Impact. All other severity levels not listed here are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program.

Known Issue Assurance

Enosys commits to providing Known Issue Assurance to bug submissions through their program. This means that Enosys will either disclose known issues publicly or at the very least privately via a self-reported bug submission in order to allow for a more objective and streamlined mediation process to prove that an issue is known. Otherwise, assuming the bug report itself is valid, it would result in the bug report being considered in-scope and due 100% of the reward with respect to the bug bounty program terms.

Immunefi Standard Badge

Enosys has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to our best practices.

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.

Repeatable Attack Limitations

In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable.

Previous Audits

Enosys has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.

• WatchPug audit: https://github.com/flrfinance/bridge-contracts/blob/main/watchpug_audit.pdf

Proof of Concept (PoC) Requirements

A PoC is required for the following severity levels:

• Smart Contract - Critical
• Smart Contract - High
• Smart Contract - Medium

All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

Reward Payment Terms

Payouts are handled by the Enosys team directly and are denominated in USD, to be paid in USDT on the Ethereum Network.

The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability, as long as the token meets Immunefi’s minimum liquidity requirements. For avoidance of doubt, if the reward amount is USD 5 000 and the average price is USD 1.75 per token, then the reward will be 2857.142857 units of that token.

All code of Enosys can be found at https://github.com/flrfinance/bridge-contracts. Documentation for the assets provided in the table can be found at flrfinance.github.io/flr-wraps-contracts.

Smart Contract addresses for WrapMintBurn, WrapDepositRedeem, and WrapToken can be found here:

• FLRWrap XDC Mainnet - Songbird Canary Network deployment:
  • WrapMintBurn: https://songbird-explorer.flare.network/address/0xD5308A4Bb2D7121A26d0bd11257245F0EFDa2bc4
  • WrapDepositRedeem: https://explorer.xinfin.network/address/xdcD5308A4Bb2D7121A26d0bd11257245F0EFDa2bc4
  • WrapToken: https://songbird-explorer.flare.network/address/0xC54De96302981f87a6F80E4607593681B44d670c
• FLRWrap Ethereum Mainnet - Songbird Canary Network deployment:
  • WrapMintBurn: https://songbird-explorer.flare.network/address/0xB3902647015C17FC3c2f5ca5f5cb68BBf2D9B1E2
  • WrapDepositRedeem: https://etherscan.io/address/0xB3902647015C17FC3c2f5ca5f5cb68BBf2D9B1E2
  • WrapToken: https://songbird-explorer.flare.network/address/0x1a7b46656B2b8b29B1694229e122d066020503D0

Unless explicitly listed, only pages of the web/app assets in addition to the direct link are considered in-scope of the bug bounty program. Other subdomains are not considered as in-scope. However, for subdomain takeovers that lead to an impact on the in-scope asset, please refer to our page about Reported Subdomain Takeovers.

Other helpful links include:

• Enosys Bridge Whitepaper: https://enosys.global/papers/EnosysBridgeWhitepaper.pdf

These impacts are out of scope for this bug bounty program.

All Categories

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist), except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
• Broken link hijacking is out of scope

Smart Contracts and Blockchain/DLT

• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Centralization risks

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• Any testing with pricing oracles or third party smart contracts
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks
• Automated testing of services that generates significant amounts of traffic