├── 1. Introduction.md
├── 4. Tokenomics.md
├── LICENSE
├── RAIRprotocol Brand Kit
├── EPS
│ ├── RAIR Protocol Logo 2024-02.eps
│ ├── RAIR Protocol Logo Black-02.eps
│ └── RAIR Protocol Logo White-02.eps
├── JPG
│ ├── RAIR Protocol Logo 2024.jpg
│ ├── RAIR Protocol Logo Black 2024.jpg
│ ├── RAIR Protocol Logo Color.jpg
│ └── RAIR Protocol Logo White 2024.jpg
├── PNG
│ ├── RAIR Protocol Logo 2024.png
│ ├── RAIR Protocol Logo Black.png
│ └── RAIR Protocol Logo White.png
├── RAIR R Symbol Only
│ ├── EPS
│ │ ├── RAIR SQ Symbol Logo-Black.ai
│ │ ├── RAIR SQ Symbol Logo-Black.jpg
│ │ ├── RAIR SQ Symbol Logo-Color.eps
│ │ ├── RAIR SQ Symbol Logo-White.ai
│ │ └── favicon6.ico
│ ├── JPG
│ │ ├── RAIR SQ Symbol Logo-Color-BlkBkGrd.jpg
│ │ ├── RAIR SQ Symbol Logo-Color.jpg
│ │ └── RAIR SQ Symbol Logo-White-BlkBkGrd.jpg
│ ├── PNG
│ │ ├── RAIR SQ Symbol Logo-Black.png
│ │ ├── RAIR SQ Symbol Logo-Color.png
│ │ └── RAIR SQ Symbol Logo-White.png
│ └── SVG
│ │ ├── RAIR SQ Symbol Logo-Black.svg
│ │ ├── RAIR SQ Symbol Logo-Color.svg
│ │ └── RAIR SQ Symbol Logo-White.svg
└── SVG
│ ├── 4F3F6E0BBA68FA90.jpg
│ ├── RAIR Protocol Black 2024.svg
│ ├── RAIR Protocol Logo 2024-02.svg
│ └── RAIR Protocol White 2024.svg
└── README.md
/1. Introduction.md:
--------------------------------------------------------------------------------
1 | ## 1. Introduction
2 | The business model of the internet hinges on the interplay of proprietary and open source. In the typical model, an enterprise develops an open source underlying codebase, that is then monetized by a centralized for profit corporation.
3 |
4 | ----------------
5 |
6 | ### History [1.1]
7 | Redhat Linux pioneered this model in the late 1990s, much to the chagrin of Linux core developers. Despite a valiant effort to reward Linux contributors with shares of stock in the Redhat corporation, the systems for compensating open source development remain controversial.[1](#References)
8 |
9 | In the web2 era, proprietary moats developed using the underlying rails of HTTP:// and other core protocols. While users rely on the open internet to access the FAANG behemoths, in web2 no monetization inherently accrues to the maintainers of the underlying protocols.
10 |
11 | ### State of Web3 [1.2]
12 | With the rise of public persistent data (aka blockchain) the monetization of open source entered a new "Web3" era.
13 |
14 | Developers believing in the protocol, for the first time could be compensated in the native unit of the protocol. Either by purchasing tokens directly, or through increasingly sophisticated grant mechanisms. By 2016, this thesis was codified into the seminal blog post "Fat Protocols [2](#References) where the author posits open source protocol tokens will solve the Redhat vs Linux compensation and incentive issue.
15 |
16 | Fast forward to 2024, and it is mandatory for the core protocol layers of Web3 (L1/L2 blockchains, Oracles, DA, Restaking, etc) to be open source to be trusted. //However// the Dapps built on top of Web3 are largely NOT. The VC model to fund teams that take open source infrastructure to then build proprietary business logic moats on top of is still alive and well.[3](#References) Conjecture.. the development of Web3 killer Dapps is being stymied by this proprietary smothering.
17 |
18 | ### RAIR [1.3]
19 | The RAIR protocol has been in active development since 2019 as an investor backed enterprise SaaS product. In 2024, the entire RAIR Codebase is available for the first time via an open source Apache 2.0[4](#References) token licensing model.
20 |
21 | Throughout this whitepaper, we will articulate our reasoning for going fully open source, and expound upon our token licensing model to reward the development of the RAIR token supported Dapp layer.
22 |
--------------------------------------------------------------------------------
/4. Tokenomics.md:
--------------------------------------------------------------------------------
1 | ## 4. Tokenomics
2 | To keep the tokenomics simple and straightforward, the RAIR token is designed with only 2 primary functionalities.
3 | * Burn model: Burning RAIR tokens for a perpetual license NFT at graduated rates based on enterprise ARR.
4 | * Reward model: Performing onchain activities (Deploying and updating RAIR smart contracts) requires RAIR. Incentive systems to reward early adoption and compensate open source development via a points -> fungibles conversion process.
5 | Our factory deployment tools require the submission of RAIR tokens along with each onchain deployment to function.
6 |
7 | #### Forking
8 |
9 | While this can be forked and bypassed, choosing to pay the RAIR tokens funds open source development, and ensures the officially verified smart smarts are used. Only wallets with valid license NFTs can collect rewards. Finally, projects bypassing the token code are in violation of the terms of use of the open source licensing agreement.
10 |
11 | #### Figure 1:
12 | Workflow to register a license using the RAIR open token license model
13 | 
14 |
15 |
16 | ### Deflationary Burning [4.1]
17 | Burn RAIR tokens to receive a full open source license to software. RAIR will be burned and converted to a soul-bound NFT representation of the license that each entity can use as proof-of-license.
18 |
19 | This creates a downward pressure on supply. Each NFT license created will be able to stake for network rewards in the future on an exponentially decreasing rewards rate.
20 |
21 | Note: Each entity must apply to DAO to receive license NFT. DAO to determine which cohort category each licensee falls into.
22 |
23 | #### Table 1:
24 |
25 | Token licensing cost by cohort
26 |
27 | Benchmark // Startup / SME / Corporate // Vendor/Public
28 | ARR // 0-10m / 10-20m / 20-100m // 100m+ or vendor
29 | Cost // ~300 USD / ~3,000 USD / ~30,000 USD / ~300,000 USD
30 |
31 | ### Inflationary Rewards [4.2]
32 | When onchain activities are performed, RAIR is required using a mandatory facet in our diamond deployment contracts. This RAIR accrues to a development fund to support ongoing open source development. DAO will oversee use of funds to reward developers, pay bug bounties, fund new proposals, and the like. A governance structure is in place to ensure funds are efficiently spent to maximize the value of the network.
33 |
34 | An automated trade and execution bot will be deployed to recycle up to 1% of daily orderbook liquidity into Ethereum to accrue to a development fund. This ETH will be accrued by selling RAIR back into the open market, along with generating an inflationary reward.
35 |
36 | #### Emissions Curve [4.2.1]
37 | Each RAIR used onchain will generate new tokens sent 50% to the payer of the activity, and 50% to the development fund on an exponentially decreasing emissions curve.
38 |
39 | Users will only be able to receive rewards to an address that has a staked RAIR license. *E.g. RAIR must be burned into a soul bound NFT to accrue rewards.*
40 |
41 | Effectively this will create 3 periods of RAIR distribution.
42 | * An initial **inflationary** "mining" period where incentives are in place to generate more RAIR than it costs perform onchain activities
43 | * An **equilibrium** period where is effectively "free" to use onchain
44 | * And a **final** reduced rewards period where a terminal inflation rate takes over to incentivize ongoing development of the project at a sustainable level
45 |
46 | ### Token Distribution [4.3]
47 | RAIR was originally developed as a for-profit C-Corporation. Valueless grants of tokens will be airdropped to different cohorts that provided value to the project after a post TGE vesting period.
48 |
49 | These groups include:
50 | * C Corp Equity Investors (XX%)
51 | * P1/P2 Token Investors (XX%)
52 | * Developers (XX%)
53 | * Advisors (XX%)
54 | * Founders (XX%)
55 |
56 | ### Token Supply [4.4]
57 | 1,000,000,000 RAIR tokens will be generated at TGE.
58 | * P1 Tokens were valued at 15m initial fully diluted market cap (IFDM) in 2021
59 | * P2 Tokens were valued at 25m IFDM in 2022
60 |
61 | 2 tranches will be available at the 2024 token sale pre TGE via a liquidity bootstrapping protocol (LBP).
62 |
63 | * P3 Tokens 30m IFDM (1m USD equivalent)
64 | * P4 Tokens 35m IFDM (2.5m USD equivalent)
65 |
66 | Initial inflationary rewards period will generate new RAIR at a rate of 2x per deployed onchain activity for the first 800,000,000 RAIR processed through the system. *E.g. send 10 RAIR to deploy smart contract, receive 20 RAIR points from treasury.* This will generate a final fully diluted marketcap (FFDM) of 1.8b RAIR. Reward mechanism is designed to balance token distribution between early adopters and later participants.
67 |
68 | ### Points Accrual [4.5]
69 | Once FFDM is achieved, a 1x "free" period will match RAIR deployment costs for the final 800,000,000 RAIR processed through the system.*E.g. send 10 RAIR to deploy smart contract, receive 10 RAIR from treasury.*
70 |
71 | Finally, a terminal emissions rate of new RAIR will be determined by DAO governance not to exceed a 2% annual emissions rate once the 800m matching period is exhausted.*E.g. send 10 RAIR to deploy smart contract, receive XX<10 RAIR from treasury. OR send 10 RAIR, treasury burns X RAIR, etc tbd by DAO.*
72 |
73 | During this period, RAIR tokens will be earned through various value accretive onchain activies. Prior to receiving fungible tokens, users will accrue nontransferable wallet locked "points".
74 |
75 | At launch, there will be only 3 activities that count towards point accrual.
76 | * Minting NFT Licenses. RAIR points accrual for burning RAIR to mint licenses per ARR tranches listed in 4.1.1.
77 | * Deploying Smart Contracts. 10 RAIR per deployment.
78 | * Signing up for accounts by binding social logins. 10 RAIR per unique account.
79 |
80 | DAO will decide further points accrual activities after FFDM.
81 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | Apache License
2 | Version 2.0, January 2004
3 | http://www.apache.org/licenses/
4 |
5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6 |
7 | 1. Definitions.
8 |
9 | "License" shall mean the terms and conditions for use, reproduction,
10 | and distribution as defined by Sections 1 through 9 of this document.
11 |
12 | "Licensor" shall mean the copyright owner or entity authorized by
13 | the copyright owner that is granting the License.
14 |
15 | "Legal Entity" shall mean the union of the acting entity and all
16 | other entities that control, are controlled by, or are under common
17 | control with that entity. For the purposes of this definition,
18 | "control" means (i) the power, direct or indirect, to cause the
19 | direction or management of such entity, whether by contract or
20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 | outstanding shares, or (iii) beneficial ownership of such entity.
22 |
23 | "You" (or "Your") shall mean an individual or Legal Entity
24 | exercising permissions granted by this License.
25 |
26 | "Source" form shall mean the preferred form for making modifications,
27 | including but not limited to software source code, documentation
28 | source, and configuration files.
29 |
30 | "Object" form shall mean any form resulting from mechanical
31 | transformation or translation of a Source form, including but
32 | not limited to compiled object code, generated documentation,
33 | and conversions to other media types.
34 |
35 | "Work" shall mean the work of authorship, whether in Source or
36 | Object form, made available under the License, as indicated by a
37 | copyright notice that is included in or attached to the work
38 | (an example is provided in the Appendix below).
39 |
40 | "Derivative Works" shall mean any work, whether in Source or Object
41 | form, that is based on (or derived from) the Work and for which the
42 | editorial revisions, annotations, elaborations, or other modifications
43 | represent, as a whole, an original work of authorship. For the purposes
44 | of this License, Derivative Works shall not include works that remain
45 | separable from, or merely link (or bind by name) to the interfaces of,
46 | the Work and Derivative Works thereof.
47 |
48 | "Contribution" shall mean any work of authorship, including
49 | the original version of the Work and any modifications or additions
50 | to that Work or Derivative Works thereof, that is intentionally
51 | submitted to Licensor for inclusion in the Work by the copyright owner
52 | or by an individual or Legal Entity authorized to submit on behalf of
53 | the copyright owner. For the purposes of this definition, "submitted"
54 | means any form of electronic, verbal, or written communication sent
55 | to the Licensor or its representatives, including but not limited to
56 | communication on electronic mailing lists, source code control systems,
57 | and issue tracking systems that are managed by, or on behalf of, the
58 | Licensor for the purpose of discussing and improving the Work, but
59 | excluding communication that is conspicuously marked or otherwise
60 | designated in writing by the copyright owner as "Not a Contribution."
61 |
62 | "Contributor" shall mean Licensor and any individual or Legal Entity
63 | on behalf of whom a Contribution has been received by Licensor and
64 | subsequently incorporated within the Work.
65 |
66 | 2. Grant of Copyright License. Subject to the terms and conditions of
67 | this License, each Contributor hereby grants to You a perpetual,
68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69 | copyright license to reproduce, prepare Derivative Works of,
70 | publicly display, publicly perform, sublicense, and distribute the
71 | Work and such Derivative Works in Source or Object form.
72 |
73 | 3. Grant of Patent License. Subject to the terms and conditions of
74 | this License, each Contributor hereby grants to You a perpetual,
75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76 | (except as stated in this section) patent license to make, have made,
77 | use, offer to sell, sell, import, and otherwise transfer the Work,
78 | where such license applies only to those patent claims licensable
79 | by such Contributor that are necessarily infringed by their
80 | Contribution(s) alone or by combination of their Contribution(s)
81 | with the Work to which such Contribution(s) was submitted. If You
82 | institute patent litigation against any entity (including a
83 | cross-claim or counterclaim in a lawsuit) alleging that the Work
84 | or a Contribution incorporated within the Work constitutes direct
85 | or contributory patent infringement, then any patent licenses
86 | granted to You under this License for that Work shall terminate
87 | as of the date such litigation is filed.
88 |
89 | 4. Redistribution. You may reproduce and distribute copies of the
90 | Work or Derivative Works thereof in any medium, with or without
91 | modifications, and in Source or Object form, provided that You
92 | meet the following conditions:
93 |
94 | (a) You must give any other recipients of the Work or
95 | Derivative Works a copy of this License; and
96 |
97 | (b) You must cause any modified files to carry prominent notices
98 | stating that You changed the files; and
99 |
100 | (c) You must retain, in the Source form of any Derivative Works
101 | that You distribute, all copyright, patent, trademark, and
102 | attribution notices from the Source form of the Work,
103 | excluding those notices that do not pertain to any part of
104 | the Derivative Works; and
105 |
106 | (d) If the Work includes a "NOTICE" text file as part of its
107 | distribution, then any Derivative Works that You distribute must
108 | include a readable copy of the attribution notices contained
109 | within such NOTICE file, excluding those notices that do not
110 | pertain to any part of the Derivative Works, in at least one
111 | of the following places: within a NOTICE text file distributed
112 | as part of the Derivative Works; within the Source form or
113 | documentation, if provided along with the Derivative Works; or,
114 | within a display generated by the Derivative Works, if and
115 | wherever such third-party notices normally appear. The contents
116 | of the NOTICE file are for informational purposes only and
117 | do not modify the License. You may add Your own attribution
118 | notices within Derivative Works that You distribute, alongside
119 | or as an addendum to the NOTICE text from the Work, provided
120 | that such additional attribution notices cannot be construed
121 | as modifying the License.
122 |
123 | You may add Your own copyright statement to Your modifications and
124 | may provide additional or different license terms and conditions
125 | for use, reproduction, or distribution of Your modifications, or
126 | for any such Derivative Works as a whole, provided Your use,
127 | reproduction, and distribution of the Work otherwise complies with
128 | the conditions stated in this License.
129 |
130 | 5. Submission of Contributions. Unless You explicitly state otherwise,
131 | any Contribution intentionally submitted for inclusion in the Work
132 | by You to the Licensor shall be under the terms and conditions of
133 | this License, without any additional terms or conditions.
134 | Notwithstanding the above, nothing herein shall supersede or modify
135 | the terms of any separate license agreement you may have executed
136 | with Licensor regarding such Contributions.
137 |
138 | 6. Trademarks. This License does not grant permission to use the trade
139 | names, trademarks, service marks, or product names of the Licensor,
140 | except as required for reasonable and customary use in describing the
141 | origin of the Work and reproducing the content of the NOTICE file.
142 |
143 | 7. Disclaimer of Warranty. Unless required by applicable law or
144 | agreed to in writing, Licensor provides the Work (and each
145 | Contributor provides its Contributions) on an "AS IS" BASIS,
146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 | implied, including, without limitation, any warranties or conditions
148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 | PARTICULAR PURPOSE. You are solely responsible for determining the
150 | appropriateness of using or redistributing the Work and assume any
151 | risks associated with Your exercise of permissions under this License.
152 |
153 | 8. Limitation of Liability. In no event and under no legal theory,
154 | whether in tort (including negligence), contract, or otherwise,
155 | unless required by applicable law (such as deliberate and grossly
156 | negligent acts) or agreed to in writing, shall any Contributor be
157 | liable to You for damages, including any direct, indirect, special,
158 | incidental, or consequential damages of any character arising as a
159 | result of this License or out of the use or inability to use the
160 | Work (including but not limited to damages for loss of goodwill,
161 | work stoppage, computer failure or malfunction, or any and all
162 | other commercial damages or losses), even if such Contributor
163 | has been advised of the possibility of such damages.
164 |
165 | 9. Accepting Warranty or Additional Liability. While redistributing
166 | the Work or Derivative Works thereof, You may choose to offer,
167 | and charge a fee for, acceptance of support, warranty, indemnity,
168 | or other liability obligations and/or rights consistent with this
169 | License. However, in accepting such obligations, You may act only
170 | on Your own behalf and on Your sole responsibility, not on behalf
171 | of any other Contributor, and only if You agree to indemnify,
172 | defend, and hold each Contributor harmless for any liability
173 | incurred by, or claims asserted against, such Contributor by reason
174 | of your accepting any such warranty or additional liability.
175 |
176 | END OF TERMS AND CONDITIONS
177 |
178 | APPENDIX: How to apply the Apache License to your work.
179 |
180 | To apply the Apache License to your work, attach the following
181 | boilerplate notice, with the fields enclosed by brackets "[]"
182 | replaced with your own identifying information. (Don't include
183 | the brackets!) The text should be enclosed in the appropriate
184 | comment syntax for the file format. We also recommend that a
185 | file or class name and description of purpose be included on the
186 | same "printed page" as the copyright notice for easier
187 | identification within third-party archives.
188 |
189 | Copyright [yyyy] [name of copyright owner]
190 |
191 | Licensed under the Apache License, Version 2.0 (the "License");
192 | you may not use this file except in compliance with the License.
193 | You may obtain a copy of the License at
194 |
195 | http://www.apache.org/licenses/LICENSE-2.0
196 |
197 | Unless required by applicable law or agreed to in writing, software
198 | distributed under the License is distributed on an "AS IS" BASIS,
199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200 | See the License for the specific language governing permissions and
201 | limitations under the License.
202 |
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/EPS/RAIR Protocol Logo 2024-02.eps:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/EPS/RAIR Protocol Logo 2024-02.eps
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/EPS/RAIR Protocol Logo Black-02.eps:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/EPS/RAIR Protocol Logo Black-02.eps
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/EPS/RAIR Protocol Logo White-02.eps:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/EPS/RAIR Protocol Logo White-02.eps
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/JPG/RAIR Protocol Logo 2024.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/JPG/RAIR Protocol Logo 2024.jpg
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/JPG/RAIR Protocol Logo Black 2024.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/JPG/RAIR Protocol Logo Black 2024.jpg
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/JPG/RAIR Protocol Logo Color.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/JPG/RAIR Protocol Logo Color.jpg
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/JPG/RAIR Protocol Logo White 2024.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/JPG/RAIR Protocol Logo White 2024.jpg
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/PNG/RAIR Protocol Logo 2024.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/PNG/RAIR Protocol Logo 2024.png
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/PNG/RAIR Protocol Logo Black.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/PNG/RAIR Protocol Logo Black.png
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/PNG/RAIR Protocol Logo White.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/PNG/RAIR Protocol Logo White.png
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/EPS/RAIR SQ Symbol Logo-Black.ai:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/EPS/RAIR SQ Symbol Logo-Black.ai
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/EPS/RAIR SQ Symbol Logo-Black.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/EPS/RAIR SQ Symbol Logo-Black.jpg
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/EPS/RAIR SQ Symbol Logo-Color.eps:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/EPS/RAIR SQ Symbol Logo-Color.eps
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/EPS/RAIR SQ Symbol Logo-White.ai:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/EPS/RAIR SQ Symbol Logo-White.ai
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/EPS/favicon6.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/EPS/favicon6.ico
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/JPG/RAIR SQ Symbol Logo-Color-BlkBkGrd.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/JPG/RAIR SQ Symbol Logo-Color-BlkBkGrd.jpg
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/JPG/RAIR SQ Symbol Logo-Color.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/JPG/RAIR SQ Symbol Logo-Color.jpg
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/JPG/RAIR SQ Symbol Logo-White-BlkBkGrd.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/JPG/RAIR SQ Symbol Logo-White-BlkBkGrd.jpg
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/PNG/RAIR SQ Symbol Logo-Black.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/PNG/RAIR SQ Symbol Logo-Black.png
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/PNG/RAIR SQ Symbol Logo-Color.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/PNG/RAIR SQ Symbol Logo-Color.png
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/PNG/RAIR SQ Symbol Logo-White.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/RAIR R Symbol Only/PNG/RAIR SQ Symbol Logo-White.png
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/SVG/RAIR SQ Symbol Logo-Black.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
72 |
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/SVG/RAIR SQ Symbol Logo-Color.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
92 |
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/RAIR R Symbol Only/SVG/RAIR SQ Symbol Logo-White.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
72 |
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/SVG/4F3F6E0BBA68FA90.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/rairprotocol/RAIRdocs/4cde7479283afc703c1d51999986c69cb874ff13/RAIRprotocol Brand Kit/SVG/4F3F6E0BBA68FA90.jpg
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/SVG/RAIR Protocol Black 2024.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
328 |
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/SVG/RAIR Protocol Logo 2024-02.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
613 |
--------------------------------------------------------------------------------
/RAIRprotocol Brand Kit/SVG/RAIR Protocol White 2024.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
329 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # RAIR Open License Protocol (DRAFT)
2 |
3 | *not final, tbd final tokenomics*
4 |
5 | ## Abstract
6 | > The RAIR web3 infrastructure stack enables the creation of scalable Dapps through an open token licensing model. The RAIR open token license inherits the Apache 2.0 methodology by requiring a NFT license to be included inside the source License.md file. Used together or independently, the licensed RAIR codebase allows developers to build their own independent NFT marketplace and DRM infrastructure with all relevant smart contracting, account creation, and scalable offchain cloud management logic.
7 |
8 | Table of Contents
9 | =================
10 |
11 | - [ ] [1. Introduction](#1-Introduction)
12 | - [ ] [History [1.1]](#History-11)
13 | - [ ] [State of Web3 [1.2]](#State-of-Web3-12)
14 | - [ ] [RAIR [1.3]](#RAIR-13)
15 |
16 | - [ ] [2. RAIR Open Source Codebase](#2-RAIR-Open-Source-Codebase)
17 | - [ ] [RAIRsolidity [2.1]](#RAIRsolidity-21)
18 | - [ ] [RAIRnode [2.2]](#RAIRnode-22)
19 | - [ ] [RAIRfrontend [2.3]](#RAIRfrontend-23)
20 | - [ ] [RAIRmedia [2.4]](#RAIRmedia-24)
21 | - [ ] [RAIRsync [2.5]](#RAIRsync-25)
22 | - [ ] [RAIRinfra [2.6]](#RAIRinfra-26)
23 |
24 | - [ ] [3. Open Token Licensing Model](#3-Open-Token-Licensing-Model)
25 | - [ ] [Licensing [3.1]](#Licensing-31)
26 | - [ ] [Permissive Licenses [3.2]](#Permissive-Licenses-32)
27 | - [ ] [Apache 2.0 [3.3]](#Apache-20-33)
28 | - [ ] [Risks and Benefits [3.4]](#Risks-and-Benefits-34)
29 |
30 | - [ ] [4. Tokenomics](#4-Tokenomics)
31 |
32 | * [Acknowledgements](#Acknowledgements)
33 | * [References](#References)
34 |
35 |
36 | ----------------
37 |
38 | ## 1. Introduction
39 | The business model of the internet hinges on the interplay of proprietary and open source. In the typical model, an enterprise develops an open source underlying codebase, that is then monetized by a centralized for profit corporation.
40 |
41 | ### History [1.1]
42 | Redhat Linux pioneered this model in the late 1990s, much to the chagrin of Linux core developers. Despite a valiant effort to reward Linux contributors with shares of stock in the Redhat corporation, the systems for compensating open source development remain controversial.[1](#References)
43 |
44 | In the web2 era, proprietary moats developed using the underlying rails of HTTP:// and other core protocols. While users rely on the open internet to access the FAANG behemoths, in web2 no monetization inherently accrues to the maintainers of the underlying protocols.
45 |
46 | ### State of Web3 [1.2]
47 | With the rise of public persistent data (aka blockchain) the monetization of open source entered a new "Web3" era.
48 |
49 | Developers believing in the protocol, for the first time could be compensated in the native unit of the protocol. Either by purchasing tokens directly, or through increasingly sophisticated grant mechanisms. By 2016, this thesis was codified into the seminal blog post "Fat Protocols [2](#References) where the author posits open source protocol tokens will solve the Redhat vs Linux compensation and incentive issue.
50 |
51 | Fast forward to 2024, and it is mandatory for the core protocol layers of Web3 (L1/L2 blockchains, Oracles, DA, Restaking, etc) to be open source to be trusted. //However// the Dapps built on top of Web3 are largely NOT. The VC model to fund teams that take open source infrastructure to then build proprietary business logic moats on top of is still alive and well.[3](#References) Conjecture.. the development of Web3 killer Dapps is being stymied by this proprietary smothering.
52 |
53 | ### RAIR [1.3]
54 | The RAIR protocol has been in active development since 2019 as an investor backed enterprise SaaS product. In 2024, the entire RAIR Codebase is available for the first time via an open source Apache 2.0[4](#References) token licensing model.
55 |
56 | Throughout this whitepaper, we will articulate our reasoning for going fully open source, and expound upon our token licensing model to reward the development of the RAIR token supported Dapp layer.
57 |
58 | ----------------
59 |
60 | ## 2. RAIR Open Source Codebase
61 | The RAIR codebase comprises 6 primary microservices that help Dapps deploy and scale. Used together or independently, this code base allows developers to build their own independent NFT marketplace and DRM infrastructure with all relevant smart contracting, account creation, and scalable offchain cloud management logic.
62 |
63 | All source code and a full explanation of functionality is available on the RAIRprotocol Github. github.com/rairprotocol
64 |
65 | ### RAIRsolidity [2.1]
66 | Granular onchain NFT minting, royalty, resale, fungible token credit, and marketplace logic via ERC2535 upgradeable diamond multi-proxy contracts. Native EVM support for mainnet ETH, Astar, BSC, Matic + Testnets. Documentation for needed OpenZeppelin, Hardhat, etc deployment. Fully verified on Etherscan and relevant block explorers.
67 |
68 | ### RAIRnode [2.2]
69 | Backend to create your own modular API endpoints and offchain infrastructure. Environment variables and full open source Docker image repository allows developers to quickly spin up their own backend infrastructure by inputting relevant paths and API keys.
70 |
71 | * Many critical out-of-the-box integrations can be deployed via API environment variables including: AA wallets, Yoti AI facial scanning, MongoDB Cloud Atlas, Hashicorp vault, Filebase.
72 |
73 | ### RAIRfrontend [2.3]
74 | Deploy customizable mobile first NFT marketplace frontends using modular REACT + Typescript framework. UIs to manage smart contract creation, user, DRM, metadata, UI/UX.
75 |
76 | ### RAIRmedia [2.4]
77 | DRM protect content with a full FFmpeg encoder/transcoder. Store credentials to database or vault cluster. Store streaming data to IPFS or Cloud.
78 |
79 | ### RAIRsync [2.5]
80 | Specify all smart contract addresses to sync via Alchemy syncing engine. Supply Alchemy API key for native deployment. Extensible to other syncing infrastructure (Moralis et al).
81 |
82 | ### RAIRinfra [2.6]
83 | Core to the RAIR value proposition is our full open sourcing of our cloud infrastructure tooling. While most projects stop at revealing the intricacies of their proprietary cloud setups, RAIR is committed to fully open sourcing all aspects of our knowledge base. This includes: Terraform scripts, CI/CD pipeline, Kubernetes configurations.
84 |
85 | ----------------
86 |
87 | ## 3. Open Token Licensing Model
88 | RAIR is fully open sourcing 4 years and 2.5m USD+ of proprietary enterprise SaaS development. This means you can deploy, modify, and extend your own API endpoints on your own cloud.
89 | * RAIR C corp can assist with enterprise implementation on a SaaS/consulting basis.
90 | * RAIR DAO licenses all source code natively via soul-bound NFT tokens in exchange for burning RAIR tokens.
91 |
92 | ### Licensing [3.1]
93 | To review, software licenses come in 2 primary flavors: proprietary and permissive. Proprietary = copy our code and we can take legal action. Permissive = copy our code without the proper attribution, and we can take legal action.
94 | ### Permissive Licenses [3.2]
95 | While not exhaustive, the following permissive licenses are the most widely used. Reasons will be given below for RAIR protocol NOT using the following licenses.
96 | * MIT: Attribution is not rigorous enough as there is no public changelog requirement.
97 | * BSD (Berkeley Software Distribution): Custom rules make this license too broad to perform standardized enforcement.
98 | * GPL (GNU Public License): Changelog requirement is good, though no requirement for inclusion of source License.md like Apache 2.0
99 | * MPL (Mozilla Public License): License contamination through the automatic inheritance of GPL prevents licensing by proprietary entities.
100 |
101 | ### Apache 2.0 [3.3]
102 | The Apache 2.0 license requires two critical components necessary for an NFT open licensing model.
103 | * Public Changelog. If code is modified, publish the modifications publicly.
104 | * Inherited disclosure of license.Include the //***original***// License.md file into all derivative works.
105 |
106 | Taken together, these two properties form the basis for the RAIR protocol NFT license model. *E.g. Open source license is valid as long as a valid NFT exists inside of the license.md*
107 |
108 | ### Risks and Benefits [3.4]
109 | Benefits of this open source model include:
110 | * Trust in fully transparent source code. No black boxes.
111 | * Developer recognition and renumeration via token
112 | * Increased development speed for all of Web3. No rebuilding wheels
113 |
114 | The primary risk that prevents most Dapps from fully open sourcing their code base is the theft risk. Years and millions of dollars of IP can be forked without crediting the original creators. This risk is still present in an open token licensing model. The design of the token system must ensure the benefits of obtaining a license outweigh the costs both financial and reputational for stealing.
115 |
116 | ----------------
117 |
118 | ### 4. Tokenomics
119 |
120 | See dedicated tokenomics paper
121 |
122 | ----------------
123 |
124 | ## Acknowledgements
125 |
126 | The RAIR system is only possible thanks to years of hard work and dedication from our core development team. As RAIR transitions to a fully open source Dapp, these team members will be critical to steward the codebase into a prosperous future.
127 |
128 | @JuanMiguel
129 | @SeanMichaels
130 | @ChrisRose
131 | @MashaMitkov
132 | @ZephAlcala
133 | @SureshArora
134 | @Vino
135 | @BrianBorg
136 | @Valerii
137 | @Kat
138 | @Edprado
139 | @Martincasado
140 |
141 | ----------------
142 |
143 | ## References
144 |
145 | * [1] Stephen Shanklan. Late IPO change left many red-faced — cnet.com, 1 2002. https://www.
146 | cnet.com/tech/tech-industry/late-ipo-change-left-many-red-faced/
147 | * [2] Joel Monegro. Fat Protocols, 8 2016. https://www.usv.com/writing/2016/08/fat-protocols/
148 | * [3] Alana Edgin. Texas Tech alum sells Tronic, Web3 innovator, for $12.25 billion, 3-2024. https://www.lubbockonline.com/story/business/2024/03/15/texas-tech-alum-sells-tronic-web3-innovator-for-12-25-billion/72971130007/
149 | * [4] Apache Foundation. APACHE LICENSE, VERSION 2.0, 1 2004. https://www.apache.org/licenses/LICENSE-2.0
150 |
--------------------------------------------------------------------------------