English

Treasury

Last Update: September 2023

At the heart of Beefy's operations is our Treasury, which is managed by our Core contributor team. As our $BIFI token is fully distributed, with no tokens reserved for later use, our entire operation is funded by our ongoing revenue-generating activities. To keep the lights on and our vaults autocompounding, Beefy relies on the constant vigilance of its treasury team to manage the use of our Treasury responsibly, and with the DAO's best interests at heart.

This page explains the history and structure of the Beefy Treasury, summarises our approach to treasury management, and provides the details you'll need to access our live treasury activities.

History

Beefy's core product - our Beefy Vaults - are designed from the ground up to generate fees for the project (see Beefy Fees Breakdown) to sustain our activities. As such, we have always been a revenue-generating project, and have always had some level of treasury inflows and outflows.

Over time, our treasury activities have become increasingly sophisticated. Initially, the project's founders privately managed the inflows from the smart contract to cover their costs in operating and maintaining the protocol. The original BeefyTreasury contract was deployed on 6 November 2020. The Treasury contract was very basic in functionality, allowing the native chain token and ERC-20/BEP-20 tokens to be withdrawn by the owner, which was the BeefyDeployer EOA.

By March 2021, Beefy had expanded to include more contributors, and so the Core contributor team created the #💵-treasury channel in the Beefy Discord as a place for discussion of all treasury-related issues. Over the next few months, Beefy became increasingly multichain, and additional BeefyTreasury contracts were deployed on Avalanche, Polygon, Fantom together with some other early chains. However, the Core team recognised the limitation of the early Treasury's design, and a move MultiSig wallets was debated, despite MultiSig solutions not being available on all chains.

By September 2021, the DAO had settled on moving to MultiSig wallets on BSC and Polygon (as the two chains with MultiSig solutions available at the time), and establishing the Treasury Council as the signers of the MultiSig. On 3 September 2021, a soft vote was concluded on Discord to appoint the new members of the Treasury Council. This was followed up by a Snapshot Proposal, which confirmed the initial 7 members. On 11 September, ownership of the original BeefyTreasury contract on BSC was transferred to the new MultiSig. Since then, the MultiSig system and Treasury Council has continued and expanded to each of Beefy's new chains.

Also in September 2021, Beefy's Core team began to implement bots in the #💵-treasury channel, initially displaying the value of the Treasury for the benefit of DAO members. By October 2022, this had evolved to include each new transactions live when posted from any of the Treasury's multisig wallets. Some of the key bot commands are:

  • Show Full Treasury: @Bitch I'm a Cow#9189 treasury

  • Show Full Treasury on Specified Chain: @Bitch I'm a Cow#9189 treasury {blockchain}

  • Show Current Cowllector Balances: @Bitch I'm a Cow#9189 cowllector balances

Treasury Council

As described above, the Treasury Council was formed in September 2021 as the team that should conduct and manage all Treasury transactions and related activities for Treasury management. The role of the Treasury Council has expanded gradually, to now include:

  • Orchestrating, signing and executing all Treasury transactions (i.e. payments out of Treasury);

  • Managing Treasury assets, such as creating and exiting protocol-owned liquidity and holding grants, pending rewards and other external assets;

  • Monitoring and providing operating capital (e.g. gas) for Beefy's infrastructure, including our Cowllector, Fee Batch Harvester and contributor EOAs;

  • Arranging for payment of key expenses, including contributor salaries, sponsorships, recurring hosting and service fees and reimbursement for contributor expenses; and

  • Handling regular bribe payments to partner exchanges.

The Treasury Council has 8 members, and requires consensus from any 4 to sign off on any MultiSig transaction before it can be executed. Details of the current 8 members and their Treasury EOA wallets are:

  • Beef Nugget: 0xd38d0dd50d03cea499df2b4c8d4b47458bee9358

  • ChiliConCarne: 0x645c2c6105604bfce05c1aab2cb598af393553d5

  • DefiDebauchery: 0x037465bF6a4A8D7F552AE18046478C6A727178F3

  • Moodini: 0xdae7624267e4515f40266a38505f4f7e13dbf6c4

  • Red Bull: 0x03e7302e3ecba4c1bd0e1841b55bf2c939e03fd3

  • Ser Loin: 0xa2894cec4a49014b00e84e71861344fc794b8c27

  • TBC: 0x428b2F01Bfb0917FE6FF463f37B0c47F1782B9Cd

  • YR2150: 0xF24f555d6765D559BFF4C5557dD9024CBA10d30e

Any questions for the Treasury Council should be directed to the #💵-treasury channel on the Beefy Discord. For security purposes, please do not directly message Council members instead, or your messages will be ignored and potentially blocked or reported.

Treasury Infrastructure

