Ordum Features

# Ordum Features Polkadot's public good grants aggregator --- ### **Introduction:** ### ——> Web3 grants aggregator for an easier access to funding **ACCESSIBILITY**: - Aggregating and interpreting foundations grant application journeys into clear and comprehensive guidelines. -   Creating a user-friendly and intuitive platform that centralizes grant opportunities from various sources. **TRANSPARENCY**: - Enhancing decision making of token holders (protocols) and foundations (centralised entities) through data aggregation. - Establishing a transparent funding platform to track project progress and financing at various stages by leveraging the immutability of blockchain to maintain data integrity. **ACCOUNTABILITY**: - Improving accountability through reporting UIs and on-chain smart-contract tracking - Tracking the quality of grant deliveries and performance with a milestone based system and data aggregation ## **Current Features** The desktop webapp currently includes the features below: 1. **Account creation** for teams and individuals: - Individual and personal profiles cosist of "teams" the individual is in, "Bios", "Links", "Number of applications" and "Funding received". - Organisation profiles consist of "activity" and "team members" for accountabilty purposes --- 2. **Smart contracts data aggregation** based on different data points: - **The type of project** (DeFi, Identity, Privacy, Infrastructure, Art, Media, Gaming, Events, Education, NFTs, Translations, Other) - **Number of applications** per organisation/individual, number of submitted and edited milestones - **Blockchain** (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) --- 3. **Seamless UX/UI** Simple UI for applying to the Kusama treasury: - **Treasury profile/centralisation of documentation;** consists of existing proposals per origin track (from Polkassembly APIs), documentation on the application process and all necessary links in one place - **Abstraction of pre-image submission** - **Automated track allocation** based on the requested amount in USD - **Automated calculation of the requested amount in USD to KSM** - **Automated execution block input** based on a "start date" - **Text editor** within the application user journey for the purpose of tracking changes once the proposal is on-chain (backend consisting of mongo DB and decentralised Crust IPFS storage for immutability) - **Organisation synchronisation;** each team member can create an account which can be synced to a proposal - **Milestone and labour cost accountability** Adding tasks, costs and assigned team members to the milestones, which are trackd with PHAT Smart contracts, including a reporting UI. --- 4. **Dashboard for token holders and applicants to track:** - new proposal missed or close deadlines - proposal drafts - team mates --- ## Future Features The platform presently encompasses a range of features. However, to enhance the user experience for both grant management and governance, the project aims to conduct technical research. The goal is to select a suitable tech stack and architecture that would transition the platform into a blockchain-based and interoperable system, all the while maintaining a seamless user experience. The subsequent outlines shed light on specific challenges that hold significance for both the Polkadot ecosystem and the wider industry. Our objective is to address these challenges through the implementation of novel features: --- ### Polishing loose ends/ next grant application: - ~~Add the "pivoting" function to milestones~~ - ~~Voting on pivots by previous aye voters (feature 3)~~ - Commenting on deliveries by previous aye voters (send notification | build reporting UI) (feature 3) - Improved notifications - Documentation (Collect documentation in text format, project spec, proceed development) | Denis & Devs - Maintenance cost for kusama —> on ksm chain | Ela, Denis, Devs - R&D for new features | All team - R&D and surveys with foundations/grants programs in our ecosystem and 10 projects from other ecosystems | Roman and Ela Team --- **Development** 1. Blockchain developer 2. Front End 3. Full Stack 4. CTO **Design** 1. UX designer 2. UI designer **Other** 1. Researcher 2. Chief Product Officer ### 1. Set re-occurring spends *[ add examples of screen shots]* - The community has been vocal about demanding re-occurring spends for larger treasury proposals. A UI to set these functions up on chain doesn’t exist. - We would like to enable proponents to: set up-front payment, milestone release payments/ re-occurring spends, rewards for the completion of their grants proposal ### 2. Simple multi-sig creation [ add examples of screen shots + provide UI mockups] The token holders have stated multiple times that they would like to see larger grant applications go into a multi-sig. Our ecosystem has multiple great examples (Polkadot vault, Multix, Saturn…) and we would like to see how to enable easy multi sig creation for every organisation within the Ordum UI. Additionally, we would like to see how to include other multi-sig wallet creations from other ecosystems, notably Ethereum, Near and Cosmos. ### 3. Relevance, accountability and reviews Election of a council/ group of reviewers and/or the ability for previous voters to vote again on the quality of a milestone delivery. - There will be 2 types of multi-sigs (one for the teams // one for the council multi-sigs) - Current reporting is conducted via comments on Polkassembly or Subsquare, where the proponent submits documentation as a comment - We would like to enable the proponent to either set up their own council(GOV1) which checks the quality of their delivery and/or enable the “AYE” voters to vote again on the quality of the delivery. Surely the “council” can be gamed, but if done via multi-sig and when there is a demand for a trusted community member to be on-board this would be possible - Very often the reviewers of the proposals don’t have relevant knowledge, the proponent can add details on their councillors and their credibility, these can be rejected by the community before being initially voted in. - The councillors would be automatically added to the multi-sig governing the re-occurring spend of the team --- ### 4. On-chain discussions *[ add examples of screen shots + provide UI mockups, provide user journeys from other ecosystems grants and gov platforms]* As it stands, the user journey for grant application and evaluation is very similar across ecosystems. Each journey begins with an interaction with the community by submitting a discussion, usually to a Discourse type of forum. As we all know, this is not on chain so it creates friction and lacks data aggregation. The team aims to research how this can be brought on-chain. Currently we want to see if this can be done by using Subsocial as a layer of communication and deployment of PHAT oracle smart contracts. --- ### 5. (not for the next proposal)Automated creation of DAOs on the collectives chain ### In order to maintain consistency across the ecosystem and incorporate automated payouts, we are looking into the automated creation of organisations on the collectives chain once a team account has been created. This would enable teams to set re-occurring payments of salaries and other types of payments, while being registered as a collective in the identity registrar. --- ### ~~Prediction Market integration (if so den ksm)~~ ### [ add examples of screen shots + provide UI mockups] We are currently exploring the idea of Futarchy and how it can accelerate community research and participation for every on-chain proposal. It is our goal to test and see whether an automated prediction market creation around every governance proposal would provide further insights on organisation / individual applicants, as well as token holder engagement. --- ### [NEW] Project management and automated payouts - ### Voting interface with relevant data + guides As treasury grants are coupled with governance, Ordum will require an integration of a voting interface to decrease friction. One of the issues in these instances is a lack of voter turnout and a lack of time for community members to evaluate proposals. The current Ordum UI facilitates a TL;DR section in the application, which states that the user must submit a short description for their proposals with relevant facts, limited to 800 characters. Some community members mentioned using a “tinder like” voting interface for such occasions. The team would test out and see whether this would yield higher engagement and better decision making across multiple ecosystems. On this occasion, we would partner up with the General Magic team to build a front end UI, as they have already built such software for other DAOs. On top of this interface, we would attempt to integrate newcomer guides to for governance across up to 3 ecosystems; to see whether it would help increase governance participation of non-crypto native users. ### Voter Data aggregation In order to see the involvement of certain community members and organisations, the Ordum team would research on how to aggregate data on voting. This is being implemented in both Subsquare as well as Polkassembly, so we might reuse their code. However, the research would go beyond just the Polkadot ecosystem and we’d issue surveys to other ecosystems to see which data would be relevant across the industry + how to implement this. The data would be: consistency of voting, no of delegations, no of votes, no of proposals whose decision aligned w the vote ### Delegation Dashboard As delegation is crucial in governance, the team would research how to implement aggregated data on delegates across ecosystems. We would attempt to integrate the existing dashboard which was made by the Parity team, as well as enhance it with data from other ecosystems for better decision making. This would show the governance participation of individuals and groups across the industry. ### Voting with any token on any network This implementation is a bit of a peculiar one and it might spark both chaos and controversy across the industry. However, we believe if there were atomic swaps in the background of governance votes and if token holders would be aware of the risks of conversions, this might increase participation, democratic solidarity, as well as engagement and exposure to other ecosystems. In this instance it would be crucial to see what kind of technology needs to be implemented in order to execute this safely and seamlessly, with proper security measures in place. Additionally, a test would be required to see what the consequences and results of this type of implementation would be. ### Anonymous voting It is evident that every ecosystem requires anonymous voting for the purpose of protecting the integrity of a proposal and its voters. Multiple community members have complained about being harassed due to their decisions to participate in governance. Everyone has the right to safely decide which way to vote, whether they are a whale or not. The Ordum team would attempt to implement this with PHAT smart contracts and test it across multiple ecosystems. --- ### AI integration for spams and malicious proposals As mentioned above, there have been certain malicious proposals on various parachains [ add examples ] , for the purpose of preventing hostile takeovers; we would like to research and implement AI to scan for these and alert the teams of any potential negative impact. Additionally, we have seen scam proposals for airdrops turn up for both Kusama and Polkadot treasuries. We can identify the wording and these and develop our AI to stay on top of these kinds of proposals, if not completely block them from being proposed on the platform. If proven to work it could be used across multiple governance platforms across the Polkadot ecosystem and wider industry. --- ### Off-chain grant integration There are quite a few grants across the industry which are not on-chain or are semi-on-chain [ list grants programs ] . Additionally, they use a variety of platforms for their grants programs such as Github and Notion. --- ### Considering AI integrations in the future: - matching builders with grants - matching builders with each other for teams ---