Gro

G^2 (GSquared) is an upgraded version of Gro protocol- a stablecoin yield aggregator that tranches risk and yield. The revamped architecture simplifies the protocol by separating out previously interdependent logic into their own module contracts.

Initially the protocol has two risk- and yield-tranched assets: the PWRD stablecoin and the Vault. All deposits are non-custodially allocated to a set of strategies. Depositors into the Vault receive a higher proportion of system yields but also take on extra smart contract and stable coin risk.

Inversely, the PWRD stablecoin receives a smaller portion of the system yield but is protected against these risks. The protocol comprises of multiple smart contracts and modules, with multiple changes from the previous version of the protocol :

• The Vault and strategies have been moved out into their own stand alone module, the GVault is responsible for generating yield on the by deploying the underlying asset into strategies.
• The share tokens from the GVault are EIP-4626 compliant
• A set of keeper logic contract accompanies the GVault to allow for decentralized harvests and interactions with the vaults strategies
• Decentralized stop loss logic has been implemented to automatic realization of losses in the vaults strategies
• The tranching logic has also been seperated out into its own stand alone module, the GTranche.
• The tranche acts as a wrapper for 4626 compatible tokens
• The GTranche then distributes yield between the two tranches based off of a modular yield sharing strategy defined in a plug-in contract

The first deployment of G^2 consists of a single asset vault (3Crv) which allows the protocol to support major stablecoins (DAI/USDC/USDT) without taking on pricing risk between the asset in different parts of the system. The 4626 compatible token of this vault (G3Crv) will be wrapped in the tranche, which will implement a fixed yield distribution strategy for the Senior tranche. The GTranche is designed to be able to support multiple 4626 tokens, and is supported by a plug in generalized Relation Module contract, which allows the tranche to define a relationship between the underlying 4626 compatible tokens, enabling users to withdraw any token independent of which one they deposited.

For more information about Gro, please visit https://gro.xyz/. For more technical documentation, please visit https://docs.gro.xyz/

This bug bounty program is focused on their smart contracts, and is focused on preventing the following impacts:

• Thefts and/or freezing of principal funds in protocol of any amount
• Thefts and/or freezing of unclaimed yield of any amount
• Temporary freezing of funds for X minutes/hours/days
• Smart contract fails to deliver promised returns
• Sets of protocol interactions which benefit the person making these interactions at the expense of other users invested in the protocol, or the protocol itself
• Protocol and/or oracle interactions which result in unfair allocation of gains to specific users

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

Critical bug reports are capped at 10% of economic damage, primarily taking into consideration the funds at risk, but can also consider other factors such as branding and PR, all fully at the discretion of the team. However, there is a minimum reward of USD 50 000.

Payouts are paid out of the DAO treasury and handled by the Gro core contributor team directly. The bounty is denominated in USD, and will wholly or partly be paid in USDC. Gro protocol reserves the right to also pay out part of the bounty in its governance token.

Smart Contract

For added reference, here are the external dependencies that interact with the Gro protocol:

DAI - https://etherscan.io/address/0x6B175474E89094C44Da98b954EedeAC495271d0F

USDC - https://etherscan.io/address/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48

USDT - https://etherscan.io/address/0xdAC17F958D2ee523a2206206994597C13D831ec7

Curve3Pool - https://etherscan.io/address/0xbEbc44782C7dB0a1A60Cb6fe97d0b483032FF1C7

3Crv - https://etherscan.io/address/0x6c3F90f043a72FA612cbac8115EE7e52BDe6E490

For now, no GitHub repo is publicly available, and so a PoC is not required for any bug report. In the event of a PoC being required for final validation of a bug to clarify disagreements on a bug report’s validity, access will be provided.

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

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