Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
Treasury proposal: a statemint fungible asset explorer by OpenSquare
We believe all polkadot community members expect the parachains will boom the ecosystem, while fungible assets and DeFi maybe the most important part. We're looking forward some assets like USDT maybe issued on statemine, and we can also see some teams tried to issue some test assets on Rococo#statemint.
Then we need an explorer to check our history transfers, our issued asset lifecycle, learn some assets statistics, etc. StateScan is an explorer for it, and we began to develop it about 2 weeks ago. You can check https://test.statescan.io for our current development status. It's a development version link, but you can see current features it support. Generally they are asset list/detail, block/extrinsic/address detail. We are proposing a treasury spend to improve StateScan and so we can bring more features.
Work in this proposal
1. Unfinalized blocks and asset businesses handling
Currently we handle only finalized blocks. We have to handle the unfinalized ones to help user see the latest extrinsic status and some other unsettled businesses like the transfers.
2. Asset lifecycle
Here we record the create, issuance, mint, destroy events, and make the asset's lifecycle.
3. Make the site SSR
Currently the front site is made with create-react-app. We want to improve the user's experience with server side rendering and user don't have to see the initial spinner loading before the expected data.
4. Block/extrinsic/event list pages
5. Block/extrinsic/event/address/asset detail page create or polish
6. Asset statistics like holders trend, transfers amount/count trend, etc
7. Cross chain assets transfer records
8. Statemine implementation
Possible future work
- Identity scan and view. It depends on the statemint chain identity policy. We will scan the relay chain identity if statemint use the relay chain's identity.
- Assets price tracker and assets info(like icon, team, site) collect.
Time and cost
4 developers and 1 designer will work on this proposal, and we will request about 3 weeks equivalent cost. Cost list:
- 4 developers and 1 designer: $5000 * 4 + $3000 = $23,000
- Server fee: dotreasury will share the server for current stage, so $0.
So final cost is $23,000. We will calc the KSM count with the MA30 price at the onchain propose time if councilors have no problems.
Delivery
- Will release it to statescan.io continually.
- Will make it open source.
- Will try to finish the work in 6 weeks.
We are OpenSquare team, dedicated to facilitate the collaboration between projects and developers.
Comments (2)
This looks really useful (and necessary) to me. I'd just add two points:
Both of these touch on the same topic: we need to start thinking of multi-chain infrastructure and application development. For example, if we have Statemine, a governance parachain, a staking parachain, and an identity parachain, it does not make sense to look at them in isolation; if you want to display in a single UI that a particular identity has some assets, is a Council member, and stakes some KSM, then you need to think about these chains as members of a single network, and not isolated blockchains.
Thanks, Joe @29eda0999657482f9dd5efe01 .
Sure it's in plan. The No.7 work: cross chain assets transfer records. I haven't check the code very deeply, but heard from my partners there seems no very explicit events to mark the KSM/DOT teleports. We need to check the code more and may ask you questions.
Got it. Now it's in plan. We will implement it in next milestone. We can first read the identity from relay chain node as a workaround.
Agree! It will require more comprehensive design. From our point of view, really hope that the cross chain interactions will produce enough and explicit events/logs which will greatly reduce application developers' work to track what happens on chain.