Please add the following question/answer to the FAQ section, after the "Who can participate in voting on EOS WPS proposals?" question:

Q: How much work can be expected to get a proposal funded?
A: Data from other WPS shows that a lot of work is required to get a proposal funded. It is up to the proposer to seek and obtain votes on the proposal. The network does not provide guidance, nor guarantee, as to how to get funded.

Please update the answer for the "Is the 100 EOS fee ever refunded?" question as follows:

No, the fee is non-refundable once the proposal has been published. However, during the draft period of a proposal, the deposit of 100 EOS can be refunded.

If you include an image in the description using the included insert image feature in the formatting options, you get an "overview can't be empty" error when you attempt to submit the description.

When a user executes claim , there's no pop-up/chip appearing to show it was successful transaction.

It would be helpful if the UI could show how much was claimed.

The claim amount can be pre-calculated by applying a delta from that proposal:

proposals::payouts - proposals::claimed = expected claim return

Add a language toggle, and ideally automatically detect the user’s language and present the UI in the appropriate language.

Support for English, Chinese and Korean only for now. We can provide Chinese and Korean translation of “about” content and all UI elements.

Allows the proposer to post metadata about themselves:

metadata_json (example)

• name
• description
• website
• telegram
• wechat

TABLE proposers

params

• {name} proposer - proposer of proposal
• {map<name, string>} metadata_json - a sorted container of <key, value>

example

{
  "proposer": "myaccount",
  "metadata_json": [
    { "key": "region", "value": "global" }
  ]
}

ACTION setproposer

Set proposer's metadata

• authority: proposer
• ram_payer: proposer

params

• {name} proposer - proposer of proposal
• {map<name, string>} metadata_json - a sorted container of <key, value>

example

cleos push action eosio.wps setproposer '["myaccount", [{"key":"region", value":"global"}]]' -p myaccount

Display a countdown of the number of days remaining in the period at the top of the page

This is a nice-to-have enhancement request

The list view of Active Proposals should enable you to see many proposals at the same time without scrolling. The cards for proposals in list view are currently tall, containing a lot of vertical blank space, limiting the number of proposals that can be viewed at once.

Reduce the vertical space used by proposals in list view, and the space between them, similar to how they appear in DASH Nexus.
nice-to-have: allow the cards to be expanded to display additional info and a graph of votes over time.

See example:

Currently users are prompted to sign in as soon as they land on the website. They're not able to browse the proposals until they sign in or dismiss the prompt in Scatter.

Users should only be prompted to sign in when clicking the sign in button or attempt to take some action that requires they are signed in.

Users should be able to browse proposals without being interrupted.

To help further discussion, would be ideal to have the proposer be able to include in the draft::metadata_json:

• Slack
• Telegram
• WeChat

That way those discussion channels are "authoritative" groups created by the proposer.

Consider using the transit API, which includes support for many different EOS wallets:
https://github.com/eosnewyork/eos-transit

They don't support EOS Authenticator (B1's iOS wallet), which would be a good additional wallet to support.

Change proposal status heading:

Paid proposals -> Passing proposals

Unpaid proposals -> Not meeting threshold

Check eligible proposer (disable submitdraft & activate)

This check prevents proposer to also be voter

EOS-Nation/eos-wps@9552d86

Using the Upvote/Abstain/Downvote actions with a non-BP (or BP but not paid) account gives an "Unexpected error" message. I could see this being confusing for people that aren't aware that only paid BPs can vote.

Add a way to view old proposals from previous periods

(nice-to-have - not urgent)

Please update the "Voting periods and funding" section as follows:

A maximum budget of 50,000 EOS will be made available for each 30-day voting period. The period budget and duration are settings within the WPS smart contract that can be adjusted by MSIG approval from 15 of the top 21 Block Producers.

eosio.wps is funded from the fees accumulated in the eosio.names and eosio.ramfee accounts prior to the deployment of REX. Prior to REX, these accounts accumulated roughly 3.5 million EOS from EOS premium name auctions and RAM purchase fees. An MSIG approval from 15 of the top 21 Block Producers is required to move those funds to eosio.wps.

Any on-going fees being collected by eosio.names & eosio.ramfee will continue to flow to REX holders and shall not be transferred to eosio.wps. Funds flowing into REX will not be affected by this proposal.

We’ll propose to transfer 50,000 EOS, or two periods worth, to the eosio.wps account upon activation of the EOS WPS system. We’ll propose a top-up of another 25,000 EOS one month ahead of each period. This gives the top 21 the flexibility to discontinue the WPS system at any time by simply not funding it.

It would be nice if there was some way to see who is voting for a particular proposal

The video URL I provided in the "setup" step of the proposal doesn't appear anywhere on the proposal for those viewing it.

Feature comment

If we could add a discussion/comments section to the UI with the following features:

• create/modify/delete comment
• only eligible accounts can comment:
  • proposer
  • voters (eligible BPs)
• show all comments per single proposal ordered by date
  • table => comments
  • scope => proposal_name
  • multi-index (by timestamp) => index_position = 2
• comment_json schema can be very simple initially:
  • { "key": "text", "value": "my comment" }

Note: Accounts can only comment once per proposal, however, they can edit/delete their comment during the proposal's active status.

ACTION comment

• authority: account
• ram_payer: account

params

• {name} account - account name
• {name} proposal_name - proposal name
• {map<name, string>} metadata_json - a sorted container of <key, value>

example

# create/modify comment
cleos push action eosio.wps comment '["myaccount", "myproposal", [{ "key": "text", "value": "my comment" }]]' -p myaccount

# delete comment
cleos push action eosio.wps comment '["myaccount", "myproposal", []]' -p myaccount

TABLE comments

• scope: proposal_name
• ram_payer: account

multi-indexes

params

• {name} account - account name
• {time_point_sec} timestamp - last time created/modified
• {uint16_t} version - version number
• {map<name, string>} metadata_json - a sorted container of <key, value>

example

{
  "account": "myaccount",
  "timestamp": "2020-03-26T12:00:00",
  "version": 0,
  "metadata_json": [
    { "key": "text", "value": "my comment" }
  ]
}