# Builder Protocol Rewards Configuration Builder Protocol Rewards is almost ready for code audit! [Read overview here](https://hackmd.io/qu1JbwXWS4e_rf5FVyxl9g) Before deployment, we need yours and the DAO's input on a few important decisions. We're opening up discussion now and the finalised version will be ratified as a DAO proposal. --- ### Decision #1: % for BuilderDAO Rewards and Auction Client Referral Rewards These values have to be decided before the upgrades are deployed. ![](https://hackmd.io/_uploads/SJe8slTzp.png) **What should the percentage values highlighted in orange be?** *Note: These values can be changed again through a new contract deployment via a DAO proposal.* --- ### Decision #2: Management of BuilderDAO rewards Rewards can go to one of these two recipient options: **Option 1** Multisigs managed by the Ops Working Group - Gives us more flexibility as we iterate on this revenue model - More operational overhead **Option 2** Proxy contract controlled by BuilderDAO - More permissionless - Requires BuilderDAO to stay on L1 for the foreseeable future - Requires proposals to claim / bridge L2 rewards back to L1 mainnet on a regular basis Which option does the DAO prefer?