Resolving how Nexus stakeholders are getting paid is equally important to defining how the system will work technically. One could argue that defining the tokenomics before the technical aspects might even be more beneficial. Either way, they are - in web3 - inseparable. We now have a clearer 

 roadmap so now it’s time to address tokenomics. Understanding the basic economics of 

Nexus is supposed to make integrations simple. This has to necessarily include paying for them. Specially considering that payments are fragmented and as a result complex in competing systems like Chainlink.


 For example, a DAO on DAOHaus running on Gnosis Chain should be able to pay for the service in xDAI and have a clear understanding of the project cost to be able to provide appropriate funding.


This simplification bears significant technical challenges are laid out in this document together with a solution approach. 


Somebody will have to pay for the execution of a workflow. We will call this stakeholder from now on a 

 are external systems but perform a crucial function that has to be rewarded: they relay information from and to the 

 are ensuring that the Executors and the Connectors are doing their job and will equally get a reward for that.


Nexus requires the storage for (meta) data on 

 for bridging messages and tokens. Other system might be added over time.


When performing transactions on 3rd party 

 (like Ethereum or Near) gas chas to be paid. Additionally some services are provided by 

 by requiere payments of external providers (like Sendgrid) making it necessary for 

 that act as web3-Wrappers to be able to get paid in tokens.


Executing and validating multiple connector types


Customers can define the value of a workflow or in other words the economic impact of the workflow failing. (we could potentially do this automatically or at least suggest values).


Customers then pay a % of this value as an insurance for the execution. per execution or ongoing. Not sure yet.


Executers,  Validator and Connectors each need to stake each the total value of the workflow (as declared by customer) for every workflow over a period of time (e.g: 30 days post processing)


If everything goes well they distribute the insurance payment between them (details TBD). If something fails they can be held liable  (e.g: for up to 30 days), their stake withdrawn and the reputation slashed. Reputation could also impact the amount they need to stake.


The protocol could also incentivize people to do automated, semi-automated or manual verification/validation. The method can adjust over time and the tools for that can be developed independently.


Furthermore the protocol can be designed in a way that increased security in general increases the return of all actors making the look for ways that systems are secured collectively.


On Tokenomics

grindery

Business

Welcome

Courses

Miscellaneous

Funding and Grants

Grindery Planning Sessions: August 2022

Onboarding

gWork

Developers

Review

Partners

Active Topics

Grindery Nexus Feedback 2.0

Grindery Nexus Feedback

Demo Day Priority

Nexus Review 3

On Token Allocation

On Connectors

On Community 

On Organization

On Brand

On Roadmap 

On Validation

Co-creation Slide

Co-creation

Marketing

Funding/Investing - Inbound/Outbound

Funding/Investing

Knowledge Management_Operations

Grindery DAO Sales Process

Grindery Unified Marketing

Grindery Marketing

Grindery OKRs

Orientation for New Hires

Understand Grindery & its projects

Orientation

Grindery 101

Grindery Culture Slide

Grindery Culture: Habits and Practices

How to get paid at Grindery

Grindery Payment Policy

Getting started at Grindery

Harmony DAO

The Graph

Storage

Snapshot-XMTP-Grindery

ANKR x Grindery.io

ANKR

Chain Partnerships

XMTP

Ceramic

Celer

(d)Apps 

DAOs/Multisgs

Cosmos/Ignite 

Binance BSA

Polkadot 

Grindery Grant Program (WEB)

Grindery Infinite Fundrising (9-6-2022) - current

Grindery Infinite Fundraising

Grindery Zapier (Dimitri)

Grindery Zapier (James)

Grindery Zapier (Mohammed)

Grindery Zapier (Richard)

Grindery Zapier (Alek)

Grindery Zapier App Test Task

Grindery OAuth 2.0

Grindery DePay

Grindery Nexus Authentication Process

Get started: Grindery Progressive Scope

Grindery Integration Options

CDS Editor

Creating Blockchain Connectors

Grindery - Cross chain technologies (copy)

Grindery DePay Router Protocol

A guide to FLOW CDS

Conector Analysis

Grindery Ping Feature RoadMap

Gnosis Safe App Dev

Grindery Connector Roadmap

SDK Documentation

Grindery: A Simple Plan

Team

External Document List

Snapshot App development

Grindery Sanity Check

Developing Web3 Connectors

Grindery Payment Rails

Grindery Payment Rails - Celer

Demo Day Connectors

Grindery Roadmap in tracks

Roadmap

Module 4: How to get paid at Grindery

Module 3: Grindery Payment Policy

Module 2: Grindery Culture, Habits and Practices

Module 1: A brief history of Grindery

Exercise: Detect a transfer on any EVM chain

Grindery