# MVP Docs - DEPRECATED, goto https://coda.io/d/MVP-Docs_d22tYRigXES/MVP-Docs_suQHn#_lu1yL

This document describes the design and functionalities of Ordum per the user journey and features.

Polkadot's public good grants aggregator: Main Functionalities
---

- Simplifying grant applications (we believe that optimised UX and centralised documentation can bring more builders to the industry as a whole).

- Enhancing decision making of token holders (protocols) and foundations (centralised entities) through data aggregation.

- Improving accountability through milestone reporting UIs

---
**Docs**:

- [Ordum full graph](https://https://www.figma.com/file/I59Xvuv1jcF583ig7UFSbN/Ordum-User-Journey-V2?type=whiteboard&node-id=0%3A1&t=ghNeiQGymiPdXD6U-1)
- [MVP UI Design ](https://www.figma.com/file/UUiI6usGHEWnTLPEZ9rDRD/Ordum-UI-V2?type=design&node-id=395%3A58206&mode=design&t=Kyu7E3Zu8VOmtxaQ-1)- split into pages with the design system and UI

---

[Go to Section](#Process:-Wallet-sign-up-/-Sign-in)

# Process: Wallet sign up / Sign in

### **🔥 Sign up**
---

Before using Ordum, an individual has to sign up for an account with a wallet. This is common practice in the blockchain industry. In the future we will add email sign ups as an option, as well as information on how to set up a wallet. Further details about Polkadot wallets can be found [here](https://wiki.polkadot.network/docs/wallets-and-extensions).

### **1. Connect Wallet**

The user can choose which wallet they would like to connect with.

- [Talisman ](https://docs.talisman.xyz/talisman/build-the-paraverse/developer-resources)
- [Polkadot JS](https://polkadot.js.org/docs/)
- [Nova Wallet](https://docs.novawallet.io/nova-wallet-wiki/misc/developer-documentation/intergrate-nova-wallet) via [Wallet Connect](https://docs.walletconnect.com/) (Mobile wallet)

Once the user chooses a wallet, a browser extension should prompt them to authorise the connection.

Note that Wallet Connect CTA will display a QR code for the user to scan and connect via mobile. An example from [HydraDX app](https://app.hydradx.io/trade) is below:


The MVP would just have the QR code option, while the desktop one would come in later.

### 2. Select account

The user can select which account to sign up with, as they may have multiple addresses.


Wallect Connect will allow the user to connect with the wallet of their preference and this will be done in the app, so no need for a native UI.

When the user connects an account with Ordum, the UI will prompt them to fill out information for their [Personal Profile](#Personal-Profile).

### 🔥 Sign in
---

The process for "signing in" is very similar to [signing up](#Process:-Wallet-sign-up-/-Sign-in):

1. Connect Wallet
2. The UI should recognise the address / account that the user has previously created a profile with
3. The user chooses the address and logs in
4. Lands on "Explore Grants"


---

**Denis add tech spec**

---

# Features

After the user connects a wallet, they are prompted to create a `Personal Profile`


## Personal Profile

### Create Personal Profile

- Username (Required) | @Kpymmwb5QNSqSBSqAwgAlA can you write the details re on-chain identity
- Bio
- Profile Picture. Imported from a wallet (graphic address representation) as default and give an opportunity to upload a picture, which will be compressed to some sane ratio on our side.
- Cover image. Something default, maybe a choice of random. Give an opportunity to upload a picture, which will be compressed to some sane ratio on our side. @Kpymmwb5QNSqSBSqAwgAlA Default can just be black?
- Role (eg. designer, front end dev...)
- Links

**Denis add tech spec**


### Personal Profile


**The Personal profile consists of:**

- User entered information (Username, Roles, Bio, Links, Profile picture, Cover image)
- Teams the individual is part of (images of the participating team and CTA: `view all`)
- Total funding received (data pulled from various blockchains, for the MVP it will only be Kusama)
- Number of applications (data pulled from various blockchains, for the MVP it will only be Kusama)
- `Edit profile` CTA for the user to edit the profile

The `teams` section can be expanded with `view all` as per the page below:


The tags contain the `role` which the individual has in a `team`.

> Denis: if we allow users to register several addresses to their profile, which of them will have a `role`? Or do you want to have all of them displayed in two ways (as an Ordum username and a registrar/address)? That would make sense in terms of recognition, search, statistics, showing as a team member, etc. But this is something only Ordum website haz, so not compatible with other platforms. @Kpymmwb5QNSqSBSqAwgAlA If the user has multiple accounts registered, then the same role is attributed to all of the addresses. My implication is that the user can have as many addresses tied to their account as they want, but the information on their personal profile remains the same for every single address. But we don't have multiple addresses for the mvpThe `"role"` is there just so that other users can see what a person does/is professionally, as in individual or part of a team.

## Components: Navigation and Dashboard

--> Empty dashboard


--> Dashboard with drafts (proposal, milestone, report)

### **Navigation**
---
**Top navigation bar:**

- Back button when required

> Denis: when required? @Kpymmwb5QNSqSBSqAwgAlA there are examples in the designs when it is required. I can't state the instances here as I am not a 100% sure where these will appear in the future. Can make a list of these from the designs if required, let me know.

- [Personal Profile](#Personal-Profile)

> Denis: `delete account` option should only be in the personal account, otherwise it's easy to misclick (and also too tempting lol).
> therefore I believe let's not have that `cog` button and just a profile button (changed when there's a profile image) with `log out` and `profile options`.

### Settings


`Settings` are currently just a drop down with 2 CTAs:

- Log out (takes the user back to the login/sign up screen and logs out)
- Delete account (opens a pop up which asks the user to confirm. If they do their account is deleted).

> Denis: I'd suggest for that confirmation do like github does for irreversible actions: form (maybe doesn't accept paste) asks to enter the name of the account to confirm the action.
@Kpymmwb5QNSqSBSqAwgAlA do we also add this for deleting team accounts?
---

#### Side navigation bar

- My grants (further details in the `dashboards` section)
- Teams (further details in the `dashboards` section)
- Explore Grants/Foundations

### Dashboards

Consists of side navigation bar CTAs:

**My grants (only consists of `drafts` for the MVP)**:


- **My grants / Drafts**
- Types of `drafts` : Proposals, Milestones, Reports
- The name of the grant provider
- Last edit of a proposal
- Which team they submitted for (may also be an individual profile)
- Delete draft

---> more on proposals in the section "Apply for a grant"


- **Teams** (shows the teams that the individual is part of), with CTAs:
- Manage teams
- View (team) profile
- If the user is an "owner" of the account, they are able to delete the team.

---

### Create Team


Any individual can create a team and invite members via links. They will need to be careful with sharing these are for the MVP they can be reused by anyone.

> Denis: nah it may be just a link generated specifically for an address @TriplEight , as in wallet address?

The team and its members can be later added or removed from submitted proposals.

**Fields**

- Team name (required)

> Denis: same entity as a profile name - won't be compaptible with the other platforms. This suggests me a couple ideas:
> 1. the team **must** be created together with an address so it's tied to something onchain. (this requires some UX decisions such as: probably it should be multi-sig by default, then we need an interface fer dat)
> 2. it's still possible (also compatible with personal profiles' names) to create a not-confirmed-by-registrar account with an onchain name. This might be good enough for us (disclaimers and info messages apply).

@Kpymmwb5QNSqSBSqAwgAlA as we decided on the call; we leave this as is? Where the users can create teams and add names, but when they submit proposals the teams names get tied to an address?

- About
- Project type(these tags will be expanded as conversations with Polkassembly, Subsquare and Web3 Foundation progress. We all want to define a unified standard)| multiple fields can be added:

- DeFi
- Identity
- Privacy
- Infrastructure
- Network Changes
- Art
- Media
- Gaming
- Events
- Governance
- Education
- NFTs
- Translations
- dApps
- Other

- Blockchain | multiple fields can be added:

- Kusama
* Polkadot
* Phala
* Aleph Zero
* Basilisk
* HydraDX
* Basilisk
* Astar
* Subsocial
* Zeitgeist
* Interlay
* Ethereum
* Near
* KILT
* Aventus
* Bifrost
* Composable Finance
* Picasso
* Equilibrium
* Frequency
* Centrifuge
* Darwinia
* Ajuna
* Parallel
* Pendulum
* Moonbeam
* Unique Network
* Altair
* GM
* Inbue
* Moonriver
* Robonomics
* Touring
* Sora
* Kintsugi
* Other

> Denis: how do we expect to auto*-update these tags? based on inputs in `Other`? @Kpymmwb5QNSqSBSqAwgAlA to be honest, right now I have no idea. We will probably have to have a researcher that just collects and analyses such things for us and maintains it. Ideally we just add tags as we onboard more foundations and what is submitted under "other".

- Links:

- Email
- Discord Handle
- Element Handle
- Twitter Handle
- Website / Portfolio
- Github


---

**Denis add tech spec**

---

### Admin settings for "Manage Teams"


**Owner(individual which creates the team)**

- Manage Team Public Profile
* Add Team members via link
* Remove Team members
* Manage team member's permissions
- Submit reports
- Edit proposals
- Submit proposals
* Transfering ownership of the team
* Delete Team Account

**Member:**

* Submit proposals
* Edit proposals
* Submit reports

--> Remove functionality allows "Owners" to remove any members in the team.

---

**Adding members**

- via generated invite links


---

**Denis add tech spec**

---

## Team profile

The team profile consists of 3 sections:

### Summary

- About (input by the team owner)
- Links (input by the team owner)

### Activity

- Open grants (includes accepted grants)
- Closed grants (includes grants which contain all submitted reports and have been completed)

### Team


- list of team members
- CTAs to team member's personal profiles

---

**The team profile draws data from:**

- the inputs of the user
- blockchains which will be indexed on the platform. For the MVP it will only show data from the Kusama Blockchain.

**Breakdown of data aggregation:**

- **Chains** User input
- **Project Type** User input
- **Funding received** Kusama Blockchain ([worth checking these guys' APIs](https://kusama.dotreasury.com/#/))
- **No of applications** Kusama Blockchains (number of proposal submitted associated with this team account, shall we ask the individual to connect a wallet to the team account? Or a multi sig?)

---

### Explore Grants


Through this page the user can explore grants listed on Ordum. For the MVP we aim to have the Kusama Treasury fully mapped out with a designated profile, while other grants will only have links to their programs so that the platform aggregates all [active programs](https://docs.google.com/spreadsheets/d/16AsQiqhuIbKM2aA4ZZzQma_lqw28zyibyiVltHqabZA/edit?usp=sharing) in the Polkadot ecosystem.

**Filtering**

- Grants range (min-max amount in USD)
- Project type (filtered by tags for projects)


- Grant Type (on-chain and off-chain grants)--> this will be expanded on soon.
- Activity (Active or closed. For now these will all be active but we anticipate some of them to close eventually).

---

## Kusama Treasury Profile


When the user reaches the Kusama Treasury, the side nav expands to show different application tracks in [OpenGov](https://guide.kusama.network/docs/learn-polkadot-opengov/). While there are more tracks which also include network upgrades, as well as a mechanism called "tips" our current design only focuses on:

- **Overview** (Treasury/Foundation Profile)
- **Discussions** (This will be only a placeholder with a [link](https://kusama.polkassembly.io/discussions) to the discussions on Polkassembly)
- **Treasurer** (The origin for spending funds from the treasury, up to 333333.33 KSM).


- **Big Spender** (Origin able to spend up to 33333.33 KSM from the treasury at once.)


- **Medium Spender** (Origin able to spend up to 3333.33 KSM from the treasury at once.)


- **Small Spender** (Origin able to spend up to 333.33 KSM from the treasury at once.)


The user can browse through different proposals submitted per track. These should be fetched with existing APIs from Subsquare, Subscan or Polkassembly.

**Each proposal card has a CTA to view the proposal itself. There will be two types of proposals to view:**

- Proposals fetched via APIs which come from Polkassembly or Subsquare (third party proposals)

- Proposals submitted via Ordum (native proposals)

> Denis: I do not believe we should have this distinction. Why should we have it? @Kpymmwb5QNSqSBSqAwgAlA Because they won't look the same if submitted via us, subsquare and PA, PJS. So this must to remain.

These types of proposals will differ in the UI.

### Third Party Proposals


**The proposals should include:**

1. Proposal Title
2. Highlighted metadata from the chain
- Who the proposal is by
- The beneficiary account
- Bond (which account placed the bond for the proposal)
- Submission Deposit (which account placed the submission Deposit)

> Denis: due to these fields' data is rather long, I'd say let's have them vertical rather than in line. Maybe as a table. @Kpymmwb5QNSqSBSqAwgAlA Right now I don't know where to add it or what space is more optimal right now. Maybe after the mvp, does not seem like a priority.

3. When the proposal was posted to the chain
4. Requested amount in KSM
5. The text which was added to the third party platform
6. Links to the original posts on Polkassembly and Subsquare in the tabs on top
7. Code - which is metadata from the chain


The `code` page includes:

- Title
- Metadata highlights
- Tabs
- The proposer
- Submitted (requested amount)
- Decision deposit amount in KSM
- Origin
- Enactment After
- Submissions Deposit in KSM
- Deciding since (date and block)
- Proposal Hash
- Section
- Description

At the bottom of the page, the user can see the table and the JSON files in tabs:


---

### Native Proposals

`Native Proposals` are defined by the "Apply for a grant" user journey (more on these further down the line).

Below is a breakdown:


**The proposals should include:**

**Summary:**

1. Proposal Title
2. Highlighted metadata from the chain
- Who the proposal is by
- The beneficiary account
- Bond (which account placed the bond for the proposal)--> if these have not been added anyone can add the amount via CTA
- Submission Deposit (which account placed the submission Deposit) --> if these have not been added anyone can add the amount via CTA

3. When the proposal was posted to the chain
4. Requested amount in KSM
5. Text from the "Short Description" Section in the proposal submission
6. "External links" which the user can add in the submissions UI
7. "Project type" - tags which the user can add in the submissions UI
8. "Contact" which the user can add in the submissions UI
9. "Start date" The day when the user should receive the grant if the proposal passes
10. "Deadline" which is calculated based on their last milestone delivery as set in the "proposal submission" UI
11. "View metadata" - which is metadata from the chain


12. "Edit" CTA where the user can open their proposal and make changes.

"View metadata" page is the same as "third party proposals" "code" section, it includes:

- Navigation includes back button to the "summary" page.
- Title
- Metadata highlights
- Initial proposal tabs
- The proposer
- Submitted (requested amount)
- Decision deposit amount in KSM
- Origin
- Enactment After
- Submissions Deposit in KSM
- Deciding since (date and block)
- Proposal Hash
- Section
- Description

At the bottom of the page, the user can see the table and the JSON files in tabs:


---

### The Proposal

"The Proposal" Section is another step in the proposal submission where the user writes their proposal via text editor. There is a template in the editor which can be edited. The user can also add images, links and tables which would appear here.

---
### Team


The "Team" tab contains information of all the added team members to the proposal. These may have their own profiles on Ordum(contain CTAs to profiles) or just descriptions, in case they are contractors or do not require an Ordum account.

### Milestones


The "Milestones" section includes the milestones added by the user. This is a breakdown of labour that needs to be completed in order to finish the grant.

Each Milestone is a collapsable toggle. They consist of:

- The assigned person for the milestone
- Deadline
- Cost
- CTA: Expand for more
- CTA for the proponent: Submit Report
- Total cost for all milestones in USD


Upon expansion the viewer can see a description of the milestone and deliverables, which can be added by the proponent in the "Proposal Submission" UI.

---

### Costs


The "Cost" section includes:

- Milestones
- Costs(non-labour costs, eg. hosting, tooling...)

This section works on the same principle as the "Milestone" section, except it has added "Costs" which can be input by the user when submitting a proposal. The dropdown toggles include:

- Cost
- CTA: Expand for more

The CTA reveals a description and link to the reoccuring(monthly, weekly, yearly) or one-off cost.

> Denis: not sure if "reoccuring(monthly, weekly, yearly)" can be done simply via interface. Not sure it they are implemented, so it might require either a new functionality in the pallet or some fake-it by automatically reissuing the proposals (but then they would have been voted for again). @Kpymmwb5QNSqSBSqAwgAlA this shouldn't have to do with anything on-chain as reporting, milestones and calculations have not been standardised. The idea here is just to have a UI that calculates all of the proponents input costs so that they get a final cost automatically calculated. The only thing that goes on chain is the final amouont requested which includes all the reocurring spends. Eg. 5weeks reoucrring costs of 10 is 50 USD and that is added to the amount requested. Does this make sense?


---

### Reports


The `Reports` section allows the proponent to:

- Submit reports per milestone (these can also be submitted in the "milestones" section)
- Submit progress reports (progress report can be anything, but it mainly entails reports about progress, especially if some miletones and deadlines are delayed or missed)

Anyone is able to see these reports. Once the proposer clicks on "Submit report", the Text editor opens and they can write it in this section.

> Denis: text editor might be not that trivial (though I'll ask Pavel). Maybe say we accept importing md syntax and files and let them edit wherever they would prefer? @Kpymmwb5QNSqSBSqAwgAlA we have to have a text editor for the proposal submission anyways so I don't see a reason why not to have it here. Tl:Dr I want to avoid thrid party edits so all this can somehow be immutable at some point. WHatever the case, the majority of our concept falls into water without a text editor, correct me if I am wrong.


--> Report for a Milestone


--> Progress Report

The draft can be saved for later and will appear in the "drafts" section within "My grants".

> Denis: NB: autosaving is a default now. But the draft of any edits plead for being published. @Kpymmwb5QNSqSBSqAwgAlA I don't understand this.

If a user wants to see a report, they can click on "view report" button next to a milestone or in the "Reports" section.

The "Milestone" report would contain:

- Name of the proposal
- Milestone / Document Name
- Content that the proponent input
- Deliverable link
- CTA: Back to proposal


The "Progress Report" would contain:

> Denis: I didn't get, is there any difference between a Progress Report and a Milestone? @Kpymmwb5QNSqSBSqAwgAlA yes there is. "Progess reports" can be any kind of report that is submitted and "milestone reports" is basically a submission of a completed milestone.

- Name of the proposal
- Milestone/Document Name
- Content that the proponent input
- Deliverable link
- CTA: Back to proposal

### Treasury Profile Overview

Each treasury profile, including Kusama, will be comprised of:

1. **Grant Details**

- Introduction (short description of the grant program)
- Links (socials, contact and community)
- Projects we want to see (examples of types of projects the treasury/foundation is interested in funding)
- Get inspired (examples of previously well made projects)
- The community (a description of a community's involvement in a foundation/treasury)

Side bar contains data drawn from the Kusama blockchain:

- Next Burn (when the treasury burns funds next time. This is specific to Polkadot and Kusama)
- Projects Funded (number of successfuly executed proposals)
- Funding issued (amount of USD or KSM issued since the deployment of OpenGov on mainet)
- Available Funding (how much is left in the treasury/foundation)

---

2. **Application process**


The "application process" tab breaks down the application process of every grant. In the "Kusama Profile" it describes the governance model and requirements of every track.

**1. Understand the governance process**
> Denis: Let's move whatever is content from here to another document. Also, I'd suggest rewriting it in a more noob-friendly way. But this is not a priority at all right now. @Kpymmwb5QNSqSBSqAwgAlA we can rewrite it in a more normie friendly way when we can pay for a copywritter lol.

Both treasury proposals and network updates are executed through on-chain governance. It can be quite overwhelming and you are welcome to check out the full wiki here. However, if you only wish to apply for a grant, we've prepared a summary to get you started.

The Kusama OpenGov model works in a way where 1x token = 1x vote.
Once the vote is cast the tokens are locked up for a certain duration, and if the user chooses to do so for longer, the power of their vote can increase up to 6 times. Mind you; staked tokens can also be used to vote - which increases their utility.

The treasury has multiple tracks, but the ones relevant to you are:

Small Spender - up to 333.33 KSM from the treasury at once.
Medium Spender - up to 3333.33 KSM from the treasury at once.
Big Spender - up to 33333.33 KSM from the treasury at once.
Treasurer - up to 333333.33 KSM from the treasury at once.

Note: With further integrations we will also introduce bounties, which have been allocated curators and funds for specific types of projects.

If the proposer submits the proposal via Ordum they don’t have to worry about choosing a track as the platform will automatically allocate the track based on the requested USD amount.

Each proposal requires a down payment for a decision deposit in order for the proposal to execute. This amount varies depending on the track/ requested amount. The fee can be placed by the proposer or someone else. Below are the fees per track:

Small Spender - 3.333333 KSM
Medium Spender - 6.666667 KSM
Big Spender - 13.333333 KSM
Treasurer - 33.333333 KSM

Additionally, the proposer or another token holder must submit the pre-image deposit for the proposal to be enacted. This is a fixed fee of 1.33 KSM. The proposer will be asked if they wish to submit these or if they will leave it over to someone else.

Outline your project in either this template or within Ordum. Once you know how much your proposal costs, choose a track. Keep in mind that the difficulty of criteria increases proportionally with the amount of financing you require.

If the proponent is not well known in the community then it is suggested to break down the project into milestones which can be payed out per delivery. With this method you can establish a reputation, grow, learn and build up your skills.

There are 2 main criteria that impact the outcome of your proposal:

- the approval rate (the basic voting: AYE-pass, NAY-reject, Abstain-neither).
- support threshold (the % of all tokens in circulation used on 1 referenda/proposal).

Both of these can be visualised as curves that vary per track, which drop along the decision period, lasting for 14 days.

If the proposal is passing, after 14 days it entered a confirmation period, whose duration differs per track. This period can be shortened if there is a high participation % and high approval rate (this is highly uncommon). If the proposal is still passing within this period, then it is confirmed and the only thing left to wait for is the execution of funds, which usually happens when there is a treasury burn (a mechanism in the tokenomics to prevent inflation). The proposal can enter the confirmation period multiple times, but they are limited per track.

Below are the curves per track and their submission deposits:

> Denis: duplicates the paragraph above. Also, kinda repeats `Below are the fees per track` and the tracks descriptions. And, tbh, these graphs do not make much sense, maybe more infografics or explanations? @Kpymmwb5QNSqSBSqAwgAlA amended the paragraph. The graphs are from the official Polkadot Wiki, so I am keeping them as is for now.

1. Small Spender - up to 333.33 KSM from the treasury at once. Submission Deposit: 3.33 KSM


2. Medium Spender - up to 333.33 KSM from the treasury at once. Submission Deposit: 6.67 KSM


3. Big Spender - up to 33333.33 KSM from the treasury at once. Submission Deposit: 13.33 KSM


4. Treasurer - the origin for spending funds from the treasury, up to 333333.33 KSM


**2. Join Element**

If you think that the Kusama Treasury is the right choice for your project, create a Riot/Element account to join our communication channels if you do not have one yet.

[Kusama Direction:](https://matrix.to/#/#Kusama-Direction:parity.io) it is for discussions about Governance-related initiatives on the Kusama network, including submissions to the treasury.
[Kusama Watercooler:](https://matrix.to/#/#kusamawatercooler:web3.foundation) it is for any questions related to the Kusama network and the Kusama community in general.

**3. Draft your proposal**

Create the proposal document that will be submitted to the community to assess the quality of your initiative. A proposal template can be found [here](https://docs.google.com/document/d/1CzEnurqwqLBOGrJI9CQORiGW9m6QyPOSshhzJdR57Pk/edit#heading=h.7fq1r3kiaao7) for you to use as a guide, but this is only a recommendation on how to structure your presentation to increase the odds of having informed discussions. Alternatively, you can create your project proposal directly with Ordum (add link to submit grant).

Note: Your proposal must present a problem, define a goal, and propose an instrument to achieve this goal. Think about your project in the mid and long-term and make sure to include notes about any type of funding required to maintain the project after its initial developments.

**4. Create Identity**

Make sure that all accounts that will be used to post the Treasury proposal information on-chain have an [on-chain identity](https://support.polkadot.network/support/solutions/articles/65000181981-how-to-set-and-clear-an-identity).

**5. Seek Feedback**

> Denis: here, in 3, 4 and 5, we're sending the users to read about ID and post their proposal to Polkassembly. Some might not return, might make sense to shuffle the steps for now @Kpymmwb5QNSqSBSqAwgAlA , for now I want to keep this as is and in the future we can get a professional copywriter to update it as I don't think it is a priority and we will mainly have polkadot users to begin with. The page is quite lenghty already as well.

Post your proposal document (in view only) and all its information as a [discussion](https://kusama.polkassembly.io/discussions) on one of Kusama’s forums such as [Polkassembly](https://kusama.polkassembly.io/discussions), [Subsquare](https://kusama.polkassembly.io/discussions), or B[rightTreasury](https://treasury.bright.dev/learn-more?networkId=kusama), so that all feedback provided remains accessible.

Inform the community by posting a message along with an accessible link (in view only) to your proposal in the Direction channel to start the discussion.

Be ready to answer questions and address concerns from community members on Kusama forums and channels for a minimum of 7-10 days. Include important questions and answers at the end of the proposal document to keep it up-do-date.

**6. Update based on feedback and submit your proposal**

Submit the proposal as an OpenGov referendum under the appropriate Track and pay the Decision deposit to finalise your submission.

**7. Add relevant information to your proposal**

Log onto Polkassembly or Subsquare with the same account used to submit the proposal on-chain and add contextual information to the post that was auto-generated by your on-chain submission. You should edit the title and description of the post to match all the information from earlier discussions, such as the proposal document, link to the original discussion, and any other relevant information. If you have applied through Ordum, all the information will be displayed within your proposal.

> Denis: `all the information will be displayed within the platform.` more specifically: in your Proposals menu, maybe even as a link. @Kpymmwb5QNSqSBSqAwgAlA this specifically refers to the proposal itself, rather than the dashboard. So I changed it to that.

**8. Engage**

Continue to engage with the Community on Kusama forums and channels for the duration of the referendum, and at regular intervals after its approval.

**9. Report**

Publish a proposal report on Kusama forums before seeking further funding for your project(s).

> Denis: this might look as a boring wall of text to some. I'd like it to be in a modern *tiktok-ADHD* friendly way: with emojis, as a checklist and fancy, maybe interactive. --> @Kpymmwb5QNSqSBSqAwgAlA Firstly, we can make this interactive and far more digestible but I am not using tiktok /quick social media ways to do this as a lot of info will be misleading. Secondly, I have ideas but rn I don't think "outsiders" are our target demographic for the mvp.

> Also, all the documentation we post here, should be as interactive as possible: with wiki-links and in hard cases with GIFs or even explanatory videos.
> Not a priority.

CTAs:

- Join Element Chat
- Back to top
---

**3. Wiki**

The "Wiki" tab [links](https://guide.kusama.network/docs/learn-polkadot-opengov) to the official documentation of the foundation/treasury.

---

Missing:

- Proposal Submission
- Change "" to <>
- Some graphs?
- Breakdown big graph into smol ones