Open mochet opened 2 years ago
I still think this description sort of lacks a vision. What is the role of this product? who is it for? what problem does it solve? If you want to get buyin from future contributors, I would try to formulate that very clearly. I am not saying this issue itself should be the pitch, you can do that in other places, but the essence of the vision that pitch serves as a foundation for that fits in very well here.
Even I who have discussed this question about the role of JSSv3 does not recall or properly understand where it is going, so you are well served reiterating this.
Previously we weren't concerned with the FM program at all, now that is the primary concern and we should aim to address that first and then build upon it with expanded views of on-chain data from the QN
Is this a wise goal, given that program will end August?
@bedeho
Is this a wise goal, given that program will end August?
Absolutely, we are suffering extremely from a lack of visibility. I get the timeframe with the FM program, however this is explored in consideration of that, in fact the design has been specifically chosen to solve that problem. I had drawn out plans for JSS in JSSv2 (https://github.com/Joystream/community-repo/issues/518) long, long ago but it is pure coincedence that the design of not only JSS but also the FM program match on enough common parameters and considerations that it only makes sense to go full blast with this, as strange as it may seem.
I would heavily suggest reading the section within this issue titled Value proposition
: https://github.com/Joystream/community-repo/issues/792
In particular this part:
There are very, very long term things in terms of value and functionality that this is all aiming to deliver upon extremely quickly. While we could wait for mainnet and delivery to make several of these things happen, the reality is that extensive knowledge of our DAO/runtime is quite limited. Instead of relying up on the few people who know this stuff well, I aim for us to give the answers ahead of time and put it out there before people even have to ask.
Even I who have discussed this question about the role of JSSv3 does not recall or properly understand where it is going, so you are well served reiterating this.
I did a run through of some Block Explorer projects and looked at how they showed information from either Polkadot mainnet or parachains and I think this effectively proves the value that can easily be obtained by JSSv3, with the following key points:
A) Polkadot recently was worth $30bn USD+, its currently worth $8bn USD. Either way here are the 3rd party tools available to understand Polkadot. When considering their valuation and potential resources, the views of on-chain data are not great.
B) Besides running public infrastructure, when it comes to interpreting our data it seems that no one else is going to fix this quick enough for it to be valuable.
C) We have already demonstrated better views of our DAO via Joystreamstats v1
and a Google Spreadsheet + charts than any available option (to the best of my awareness)
Reference link: https://nodle.subscan.io/extrinsic
Link: https://altair.subscan.io/council
Link: https://polkadot.subscan.io/bounty
very long time
to loadReference link: https://explorer.polkascan.io/
Reference link: https://dotscanner.com/polkadot/search
Reference link: https://polkastats.io/events
Initial Idea
What has changed
Related issues
Tooling
Quite a selection of possible tools were listed in this issue:
Limit of Scope
Basics
Issues in scope
Views