• © Goverland Inc. 2026
  • v1.0.3
  • Privacy Policy
  • Terms of Use
SharkDAOSharkDAOby0x40b6DF5F6217Fb1a1BeAf8FdBB9572304aa78C4ddropnerd.eth

SIP-00034: Coordinape Reward Adjustment

Voting ended over 4 years agoSucceeded

Author: @dropnerd, @kb1900

Purpose

  • allows the Coordinape working team to make changes

Summary

  • allows the Coordinape administrators (@synth and @dropnerd) to make changes to total Coordinape rewards when they both agree

Background

This proposal acts as a functional ammendment to SIP-00030 Should we fund the Coordinape Test Epoch? which passed on September 28, 2021. The language in the initial proposal was:

2.5 ETH and 875,000 SHARK will be allocated from the treasury for the epoch. The ETH will be released immediately, while the SHARK tokens will be held in escrow (time-locked) for 3 months and then released to recipients.

While in discussion with SyndicateDAO, several Sharks received some advice that we may want to separate the Coordinape ETH rewards from the Coordinape SHARK rewards. To preserve flexibility, we propose to set the amount after we discuss more. To maintain accountability to SharkDAO, this proposal specifies a range of acceptable amounts.

  • ETH: 0-5 ETH
  • SHARK: 0-2,000,000 SHARK tokens

The amount decided will be published in a highly visible location.

The rationale behind this proposal (SIP-00034) is to ensure the coordinape test epoch and future iterations of coordinape have additional flexibility as the advisement landscape matures and influences decision making regarding DAO contribution incentives, finances, reimbursement etc.

Benefits

  • synth and dropnerd can better acknowledge and potentially integrate new advisement regarding reward amounts to contributors within the coordinape system

Risks

  • synth and dropnerd may go rogue and change the rewards to unfairly reward contributors too much or too little.

Off-Chain Vote

ALLOW Coordinape changes
32.55M 59.2%
DECLINE Coordinape changes
6.25M 11.4%
Abstain
16.21M 29.5%
Download mobile app to vote

Timeline

Oct 20, 2021Proposal created
Oct 20, 2021Proposal vote started
Oct 25, 2021Proposal vote ended
Oct 26, 2023Proposal updated