Closed GriffGreen closed 2 years ago
First I updated the side panel with the following:
Preview attached. Figma source https://www.figma.com/file/b6kx4mkaHxzq4TPzaI1eRY/TEC-Dapps?node-id=5109%3A6824
@marthendalnunes @GriffGreen Who else need to be tagged?
:-D Great! THIS LOOKS GREAT!!!
I have one minor copy edit and one placement edit
instead of:
"Add a proposal to experience the Conviction Voting"
It should be
"Add a proposal to experience your Conviction Voting Configuration"
And the Learn more and view chart links should be right under Conviction growth (the View Graph is tied to that param)
@divine-comedian any other thoughts?
Very Cool!
I would modify the text a bit.
First of all we don't want to cross terminology because we already submit "proposals" when we submit our commons config to github. I would substitute Proposal for Request and perhaps on the main page you could say "Simulate a Funding Request" or "Create Request" something along those lines
As for the questions in the following modal I would suggest:
`How much wxDAI is this simulated proposal requesting?
"How much wxDAI is in the Common Pool?" We could add a hover explainer if Common Pool isn't a clear term.. or make it link to the commons tribute forum post which has more info
-No changes on the third question
the other perhaps larger problem is getting users to contextualize effective supply, its hard to understand what a reasonable or realistic effective supply would be ... 10,000 TEC... 100,000 TEC ...
I don't know if there's a feasible way to make it relative to TEC minted for hatchers or relative to certain token supply benchmarks on the bonding curve.. some ideas to throw out there.
@GriffGreen @markoprljic
I made the editorial changes. https://www.figma.com/file/b6kx4mkaHxzq4TPzaI1eRY/TEC-Dapps?node-id=5109%3A6824
as per params meeting 31/10
we should add in a couple pieces of information to give third question some context:
~2 million TEC tokens will be minted at launch for Hatchers.
~130,000 TEC tokens will be minted from the intial buy-in and progressively distributed.
then lets make a clean default value that is auto-filled (but modifiable) of 1.5 million TEC tokens as the effective supply
@GriffGreen
I also tweaked the figma with some small clarifying pieces and attached some relevant tooltips for developer reference. I did not incorporate the above mentioned comments, maybe you had some ideas how to cleanly work those in @markoprljic
https://www.figma.com/file/b6kx4mkaHxzq4TPzaI1eRY/TEC-Dapps?node-id=7531%3A6443
Remove the 130k line!
Ideally it is as similar to the "add a step" feature in the bonding curve app as possible that way the user flows for both these features can build synergy.
Except we only have 1 question for them in the ABC.. and here we have 3 things to ask:
How much funding is the simulated proposal requesting? Requested Amount _____ wxDAI
How much wxDAI is being governed by Conviction Voting? Common Pool ___ wxDAI
How many TEC tokens are Actively Voting in Conviction Voting? Effective Supply ____ TEC
After they answer these 3 things, then we add that new Proposal (aka scenario) to the bottom of the List... We can cap it where ever it is reasonable.... but more is better ;-)