Sponsors Dashboard - $SA 4M bounty!

[julian-molina]

This improvement requirement seem to be related to issue #3186

Business Requirement Overview

The Superalgos Project needs to become friendlier to people that wish to support the project by buying the native token.

At this point, sponsors buying the token face significant entry barriers to engaging with governance programs, which is the main form of engagement for parties not able to contribute in any other way.

They need to:

1. Open an account with Github;
2. Download and install the platform;
3. Spend several hours with the first few tutorials;
4. Create and learn to configure their profile on a UI and UX paradigm not optimized for non-technical people.

Ideally, sponsors should be able to engage with governance using a typical web interface that is intuitive and familiar to a regular Internet user.

The governance programs that concern sponsors are mostly the Liquidity, Staking, and Referrals programs.

The Dashboard

Features

1. Create profile and authenticate the associated wallet.
2. Deploy, edit, and delete the Staking Program and assign it a percentage of the total token power.
3. Deploy and delete the Liquidity Programs.
4. Deploy and delete the Referrals Program, add and delete referrers.
5. Contribute the profile.

Information Display

1. SA Tokens Balance in the account/wallet.
2. Commited token power (the token power that has been routed to the Staking Program or any other programs in the future).
3. Available token power (the token power that hasn't been routed yet).
4. The Liquidity Programs that have been deployed.
5. % of participation on each Liquidity Program.
6. Estimated Staking rewards for the current distribution.
7. Estimated Liquidity rewards for the current distribution.
8. List referrers.

Core Interests

Offer a decentralized solution, ideally running on users' premises.
Focus on lowering entry barriers with the best possible UX.
Focus on a first version that may be expanded in the future.

Implementation

I'll leave the implementation details for developers to specify. Some brainstorming in the Superalgos Develop Telegram group would be great, or comment here -- as you wish.

[julian-molina]

@harrellbm any chance the dashboard feature you are implementing as a generic tool may be leveraged to implement this particular dashboard?

[harrellbm]

@julian-molina This is definitely a possibility! The main thing to decide would be where we want this data to come from that doesn't require a lot of setup or steps. If the dashboard queries from a website to get some of the basic data more detailed things could be pulled in once a user sets up a profile or opens the governance workspace etc.

[julian-molina]

I'm offering a $SA 4M bounty for this improvement. Discussing definitions and implementation is the first task, to clearly define the scope of the bounty.

[MarkTradeink]

As I see it, the best practice for sponsors would be a DApp which can be access through a link in our website superalgos.org (but this isn't actually 100% decentralized as it depends on SA webservice instead the user machine itself)

The sponsor should just connect the wallet (MetaMask or similar) and a Nickname (to add to his user profile), then the process of creating a userprofile and contributing it to GitHub should run in the background. I imagine a window pop-up with loading a percentage bar and explaining that what action is currently being executed in the background.

Then from this interface the sponsor should have acces to what is mentioned in the first comment of this issue:

1. SA Tokens Balance in the account/wallet. (+ Buy Option SA Tokens from DEX)
2. Commited token power (the token power that has been routed to the Staking Program or any other programs in the future).
3. Available token power (the token power that hasn't been routed yet).
4. The Liquidity Programs that have been deployed.
5. % of participation on each Liquidity Program.
6. Estimated Staking rewards for the current distribution.
7. Estimated Liquidity rewards for the current distribution.
8. List referrers.

For a more decentralized option (running in a local machine) we can develop the Dashboard App. But we should provide a more non-technical apporach for installation and running the Dashboard.

[MarkTradeink]

Working on this Governance Dashboard (preview attached). Still looking how to get the necessary information, but it seems to me that we need to re-structure those modules to be available outside of the UI.

My idea behind the Governance Dashboard is a standalone solution which could be running without opening the Platform UI. That way you can have quick access all Governance related information.

This is what needs to be send to the Dashboards App:

• Users Information (User Profile, Wallet Account, SA Balance, TokenPower, etc.). Same information that we display at the governance Report Tab.
• SA Token information (Stacking, Liquidity Programs, Referrals Programs available)

Also we need access this existing functions from the Dashboard App:

• Access to Connect Web3 wallet function
• Access to Create UserProfile function
• Access to Contribute Profile function
  

[Luis-Fernando-Molina]

@MarkTradeink text me on Telegram if you need help / directions