# Proposal Guide

**The italicized text below describes how each section should be filled out. Proposals should be comprehensive, specific, and readable. Sections can be added and removed as needed.**

```
Title: *Proposal title*
Author: *Author name*
Date: *Creation date YYYY-MM-DD*
```

## Thesis:

*A one-sentence overview of your proposal.*

## Abstract:

*A short and human-readable version of the specification section. Someone should be able to read only the abstract to get the gist of what this proposal does.*

## Motivation:

*Should clearly explain why the existing process/specification is inadequate to address the problem that this proposal solves.*

## Risks:

*Security implications/considerations relevant to the proposed change.*

## Specification:

*Specific actions that must be taken by the multisig or DAO members. This section should be comprehensive.*

## Rationale:

*Justification for the specification section.*

## Timeline:

*Specification timeline. Include Funding Cycle for Juicebox reconfigurations.*

## Copyright Disclaimer:

*All proposals must be in the public domain.*

Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).