Switch eli_ from a Dynamic to Fixed Compensation Model

Context: Please refer to Original Full-Time Team Proposal

Key Terms:

• Dynamic Compensation: Lower Base Pay + Unlimited Upside Potential
• Static Compensation: Base Pay + No additional comp above this

Why?

Dynamic compensation was intended to incentivize full-time contributors to earn above their base wage; however, this now feels (1) like a distraction from work and (2) bad incentive alignment.

I’d prefer to be in a compensation model where I can just focus on results without having to worry about asking the DAO for additional comp.

Reminder: Basic Full-time Conditions

• Community can vote out a full time contributor at any point.
• Ends in 4 months and must reapply.
• Must hold 100% of existing $KRAUSE balance to receive pay.

Change

Original: 10k $KRAUSE with unlimited upside through additional proposals.

Fixed: 10k $KRAUSE + 6667 USDC fixed.

Transparency

For transparency’s sake, here’s what I’ve been up to since the initial proposal passed. This is not meant to be comprehensive, but rather a few highlights:

1. Building Krause House wallet / dashboard with the initial features of a (1) token weighted forum to discuss Snapshot votes and (2) a place to create petitions for specific people or teams to sign off on. I see this more generally as turning into a home where Jerry’s can (1) perform a number of voting functions, (2) interact with KH smart contracts for commitment staking or token lockups for multipliers, (3) so many possibilities, the design space here is huge.
2. Created Open Bounty Board + Discord Bot to help contributors and newcomers understand where they can provide value.
3. Built Snapshot Discord Bot to keep voters up to date from within the Discord.
4. Built Proposals Database Bot to pipe open proposals data into Discord (took offline, not sure if it’s useful).
5. Proposal reviews, working with contributors to edit/improve proposals, managing Snapshot, and working to improve ease of proposals. This includes experimenting with improved UX, including creating forms to help simplify the process and TL;DR versions of how governance works—more to come.
6. Working 1-on-1 with contributors to help them take leadership and initiate teams.
7. Generally, and most importantly, whatever is needed / general gardening of the DAO. Recruiting new talent, managing Discord, troubleshooting, fixing issues as they arise.

WAGBAT