Beefy's Treasury relies on a few core building blocks of infrastructure to facilitate the secure inflows and outflows of funds from Treasury. The core elements are:

  • Treasury Multisig - multi-signature wallets controlled by the Treasury Council, used to hold all of the main assets of the treasury securely, and in a manner that can't be exploited by any single individual;

  • Treasury Contributor Wallets - externally-owned accounts (EOAs) controlled by different Beefy contributors, such as our Treasury Council members and other key DAO contributors. By using EOAs to interact with external protocols and contracts, we isolate the risk of hacks or exploits impacting the Beefy Treasury, by isolating it from externals and giving no or very limited exteranl approvals;

  • Cowllector - the Beefy Cowllector is a bot created and maintained by the Beefy Core which seeks to harvest Beefy vaults regularly (at least every 24 hours for all chains but Ethereum) and wherever a profitable opportunity presents itself. As the harvest caller claims a small fee as a proportion of the harvest, the Cowllector analyses the size of the potential reward versus the cost of harvesting, and makes automatic calls where appropriate;

  • Revenue Bridge - the Beefy Revenue Bridge is a set of contracts on each chain which facilitate the bridging of Beefy's fees back to Ethereum. The bridge contract performs a few functions to allocate and prepare them for bridging. The bridge itself contains multiple different bridging services, and will use the preferred method which has been specified to the contract. The bridge can either bridge directly to Ethereum, or back via any number of intermediate chains; and

  • Fee Batch - the Beefy Fee Batch is a set of contracts on each chain, which aggregate Beefy's fees from across the protocol into one place, to be able to efficiently distribute them to stakeholders. On Ethereum, the fees arrive to the Fee Batch, which aggregates all of the protocol's fees. Once a sufficient amount of tokens are batched token, the Fee Batch distributes them both to Treasury and - after swapping back to native $ETH - to the Incentive Programmes.

The treasury multisigs can be found at the following addresses for the following chains:

Older retired treasuries (either on retired chains or replaced by new treasuries) include:

Treasury Management

Management of Beefy's Treasury has also evolved over time, to reflect the changing needs of the protocol and the DAO. Operating on so many chains, each with their own sets of vaults, infrastructure and MultiSig wallets makes it a complicated process to actively manage the Treasury. Instead, a number of overarching principles have emerged to guide current best practices.

First and foremost, Beefy's contributor team have opted to operate the Treasury on each major chain primarily in stablecoins, to mitigate the downside risk of holding volatile assets. This allows Beefy to make clear and deliberate decisions about how to use its funds, free from the risks of current market condition. As such, the Fee Batcher on each major chain swaps all Beefy's vault fees into a designated currency for that chain, as detailed in Inflow Currencies below.

Secondly, it was decided that investing a portion of treasury assets in Beefy Vaults to generate passive income would be a sensible and smart use of funds. Generally speaking, only a small proportion of the Treasury held on our major chains is ever invested in Beefy Vaults, and they are always allocated to stablecoin-only vaults. Though returns on invested funds are generally relatively small, this mechanism does help to mitigate the inflationary nature of stablecoin valuations.

Finally, to facilitate liquidity for our tokens across the different chains, Beefy also invests in and maintains liquidity positions in our tokens, including both our $BIFI Token, and our Beefy-escrowed Tokens. Our $BIFI token is typically paired with native or gas tokens on the relevant chain, to provide the easiest route into the token for new arrivals on the chain. Once the bridged $BIFI token contract is deployed on a new chain, the contract is connected to the Beefy Bridge and our partners at Multichain, so that more $BIFI can be bridged onto the chain and so that an initial LP can be created.

Live summary details of the current state of the Beefy Treasury, including all liquid, staked/invested and locked tokens and liquidity positions, are available in the Treasury Dashboard page of the Beefy App.

Inflow Currencies

As described above in Treasury Management, inflows on our key blockchains are swapped into stablecoins for treasury management purposes, with each chain's Revenue Bridge contract adopting a key stablecoin for its operations. The following chains have the following nominated currencies:

  • Arbitrum: USDC

  • Avalanche: USDT

  • Base: WETH

  • BSC: BUSD

  • Canto: USDC

  • Cronos: USDC

  • Ethereum: USDC

  • Ethereum Validator: WETH (retained in validator)

  • Fantom: USDC

  • Fantom Validator: WBTC (gradually bridged to Ethereum)

  • Fuse: WFUSE

  • Fuse Validator: Fuse (retained in validator)

  • Kava: USDC

  • Metis: USDC

  • Moonbeam: MAI

  • Moonriver: USDC

  • Optimism: USDC

  • Polygon PoS: USDC

  • Polygon zkEVM: WETH

  • zkSync: WETH

Volumes and liquidity on Aurora, Celo, Emerald, Harmony and HECO are all currently too small to warrant stablecoin management, so vault fee inflows are typically swapped into the relevant native chain token instead.

Last updated