Welcome to the Euler Governance Forum


This forum is dedicated to discussions on Euler governance. Relevant topics include:

  • Governance proposals
  • Proposal discussions
  • Site feedback
  • Risk assessments

This is not the place for:

  • EUL price discussion
  • Generic Euler discussion
  • Euler support requests
  • Off-topic conversations

If you need technical help, or want a place for more general discussion, visit the official Euler Discord .

Common Questions


Below, we have provided a template on how to structure your Euler proposals in order to offer a more comprehensive & efficient deliberation process.

Governance Process

1.[RFC] Request for Comment

The [RFC] is the first step in creating a governance proposal. Make sure it’s well-formulated, be proactive with the community and be open to suggestions.

2.Governance Proposal

If the [RFC] is well-formulated and the community has a clear understanding of the proposal and supports your [RFC], it will be moved by a mod to the governance category as an eIP: Euler Improvement Proposal.
Please note that it usually takes a week (7 days) for a proposal to be moved from RFC to the eIP stage.
Once an eIP has been assigned, the proposal can then be created on Snapshot or Tally using this eIP.

Snapshot allows for off-chain “gas-less” voting while Tally allows for on-chain voting which will incur transaction gas fees. Snapshot is mainly used to determine the support for a potential on-chain proposal, or to create proposals that do not necessarily interact with the protocols smart contracts but can be used to help the Euler foundation make decisions on other subject matters or perform actions on behalf of the community, e.g., issue a grant, or pay a bill, for example. Thus mainly used to aid Euler in making difficult decisions in collaboration with the community.


A snapshot vote does not always need to be posted by the original eIP author, it can be posted by someone else or by the core team in case the minimum threshold of EUL is not being met.

A Snapshot should always have the link to the eIP attached. The parameters of the poll (Yes, No, different options for values) need to mirror the options discussed in the eIP.

Please see the Euler governance documentation describing how to create a proposal and vote on Snapshot.


Please see the Euler governance documentation describing how to create a proposal and vote on Tally.


Proposals that are rejected due to invalidity or insufficient support can be resubmitted. Approved proposals with sufficient support via governance/voting will be implemented by the Euler Foundation.

Proposal Structure

  • Title: [Enter Proposal Title]
  • Author(s): [enter name(s) of associated authors]
  • Related Discussions: [paste link here]
  • Submission Date: [Enter Date]

Body Paragraphs:

  • Simple Summary: Give the community a TL;DR on your proposal; no more than 2-3 sentences.
  • Abstract: Introduce and expand on the proposal. Highlight key points on how the proposal will improve stakeholder/token holder experience, protocol performance, and the overall implementation process.
  • Motivation: What problems will this proposal address/solve? What’s the value-add?
  • Specification & Implementation: Present the implementation of the proposal and answer key relevant question to the protocol
  • Voting: Define what a “yes” and “no” vote entails. If there are any Snapshot votes or forum polls associated with this proposal, please attach them.

Example of a proposal draft:

A good governance proposal example can be found here: eIP: Promote WBTC to collateral tier.

Stay updated by subscribing to the community newsletter and follow the Twitter Page!


A small step for Euler, A big step for defi and web3!