Cyan
Cyan is the first buy now pay later service for the metaverse. Our goal is to make NFTs and all metaverse assets attainable for everyone. Choose to finance your purchase over a period of three months, or get a collateralized loan on your existing NFTs. If you have ETH to stake, you can park them in our Vaults to earn yield!
PoC required
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.
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.
Public Disclosure of Known Issues
Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program.
- If the “setApprovalAll” or “approve” function from a particular collection is invoked prior to the creating of the loan, the locking mechanism will be unable to impede the transfer of the item.
- To mitigate this, Cyan team will never whitelist those functions to be called from Cyan wallet for any collection.
- ERC721Module is able to lock tokens that aren’t present in the wallet.
- Only CyanPaymentPlanV2 contract is able to call “setTokenLock” method and ownership of the token is verified on this contract.
- When declining a Buy Now, Pay Later (BNPL) payment plan, the system will refund the initial downpayment to the plan holder. Should the plan be pre-funded, the allocated funds will revert to the designated vault. However, if the payment plan uses the platform's native token and the plan owner is a smart contract that cannot accept this native token (either due to malicious intent or oversight), the BNPL rejection process will be halted.
Previous Audits
Cyan 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
- 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 Cyan team directly and are denominated in USD. However, payments are done in USDC.
Program Overview
Cyan is the first buy now pay later service for the metaverse. Our goal is to make NFTs and all metaverse assets attainable for everyone. Choose to finance your purchase over a period of three months, or get a collateralized loan on your existing NFTs. If you have ETH to stake, you can park them in our Vaults to earn yield!
For more information about Cyan, please visit https://www.usecyan.com/
Cyan provides rewards in USDC. For more details about the payment process, please view the Rewards by Threat Level section further below.
Responsible Publication
Cyan adheres to category 3. 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
Cyan 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
Cyan commits to providing Known Issue Assurance to bug submissions through their program. This means that Cyan 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
Cyan has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to our best practices.
Invoicing Information
If needed by the security researcher, Cyan is able to provide the necessary information for the proper issuance of an invoice. This includes:
- Corporate name
KYC not required
No KYC information is required for payout processing.
Prohibited Activities
- 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
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.