# Bloom Budget Proposal #22: Level & Unit Adjustments

- Space: [Bloom Studio](https://snapshot.box/s:gov.bloomstudio.eth.md)
- Author: 0xD80e4Ef6169e5F737430be8a845237Befb9a0aDB
- State: Closed
- Voting type: Weighted
- Start: 2024-08-30 01:06 UTC
- End: 2024-09-02 01:06 UTC
- Votes: 12
- Quorum: 25,000,000 voting power
- Open in Snapshot: https://snapshot.box/#/s:gov.bloomstudio.eth/proposal/0x36238c87da685defd3775ce982ec96ae5b61d6b10c2f8b436b418aaaacc2d613

## Results

- Adopt: 27,551,060.09 voting power, 100.0%
- Reassess: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

**Authors**
Lapras

**Type**
RUC

**Abstract**
This proposal seeks to make adjustments in units and leveling for a few contributors reflecting contributions and roles.

**Definitions**
None

 
 **Background**
Bloom's Recurring Unit Contributor program is designed to be flexible and accomodate individual circumstances, growth, and availability. Loosely, it is designed to maximize mobility within the system to best meet both the individual and project's needs. Over the last several months, a few notable examples have emerged: Balu has individual circumstances limiting his technical contributions but as a backbone of our backend team, we want to keep his involvement and make it commensurate to technical availability. Inversely, bagelface has taken on an increased role over time leading various projects on the backend. Lastly, friedplant has shown growth and technical comfort with increasingly larger projects, which aligns with a L2 role. In net, this proposal suggests three changes:

```
Balu L2 10u => L2 5u (Effective September 1, 2024)
bagelface L2 5u => L2 10u (Effective October 1, 2024)
friedplant L1 10u => L2 10u (Effective October 1, 2024)
```

 
 **Voting Options**
```
Adopt
Reassess
Abstain
```

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

