List view
- Due by December 30, 2022•14/14 issues closed
- No due date•26/26 issues closed
- No due date•16/16 issues closed
Let's get to 80% coverage
No due date•19/19 issues closedAll issues to be solved for a release candidate.
No due date•58/58 issues closedAll issues to be solved for sunsetting v3.
No due date•14/14 issues closedIssues for V4. Main goals: -Better IDOs -Balancer V2 -Improve fee flexibility The big split https://github.com/oceanprotocol/multi-repo-issue/issues/59
Due by February 20, 2022•193/193 issues closedHere are the features that will not be present in the first cut of V4
No due date- No due date•17/17 issues closed
https://github.com/oceanprotocol/multi-repo-issue/issues/91
No due date•5/5 issues closedOne interface to rule all chains. https://github.com/oceanprotocol/multi-repo-issue/issues/67
No due date•30/30 issues closedAll of `ddo.price` will be deprecated in the future. In last weeks we already removed our reliability in market on `ddo.price` values. E.g. on the asset details page users will always see all numbers coming from The Graph query in the end. There some remaining places where we rely on `ddo.price.value` or `ddo.price.type`: - `AssetTeaser.tsx` - all aquarius queries based on liquidity & price, e.g. highest liquidity list on front page, search results - `ddo.price.type`: deciding tabs on asset details - properly fetch price in `useAsset` without `ddo.price.type` - we need a new component for `Highest Liquidity` were we show the top 9 assets, but there will be no `All data sets with pool` button. The visual component stays the same, we need to construct the data. We can fetch the pools from the graph and then for each pool fetch the ddo and create a list of ddos.
No due date•6/6 issues closed- No due date•59/59 issues closed