Nebula Protocol

Nebula is a protocol built on Terra that enables users gain exposure to narratives and strategies expressed through decentralized basket instruments called clusters. Clusters are smart contracts that manage a dynamic investment strategy.

These clusters possess two main unique properties:

Programmable, updates for target weight allocation

As opposed to its TradFi counterparts which are seldom managed and adjusted through rigid parameters, Clusters can quickly adjust their target allocations as frequently as every block, to actively steer their inventory composition to stay course or pivot according to their designed strategy. There are no inherent restrictions on the possible logic used or the assets included, and thus no limitations to what strategies the cluster can follow

Decentralized, continuous rebalancing

Whereas traditional structured products are periodically balanced by a centralized entity, clusters are continuously and organically kept in balance with their target through the activity and actions of the users of the protocol themselves. Clusters need no active management and are powered from the organic activity of Nebula users.

For more information about Nebula Protocol, please visit https://docs.neb.money/.

This bug bounty program is focused on their smart contracts and is focused on preventing:

• Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
• Permanent freezing of funds
• Any governance voting result manipulation
• Theft of unclaimed yield
• Permanent freezing of unclaimed yield

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

The following known issue is considered as out of scope of this program.

An actor could utilize the current governance snapshot feature to enable polls to reach quorum slightly more easily by:

• waiting until the poll is snapshotted
• staking a large amount of NEB tokens in governance
• vote on the poll

However:

• even without this snapshot implementation, actors could still manipulate quorum by staking/unstaking right before the poll ends to have different quorum calculation
• the difference is that without the snapshot feature they could do it right at the end if they do not like the outcome of the poll
• the snapshot feature is implemented to prevent whales denying reaching quorum

Rewards for critical smart contract vulnerabilities are further capped at 10% of mainnet economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 100 000 for Critical smart contract bug reports.

Payouts are handled by the Nebula Protocol team directly and are denominated in USD. However, payouts are done in UST.

Smart Contract

All smart contracts of Nebula Protocol can be found at https://github.com/nebula-protocol/nebula-contracts. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• 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)

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• 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
• Public disclosure of an unpatched vulnerability in an embargoed bounty