Skip to content

optimizing futarchy for least volatility  #237

@zack-bitcoin

Description

@zack-bitcoin

There has been debate in Amoveo about whether our futarchy markets for updates to Amoveo should optimize for the market cap or for the price of a VEO.

Spike offers up a third option of what we should optimize for. We should try to keep the volatility as low as possible.

The cost of making derivatives is proportional to how wide the margins are on those derivatives. The width of margins priced in VEO is mostly determined by how volatile VEO is.
So, if we want Amoveo to be a useful platform for derivatives, we should try to keep the volatility low.

We should come up with some ways of estimating the volatility, and make some graphs of it changing over time so we can visualize the situation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions