Community-oriented Sub.ID features - Batch one
Sub.ID Features Proposal: Collator and validator staking, Staking dashboard, Crowdloan claims, Cross-chain transfers
Launched a year ago, the Sub.ID web dapp was initially designed to provide quick and convenient access to all your Substrate addresses, balances and other assets in one place. It was built with the Dotsama ecosystem in mind and tailored to benefit its most active members. Since then, Sub.ID has been connected to over 30 Substrate chains, gained substantial traction, and got its own dedicated vision and roadmap.
We are seeking to secure funding from Kusama treasury for the following community-oriented features:
BATCH ONE
- Collator and validator staking: network selection, stake / unstake buttons and actions, collators / validators list, parachain / FRAME staking pallets support
- Staking dashboard: staking analytics, data aggregation, APR calculation, rewards calculation
- Crowdloan claims: claim buttons and actions, claim/vesting pallets support (backend/frontend), human friendly time to unlock staked tokens
- Cross-chain transfers: native & cross-chain transfers (UX/frontend), tokens pallets support (native transfer), XCM pallet integration, support of EVM tokens & transfers
BATCH TWO
- Alternative balance view
- Accounts grouping
- Transaction history
- P&L analytics
BATCH THREE
- Mobile app
The first allocation will only cover BATCH ONE features for now, the rest are our plans for the future.
Please review the full proposal with detailed description costs at https://docs.google.com/document/d/1RElvy5RYhnNInwnGsjibedGLI3EeBoqqazKk6Syv13M/view. We would love to get your feedback please.
Comments (1)
Super interesting! Keeping everything in equilibrium, I wonder if it would also be completely open-sourced and where precisely the dapp would sit, considering that the aim is to be fully decentralized and chain agnostic.
Yes, the code produced under this proposal will be open sourced under GNU GPL v3 license, as stated on page four. This refers to all the frontends of web and mobile apps, and SDK. Backend has to stay centralized for the time being because it's pretty heavy duty with its RPC connection to many nodes and related performance issues. Its functioning and evolution is maintained by the whole team, also mentioned in the proposal. We will continue looking for more decentralized solutions, one of which could be Substrate light client that connects directly to the networks. If included into the subsequent batches, we will definitely open source it as well.