V2.alpha to 2.x roadmap

[janklimo]

🚗 V2.alpha to 2.x roadmap

As discussed in the scrum call, this aims to be a very specific list of objectives that need to be met for specific UI release milestones.

V2.alpha – community release (Apr 1st)

Intended to offer a core set of features to be tested by our loyal users to provide feedback on.

pf-core

• Fix data issues in pf-core, issues 100 and 104.
• Add pool IDs to API response
• Fix user model, issue 154

UI

• Dark and light theme
• Fix any missing/ugly icons
• Transaction flow animations from fennec
• Token approval
• Jar deposit
• Jar withdrawal
• pToken approval
• Stake
• Unstake
• Harvest pickles (farm)
  • Apply the same flow to the harvest pickles modal on the dashboard
• Lock dill
• Extend dill lock
• Harvest pickles (dill)

V2 – public release (TBD)

With this release V2 becomes the default landing page with the option to visit V1. Feature-freeze of V1.

• CowSwap
• Finalize dual distribution
• Make themes look good
  • Persist themes when reloading the page
• Update routing to make V2 the default, add a link to go back to V1
• Voting
• Non-standard jars
  • UniV3 jars
  • B.Protocol
  • Withdraw-only jars
  • Balancer
• Get Mark's help on the final design touches. Voting, stats, farm details are too freestyle.

V2.1 – follow-up release(s)

• Zaps
• Disabled/inactive jars (with filter)
• Depositing native assets (see Add cronos to UI #393)
• Fix connectors on sidechains (using @web3-react v8)
• Brinery, Brinery Pools, & Brinery Jars (Add Brinery flow to UIv2 #461)

[larrythecucumber321]

Thanks for the amazingly detailed checklist @janklimo 👏

The items below are all for V2 - public release....

Amongst the list of Non-standard jars for the public release, I would include:

• Balancer timed-withdrawal jars
• Withdraw-only jars
• Disabled jars (which currently exist in the 'Inactive Jars' section of the UI)
• Depositing native assets, as done in Add cronos to UI #393

Under Voting, we can further chunk those tasks into

• Voting interaction
• Vote distribution chart

Not currently in production, but the FXS locking feature being developed in #191 wil need to be ported to V2.

That's all I can think of for now, but will add to this when/if other items come to me!

[manymoneymanny]

From Sprint planning, items to fix before release:

• remove "compounding" indicator.
• add /dill/vote page navigation
• add $PICKLE marketcap and total supply under price indicator or on hover
• add APY breakdown on hover
• add APY breakdown on details

[manymoneymanny]

• add /dill/vote page navigation

@bcstryker this one should be yours

[janklimo]

opened #469 and #470

[janklimo]

@mannyreimi88 or @bcstryker can you please add tickets for these?

[manymoneymanny]

testing DILL page today @janklimo:

some observations / suggestions:

• add the $PICKLE balance in-wallet and the $PICKLEs locked in the current $DILL lock (and maybe their worth in $) so it's easy to grasp if I need to lock anything.

• may need buttons to refresh balances in modals, this is because I am sure my balance changed while the page was already loaded but I had to refresh the whole page as when I clicked the modal by balance was zero.

• increase_amount() call failed: https://etherscan.io/tx/0x75d57d3c1c9d45baa98f89bacf79b35b34635f15f8f1b3958ec1fb892795e92b
• extend lock modal opens and default state seems there's a visual bug.

• I was unsure whether I was extending lock for the max amount or not.

• extend lock transaction couldn't be even relayed

• gas estimates were off throughout

• more indicators are needed in the revenue distribution stats element

[janklimo]

Thanks for testing this @mannyreimi88 very good points. @larrythecucumber321 I looked at the timestamp we pass to the increase lock transaction and it's 346 years into the future 😅 can you help fix some of these?

[manymoneymanny]

another cosmetic improvement would be if the "pie chart" image here we could use the "identicons" by Dan Finlay that are very classic to Ethereum https://www.npmjs.com/package/ethereum-identicon

[larrythecucumber321]

@janklimo I'll take care of these.

@mannyreimi88 Strange, I had no problems with these transactions testing myself just now... (see below). I have no idea how the increase lock transaction tried locking so far into the future, never seen that happen but I can investigate. Lastly, the failure to submit the transaction is a MetaMask issue.

I can implement your other enhancements no problem. Can you transfer these onto an issue and a card on the project board please?

[manymoneymanny]

@larrythecucumber321 here you go #443