# New Risk Steward Signer

**URL:** https://governance.aave.com/t/new-risk-steward-signer/16749
**Category:** General
**Created:** [February 26, 2024, 7:32pm UTC](https://governance.aave.com/t/new-risk-steward-signer/16749 "2024-02-26T19:32:48Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![bgdlabs](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/bgdlabs/32/1829_2.png) [@bgdlabs](https://governance.aave.com/u/bgdlabs)
#### Post date: [February 27, 2024, 12:29pm UTC](https://governance.aave.com/t/new-risk-steward-signer/16749/2 "2024-02-27T12:29:52Z")

</div>

From the perspective of having designed the `CapsPlusSteward` (Risk Stewards Phase 1), we think it is quite reasonable to keep @ChaosLabs as sole signer, at least temporarily.  
The rational is the following:

- `CapsPlusSteward` has been the pilot program of Risk Stewards, with very limited scope and almost no possibility of damage: it only allows to increase supply and borrow caps, and in a pretty controlled manner.
- The procedures (generation of updates, tests) are pretty solid on [the repository](https://github.com/bgd-labs/aave-risk-stewards) we created back in the days for risk service providers to manage and use.
- Both ourselves supporting technically the community and Certora reviewing proposals are always available to help if any doubt/problem would arise for @ChaosLabs .

  

In addition, we would like to understand which is @Gauntlet suggestion for the upcoming [generalised Risk Stewards Phase 2](https://governance.aave.com/t/arfc-bgd-risk-steward-phase-2-risksteward/16204), given that from our understanding nothing has been suggested to the community.

---

_[View the full topic](https://governance.aave.com/t/new-risk-steward-signer/16749)._