📜Whitepaper

The RAIR web3 infrastructure stack enables the creation of scalable Dapps through an open token licensing model.

Abstract

The RAIR open token license inherits the Apache 2.0 methodology by requiring a NFT license to be included inside the source NOTICE 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.

Introduction

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.

History

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

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.

State of Web3

With the rise of public persistent data (aka blockchain) the monetization of open source entered a new "Web3" era.

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 where the author posits open source protocol tokens will solve the Redhat vs Linux compensation and incentive issue.

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 Conjecture.. the development of Web3 killer Dapps is being stymied by this proprietary smothering.

RAIRprotocol

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 token licensing model.

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.

Open Token License

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.

  • RAIR C corp can assist with enterprise implementation on a SaaS/consulting basis.

  • RAIR DAO licenses all source code natively via soul-bound NFT tokens in exchange for burning RAIR tokens.

Licensing

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.

Permissive Licenses

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.

  • MIT: Attribution is not rigorous enough as there is no public changelog requirement.

  • BSD (Berkeley Software Distribution): Custom rules make this license too broad to perform standardized enforcement.

  • GPL (GNU Public License): Changelog requirement is good, though no requirement for inclusion of source License.md like Apache 2.0

  • MPL (Mozilla Public License): License contamination through the automatic inheritance of GPL prevents licensing by proprietary entities.

Apache 2.0

The Apache 2.0 license requires two critical components necessary for an NFT open licensing model.

  • Public Changelog. If code is modified, publish the modifications publicly.

  • Inherited disclosure of license.Include the //original// License.md file into all derivative works.

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 NOTICE file

Risks and Benefits

Benefits of this open source model include:

  • Trust in fully transparent source code. No black boxes.

  • Developer recognition and renumeration via token

  • Increased development speed for all of Web3. No rebuilding wheels

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.

Acknowledgements

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.

@JuanMiguel @SeanMichaels @ChrisRose @MashaMitkov @ZephAlcala @SureshArora @Vino @BrianBorg @Valerii @Kat @Edprado @Martincasado

References

Last updated