📝 Brevis Improvement Proposal (BIP) Guidelines

Governance BIPs
1

This guide explains how to draft and submit a Brevis Improvement Proposal (BIP).

BIPs are the primary mechanism for proposing changes to the Brevis ProverNet protocol, including upgrades to governance, auction design, staking, and network parameters.

:bullseye: What is a BIP?

A Brevis Improvement Proposal (BIP) is a formal, structured proposal that introduces:

  • Protocol upgrades

  • Parameter changes

  • Economic or market design improvements

  • New features or integrations

BIPs are the foundation of transparent and community-driven governance.

:compass: BIP Lifecycle

Every BIP goes through the following stages:

1. :light_bulb: Idea (Pre-BIP)

  • Discuss your idea in Governance Discussion

  • Gather early feedback before formalizing

2. :memo: Draft

  • Submit your proposal in the BIPs → Draft category

  • Use the template below

  • Clearly define problem, solution, and impact

3. :magnifying_glass_tilted_left: Review

  • Community and contributors provide feedback

  • You may revise the proposal based on discussion

4. :ballot_box_with_ballot: Voting

  • Once mature, the proposal moves to Voting

  • Voting through * Snapshot.

5. :white_check_mark: Final / Implemented

  • If approved, the proposal is executed

  • Status updated to Accepted / Implemented

:pushpin: BIP Categories

When submitting a BIP, choose the appropriate type:

:gear: Protocol BIPs

  • Core system changes

  • zkVM / coprocessor / proof pipeline updates

:abacus: Economic BIPs

  • Auction design (TODA improvements)

  • Pricing mechanisms

  • Fee structures

:desktop_computer: Prover BIPs

  • Staking requirements

  • Delegation models

  • SLA and slashing rules

:bar_chart: Parameter BIPs

  • Adjustable system parameters (e.g. slashing %, fees, limits)

:globe_with_meridians: Ecosystem BIPs

  • Incentive programs

  • Integrations and standards

:brick: BIP Template

Please use the following structure when submitting a BIP:

Title

A short, descriptive title

Summary

A brief (2–3 sentences) overview of the proposal

Motivation

  • What problem does this solve?

  • Why is this important now?

Specification

Provide a clear and precise description of the proposed change.

Include:

  • Technical details (if applicable)

  • Parameters being changed

  • New mechanisms or logic

Rationale

Explain why this approach is chosen over alternatives.

Impact Analysis

Describe the expected effects on:

  • Provers (hardware, cost, SLA requirements)

  • Requesters / Applications (latency, cost, UX)

  • Network Economics (fees, incentives, token usage)

  • Security (attack surface, failure modes)

Implementation Plan

  • How will this be implemented?

  • Timeline / phases (if applicable)

Risks & Mitigations

  • What could go wrong?

  • How are risks mitigated?

Open Questions

  • Any unresolved points for discussion

:writing_hand: Writing Tips

Strong BIPs are:

  • Clear — easy to understand for both technical and non-technical readers

  • Specific — avoid vague or ambiguous proposals

  • Data-driven — include benchmarks, simulations, or reasoning where possible

  • Impact-aware — consider all stakeholders

:warning: Common Mistakes to Avoid

  • Skipping the discussion phase

  • Proposing without clear motivation

  • Ignoring economic or security implications

  • Overly vague specifications

:handshake: Collaboration

BIPs are not final at submission — they are living documents.

Authors are encouraged to:

  • Engage with feedback

  • Revise proposals

  • Collaborate with contributors

:rocket: Ready to Submit?

  1. Start with a discussion if your idea is early

  2. Draft your BIP using the template

  3. Post in the BIPs → Draft category