# MFER Dapp

The DAO manages and funds the future development of the MFER Dapp, which provides a view into everything related to the Fuckery Protocol.

It will generally be accessible but will have portions and actions that owners of an MFER iD can only use.

From a technical standpoint, the code and hosting are completely decentralized, open-source, and owned by the DAO.

This is a list of the pages that make up the MFER Dapp. Each page of the MFER Dapp includes a link to share the specific details in a preformatted Tweet.

### Every Epoch $MFER Distribution Summary

* Summary of all epochs, blocks produced, ADA rewarded, treasury/reserve split all time, countdown until next epoch, how much $MFER distributed next epoch
* Table of all epochs with delegators, ADA staked, blocks produced, ADA rewarded, treasury/reserve split, USD at time

### Single Epoch $MFER Distribution Summary

* Summary of epoch (same as total summary of all epochs)
* Table of each distribution linked to the Membership NFT Token

### Current Reserve/Treasury Statistics

* Summary of Reserve ADA, Treasury ADA, current USD of both, total $MFER in circulation
* List of actual wallet addresses with Cardano scan links
* Graphs for ADA over time for Reserve/Treasury
* Graphs for USD over time for Reserve/Treasury
* $MFER burn/redemption limits by the community as a whole before it locks up for all
* Organization multi-sig wallets and contents

### Global Smart Contract Function Log

* Real-time flow of every smart contract function being executed (distribute, burn, exchange) with filters and searching, ADA received/distributed
* Filtering by date, type of function, amount greater than

### Your $MFER Statistics

* Current $MFER holding, estimated $MFER distribution next epoch with % of total, countdown until next $MFER distribution, your $MFER burn cooldown, your $MFER burn amount possible
* Voting Stats: Times Voted, $MFER voted with
  * Table of actual votes that's a copy of the&#x20;
* Current Staking Status
* Claim $MFER
  * UI for Distribute SC
* Burn $MFER&#x20;
  * UI for Burn SC
* Links for
  * Instructions on staking in our pool
  * Cardano pool statistic websites

### $MFER Holders

* Summary of total holders (wallets), total membership NFTs
* See total ART/TECH/DEGEN/UNDECIDED breakdown, same ART/TECH breakdown within each Organization
* List of all $MFER holders with filters and searching + membership NFT linked
  * PFP, Name, Address, $MFER, % of supply, Twitter, Discord, Trust, Organization, Art/Tech/Degen

### Proposals

* Summary of total number of proposals, number of votes, number of unique voters, total preparing/active/passed/failed
* List of proposals with current status, backing organization, votes for, votes against, total votes, total $MFER voted, % of supply voted
  * Filters and searching

### View Proposal

* Stats for proposal included in the List
* Voting Ends countdown (if applicable)
* Timeline of Progression of the Proposal
* Line graph of voting over time with For/Against/Abstain with Quorum needed line

### Governance Options

* List of all active Governance Options with current values
* History of their values, last updated, exact changes, and associated proposals.

### Mint and Update MFER iD

* Mint
* Customize
* Update available options
* View other options set by smart contracts

### UI for Exchange smart contract function

* Accepts $MFER on behalf of any network participant using an API (pay-in address), a microapp (ex: NMKR Pay), or the MFER Dapp (custom-link to UI)

### Global Navigation and Authentication

* Persistent showing of PFP from MFER iD

### Discourse for Proposals

* Replaces House of Mfers
* Custom Authentication with MFER iD


---

# 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.oldmoney.io/mfer/mfer-dao/mfer-dapp.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.
