Co-creation

Last updated by Jamiu Idowu 2 months ago

Partnerships/Co-creation 

Background  

The general purpose of the Nexus engine is to help users add integrations to improve their user experience. 
This includes Web3 users, and we also want to bring the mass of Web2 users into Web3.  
So in addition to working directly with DAO frameworks, DAOs, and DApps to confirm how we can help them add integrations to improve their user experience, we should also work with Web2/SaaS companies to bring to them Web3 technologies that they could use.  
Examples of target companies are the large Web2 companies, such as Google, AWS, Microsoft, but also all the no-code services like Notion, Airtable, etc.  
In order to engage we need to confirm: 
What Web3 users/companies are interested in 
What Web2 users/companies are interested in 
 
From an initial set of discussions with various players: 
 
Web 2 end-users  see Grindery a company that helps bridge web2 and web3. They are looking for help in the  on-boarding into the Web3 world 
 
Web 3 end-users  see Grindery a company that helps  improve their user experience 
 
Web2 companies  are looking at Web3 and the areas where there is traction are: 
 
NFTs (=B2C)  as a way to establish ownership of an asset (digital or physical). This is an easy way into Web3 as a lot of people like to collect images and are happy to try NFTs. And on the business side they can see the value of documenting ownership or notarizing events 
Q: what is Grindery doing for NFT users? 
 
DAOs (=B2B)  as a way to change how people collaborate.  
The immediate value of DAOs seem to be a way to establish a budget for something (there seem to be a lot on the non-profit side).  
And moving forward, DAOs are tied to the future of work discussions. One thought leader in the Future of Work discussion is Ricardo Semler - https://semcostyle.com/  
The big challenge facing DAOs is the voting mechanism. In order to be valid, a vote should be: 
Obtained from a group that is representative of the community impacted 
Informed: 
All voters should be exposed to pros and cons and impact on minorities 
All minorities should be heard to prevent the dictatorship of the majority 
Time given to minorities should be managed to prevent the takeover by a vocal minority  
The current systems are prone to manipulations: 
One person can have many wallets, and therefore vote multiple times 
Representation is not really checked, whoever has a voting token will vote, and for now most token holders vote but it is not clear how this will evolve 
Knowledge of the topic is not checked, so votes may or may not be informed 
Who can submit proposals and what type of proposal are submitted to a vote is not always controlled so there can be a bias there too 
 
Q: what are we doing for DAOs today? Can we provide anything related to voting mechanism? other? 
 
There is also an opportunity for Grindery to contribute to help the implementation of Web3  infrastructure to decentralize services .  
A low hanging fruit in this area would be  Personal Data management :  
implementation of  Authentication  through a Wallet, and  
Storage  using IPFS  
Today IPFS is mostly for archive, and since a pinning service is required to keep at least one access to the content the model is not really decentralized. 
Microsoft also mentioned that Web3 technologies could be used to extend  Robotic Processing Automation (RPA) . Instead of a hosted service provided by Microsoft, some of the work could be offered to “miners”. This is similar to what we are considering doing for Grindery. 
 
Q: what can we do in terms of decentralized infrastructure? 
 
Web3 companies are looking for help improving user experience.  
A group of DAOs and DAO frameworks is working on improving the technology and establishing standards so that people can work across DAOs and Chains: https://daostar.one/  and https://metagov.org/  
We need to be involved in these discussions. 
 
Q: can our CDS be pushed as a standard? 
 
Beyond the functional aspects of what can be done on, off and across chains, there is also the issue for all players of paying for the gas fees required to execute a workflow. 
There is an opportunity for Grindery to provide a solution to make the payment of gas fees transparent through the implementation of liquidity pools. 
A group of liquidity pools funded by the various Blockchains and DAO Framework would be the equivalent of Visa, a consortium of banks implemented to facilitate payments across various banking systems. 
A group of liquidity pools that we implement ourselves would be the equivalent of Wise.com, that has setup bank accounts in various countries to facilitate payments across countries and currencies. 
 
Q: how far are we from being able to formulate a solution to DePay? 
   
 

Potential Narratives 

Option 1: Grindery is pioneering the Future of Work. 
We are a decentralized organization in the real world, we are implementing Web3 technologies to become more efficient. Areas where we can try this: 
DAO for fundraising 
Gnosis Safe for treasury management 
Celery for budget management 
Storage using IPFS 
In order to make it work, we need to integrate our existing tools and processes (Web2) to these Web3 bricks. And in doing so, we make it easier to others to adopt these technologies. 
NOTE: this is what we say in the White Paper already 
>>How does Grindery Nexus create value? We’re using our example DAO. But rather than creating an individual integration, we will create a Moloch extension called a “Boost” that can then be reused by any other DAO.   

Use cases that we can promote today (on the shelf):   

Improved budget management (Gnosis safe, Celery, etc.) through the integration with spreadsheets or databases, and through notifications 
Login with a Wallet 
Notifications of events recorded in a Blockchain 
NOTE: messaging apps are the most used apps in Zapier, there is a good chance that the same will apply to Web3 
 

Examples of collaborations with Web3 communities 

Harmony: 

Payout for DAOs 

AstroDAO 

TBD 

Gnosis 

Embedded integration: notifications 

Examples of collaborations that we can explore with SaaS companies:   

Zapier 

Access to all their integrations through the Nexus integration. We can reproduce this model with Microsoft and others. 
NOTE: we want to be on all available marketplaces  

Skiff 

Notifications  

XMTP: 

Notifications 

Sendgrid 

Integration so that we can send notifications  

Notion:   

how to save pages in IPFS instead of regular storage as provided by Notion(?)  
How to connect a Notion table to a Vote proposal or a mass payment 

Airtable:  

How to connect an Airtable to a vote proposal or a mass payment 
 

Google/AWS/Microsoft: 

How to provide IPFS nodes for private storage - the value is that instead of being tied to a specific provider users will be able to manage their data better 
How to provide infrastructure to deploy nodes for processing of workflows 
How to tie an account to a wallet so that Login can be done through a wallet rather than the email address 
 
 
Refreshed On: Dec 06, 2022 08:53:25 UTC+00:00