RAIRprotocol
  • 💎Welcome to RAIR
  • 💴Whitepaper (draft)
    • Start
      • History
      • Licensing
      • Codebase
      • Onboarding
      • Mechanics
        • Burn Model
        • Earn Model
      • Governance (DAORM)
  • ↔️Integrations
    • Core Technologies
      • Guides
        • Alchemy
        • GCP Cloud Storage
        • Web3Auth
    • Blockchains
  • 👩‍💻CODEBASE
    • RAIRsolidity
      • Soneium (Minato)
      • Core DAO
      • All Contract Addresses
      • Transfer functions
    • RAIRdapp
      • RAIRfrontend
        • Proxy Settings for Default Frontend
        • Frontend Variables Library
      • RAIRnode
        • Permissions and Access Controls
        • Backend Variables Library
      • RAIRsync
        • Integrating New EVMs
      • RAIRstream
      • RAIRinfra
    • RAIR API
      • Endpoints
        • Auth
          • Get challenge
          • Login
          • Logout
          • Me
          • Unlock
          • Stream
            • Out
        • Analytics
          • Csv
        • Contracts
          • FactoryList
          • Full
          • Import
          • My
          • Network
            • Products
              • Offers
        • Credits
          • Withdraw
        • Favorites
        • Files
          • ById
          • ByCategory
          • Categories
          • ForToken
          • Unlocks
          • List
          • Remove
          • Update
        • Nft
          • Network
            • Attributes
            • Files
            • Locks
            • Offers
            • Token
              • Pinning
          • PinningMultiple
          • Csv
            • Sample
        • Offers
          • /
        • Products
          • /
          • User
        • Resales
          • Create
          • Delete
          • Open
          • Purchase
          • Update
        • Search
          • All
        • Settings
          • Featured
          • Theme
          • AppLogo
        • Tokens
          • /
          • TokenNumbers
        • Transaction
        • Upload
          • File
          • Validate
        • Users
          • /
          • Export
          • List
          • Yoti verify
      • Specification
    • A Note on Documentation
  • ⚙️Installation and Testing
    • Getting Started
      • Welcome to New Web3 Devs!
      • RAIRlite (Single VM)
        • Windows WSL Installation
        • MVP Test Plan
        • https configuration
      • RAIRcloud (Cloud Enabled)
        • Cloud Test Plan
  • 🛟End User Guides
    • User Functionality
      • How to login
      • Buy your first NFT
      • Put items up for sale
      • Watch Content
    • Admin Functionality
      • Deploying NFT contracts
      • Managing Metadata
      • Managing Media
      • Managing Marketplace
      • Managing Users
      • Importing External Contracts
Powered by GitBook
On this page

Was this helpful?

  1. Whitepaper (draft)
  2. Start

Onboarding

How developers interact with RAIRprotocol

PreviousCodebaseNextMechanics

Last updated 2 months ago

Was this helpful?

RAIRprotocol will only be as successful as the community that supports is ongoing open source development. As such, developers must be rewarded for their valuable contributions to the network. We call this reward Dapp (DevDapp.com)

Event Listening Logic

RAIRprotocol utilizies 3rd party repository management software (namely GitHub) as the source of truth for distributing incentive rewards. While GitHub is not the exclusive repository for RAIRprotocol, it has by far the largest active developer community in which to achieve a network effect from.

Event listing logic of RAIRprotocol can apply to any public facing code repository, though the initial implementation is specifc to GitHub event emissions.

Incentive Workflow

  1. Developer signs up to work on RAIRprotocol from the offiical RAIR Incentive program dApp by connecting his or her Github account via Auth0 social logic flow and generating a Web3 Wallet.

  2. Developer finds a list of available tasks to perform. Bug submissions, bug fixes, new feature request etc.

  3. To create an issue recognized by the DAO github, the developer must choose to join an available pool.

  4. Upon creating a new issue in Github, the core DAO team will review the issue and if valid apply the appropriate label.

  5. This labeling process generates an event in the GitHub API. Logic in the onboarding dApp then matches the label with the associated github username and assigns "points" (offchain token IOUs) to the user.

  6. User can then choose to stake their points to receive the full amount, or have immediate liquidity for a tax.

  7. Event logic continues to work for deeper code work, including the successful merging of pull requests into main.

Any event in Github can be configured to generate rewards. Emissions rates and how ongoing developer rewards fund is distributed is at the sole discretion of the RAIRprotocol DAO members. See mechanics section for full explanation.

💴
(earn model)