Skip to main content

RaidGuild Improvement Proposals

A RIP is a RaidGuild Improvement Process or Proposal: a durable way to develop, fund, and record improvements to the Guild. RIPs may change operations, create shared tools, or fund internal work.

  1. Post the idea in Portal. Give people a readable starting point and explain the problem, beneficiaries, and intended outcome.
  2. Open discussion in Discord. Use the current RIP or governance space to invite objections, collaborators, and alternatives.
  3. Deliberate and negotiate. Refine scope, ownership, budget, success criteria, and any operating or security implications.
  4. Write the final RIP in GitHub. Use the RIPs repository as the durable artifact for the proposal members are actually evaluating.
  5. Submit the onchain proposal. Link the final RIP and make sure eligible voters know the vote is live.

Members are technically able to go directly onchain, but that does not remove the proposer’s responsibility to do due diligence and communicate. Voters should be skeptical of proposals that skipped socialization without a good reason.

A Strong RIP Includes​

  • the problem and why it matters now;
  • the proposed approach and alternatives considered;
  • owner or party, milestones, and expected deliverables;
  • budget, payment path, and any use of escrow;
  • risks, dependencies, and success criteria; and
  • links to the relevant Portal and Discord discussion.

Funding and Payment​

Define the release conditions before work begins. Smart Invoice or another escrow arrangement may be useful, but escrow is optional rather than a universal requirement. For paid contributors, follow the current RaidGuild LLC and payment requirements.

After delivery, bring the result back to the Roundtable or relevant steward space, record what shipped, and make the outcome easy to find from the GitHub RIP.

Ask Raida