Nayms
Program Overview
The Nayms Platform is a single environment for insurtech brokers to run their operations. Brokers can connect to alternative capital and access underwriting not present in other markets, and by placing capital and risks for Segregated Accounts, new revenue streams are created where transaction rails are automated.
For more information about Nayms, please visit https://nayms.com/.
Nayms provides rewards in USDC. For more details about the payment process, please view the Rewards by Threat Level section further below.
KYC Requirement
The provision of KYC is required to receive a reward for this bug bounty program where the following information will be required to be provided:
- Identity Document
- Proof of Address
KYC information is only required on confirmation of the validity of a bug report and will be handled by Sumsub (LINK). Link to KYC submission is here: https://in.sumsub.com/idensic/l/#/uni_5lU19AU1ouPfWGbI
Responsible Publication
Nayms adheres to category 3: Approval Required. 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
Nayms adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.
Known Issue Assurance
Nayms commits to providing Known Issue Assurance to bug submissions through their program. This means that Nayms 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.
Rewards by Threat Level
Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.
Reward Calculation for Critical Level Reports
For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 100,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 10,000 is to be rewarded in order to incentivize security researchers against withholding a bug report. For a bug to be deemed critical, the attack should happen from an unknown address. The setup in the poc may be done by admin accounts, but the attacking account must be unvetted.
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
Nayms has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
Proof of Concept (PoC) Requirements
A PoC is required for the following severity levels:
- Smart Contract, Critical Severity Level
- Smart Contract, High Severity Level
- Smart Contract, Medium Severity Level
- Smart Contract, Low Severity Level
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 Nayms team directly and are denominated in USD. However, payments are done in USDC.
Smart Contract
- Critical
- Level
- USD $10,000 to USD $100,000
- Payout
- High
- Level
- USD $5,000
- Payout
- Medium
- Level
- USD $2,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Assets in scope
- Smart Contract - NaymsType
All code of Nayms can be found at https://github.com/nayms/contracts-v3. . Documentation for the assets provided in the table can be found at https://nayms.gitbook.io/nayms-docs/.
Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
Smart Contract
- Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original resultsCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield from an unvetted addressCriticalImpact
- Permanent freezing of funds from an unvetted addressCriticalImpact
- Protocol insolvency from an unvetted addressCriticalImpact
- Manipulation of user roles inside the system via unvetted wallet or smart contract that may result in any critical severity issueCriticalImpact
- Manipulation of user roles inside the system via unvetted wallet or smart contract that may result in any high severity issueHighImpact
- Theft of unclaimed yieldHighImpact
- Theft of unclaimed royaltiesHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Permanent freezing of unclaimed royaltiesHighImpact
- Temporary freezing of fundsHighImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
- Contract fails to deliver promised returns, but doesn't lose valueLowImpact
Out of Scope & Rules
These impacts are out of scope for this bug bounty program.
All Categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by 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
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
Smart Contracts
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
- Best practice recommendations
The following activities are prohibited by this bug bounty program:
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty