# Ordum Notification and Activity System V1

Ordum has the ambition to develop further tooling for grant applicants and foundations, but version 1 of this system focuses on the needs of the Kusama protcol treasury and its token holders.

## Problem

The notification system is mainly designed to address the problems of the token holders, less of the applicant, as in this phase of the user journey, community members will have issues with:

- staying up to date with new proposals and discussions
- staying up to date with comments
- knowing of proposal changes and edits which may affect their vote

Even though the notification system addresses mainly the the issues of the community, it points out a key issue which resides with the applicant: **impacting the community vote once the proposal has been edited to reflect the insights of the token holders.**

## Hypothesis

**Ordum will eventually have 3 types of users:**

- Applicants (individual/teams)
- Foundations (centralised/decentralised)
- Decentralised community voters/ token holders

Notifications play a big role within an individual's attention span, therefore the goal of this system is to minimise distractions, as well as searches.

**Polkadot grant systems usually come in 2 types:**

- off chain (usually forked from Web3 Foundation Github)
- on chain (a decentralised protocol such as GOV2 on Kusama and others which have councils*)

**with the assumption that these will eventually be obsolete in favour of their own versions of GOV2*

**As our MVP is for Kusama, a decentralised treasury governed by token holders and a protocol, our notification system will focus on:**

- Applicants
- Decentralised Community Voters / Token Holders

---


*fig 1: Kusama Applicant User Journey*

---
Based on the current Kusama Treasury user journey and system, we can define these user's interests:

**Applicants**

- Comments on proposals and submissions
- Status updates on proposals (deciding, passing, confirming, passed/rejected, executed)

The most important element for an applicant is to be able to take into account the community's feedback, as they decide on the outcome of the proposal. This is done through:

- Comments on Polkassembly and Subsquare
- Kusama Direction Channel
- Other social media channels

When the applicant is up to date with all the information they can take into account constructive feedback and refine their proposal.

**Token Holders**

- New Proposals
- New Discussions
- New comments on involved proposals and discussions
- Changes to Proposals and Discussions

The goal of the token holder is to maximise ROI of the treasury and think of the community's and protocol's best interest. For this purpose, members are actively involved in reading new proposals, commenting, following social media, the Kusama Direction chanel. Additionally, there are different comments in both Subsquare and Polkassembly.

## Solution

Ordum will tackle the mentioned issues in a few ways, but the notification system is meant to keep community members, as well as applicants, up to date with new proposals, submissions and comments.

### The design

Notifications will show as:

- `new activity`
- `history`

...in the Ordum `Home Dashboard`.

Notification types categorised per user:

| Token Holder | Applicant |
| ------------ | ------------------- |
| New Proposal | Comments on submitted Proposal |
| New Discussion| Comments on submitted Discussion |
| Status report on followed and commented proposals* | Status report on proposal**
| New comments on involved discussions | Reminder for milesone submission
||Updates on relevant actions from other team members in the organisation, eg. proposal submission

- **New comments included from Subsquare and Polkassembly*
- ***Status Report Includeds changes of state; `deciding`, `confirming`, `passed/rejected`, `executed`*

**How do the users opt in for notifications?**

| **Token Holder** | **Applicant** |
|----------------- | ------------ |
|Follow Kusama Treasury| Automatically as a team member, can be turned off in Settings


*fig2: Ordum Notification flow chart*


Fig3: System Notifications, Errors and issues


Fig 4: Feedback Notifications

[Open Figma File](https://www.figma.com/file/mtUpWEnESZjhEk0Kd9pNHd/Ordum-Notifications_V1?node-id=0%3A1&t=CRFDVtSioxBHYQIL-1)

## Implementation

We will start by using Kian's Basic Notification System for any on-chain movements. We will have to decide how to track:

- changes of proposals and docs
- comments on PA and SS