# Governance proposal template

This is a template for submitting proposals to Lista DAO governance for external parties.

## Proposal Structure

### Title:

\[A concise and descriptive title for the proposal]

### Date:

\[The date the proposal is being made, in the DD-MM-YYYY format]

### References:

\[Name of the external party’s Project]

\[External Project’s Whitepaper]

\[External Project’s Documentation]

\[Source code for the system(s) that interact with the proposed asset]

\[External Project’s Smart contract addresses]

\[List of Oracle data sources]

\[Audits both procedural and smart contract-focused]

\[Communities - social media links]

## Body Paragraphs:

### Summary:

A brief summary of the proposal; no more than 2-3 sentences

### Abstract:

Introduce and expand on the proposal. Touch on two main topics:

1. key points on how the proposal will improve Lista DAO’s platform & protocol performance.
2. What and how will the overall implementation process look like.

### Motivation:

What problems will this proposal address/solve? What’s the value-add? This section can have sub-sections for improved readability.

### Specification:

Provide a comprehensive description of the proposed change, including any relevant parameters or risk considerations. Comments on proposals should focus on technical aspects and specify any changes to be made. This section can include sub-sections for improved readability.

### Benefits (Pros):

List the benefits of implementing the proposal and how it will advance the protocol.

### Downside (Cons):

Identify any potential downsides to implementing the proposal.

### Voting:

Define what a “yes” and “no” vote entails.

#### Additional questions for collateral onboarding

1. Explain the positioning of the asset in the Lista DAO ecosystem. Why would it be a good collateral asset?
2. Provide a brief history of the project and the different components: DAO (is it live?), products (are they live?). How did it overcome some of the challenges it faced?
3. How is the asset currently used?
4. Token (& Protocol) permissions (minting) and upgradability. Is there a multisig? What can it do? Who are the signers?
5. Market data (Market Cap, 24h Volume, Volatility, Exchanges, Maturity)
6. Social channels data (Size of communities, activity on Github)
7. Contracts date of deployments, number of transactions, number of holders for tokens
8. List any possible oracle data sources for the proposed Collateral type.
9. (Optional) List any parties interested in taking part in liquidations for the proposed Collateral type.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bsc.lista.org/governance/lista/governance/governance-proposal-template.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.