Skip to main content

Orivon Ecosystem

Here we explain the foundations of the Orivon Ecosystem

Remember that Implementations are subject to feedbacks and discussions for improvement (Contribution flow)
If you want to start a discussion to bring a topic/idea for improvement you can discuss it within the Orivon Discord
Such discussions engages particularly the interest from the Founder and the Elite Team due to its relevance

Every once and then you will find "From Technical Design" fields
These indicates what's the current Technical Design idea of that part of implementation

Technical Design is more a flexible and fully depends on these core Implementation specifications
Furthermore Technical Design is the last layer before the actual code implementation

Ecosystem​

Orivon aims to establish new Internet standards for Web3 to make it viable for mass adoption
For that reason, Orivon aims to offer a versatile and cross compatible solution for devs and users trough an Orivon Ecosystem

The main pillar for the Orivon Ecosystem is the Orivon Modules support
Which is a way to let developers, apps and programs quickly add support for Orivon modules

Based on the Modules System, it leads us to our 2 main products willing to be the core of Orivon widespread adoption:

These components are what makes the Orivon idea actually usable from the first big portion of public.

Orivon Modules support specifically, is a very powerful layer allowing to add support for Orivon Modules on every environment other than Orivon Browser, such as curl, CLI, hardware wallets, mobile etc...

Thus allowing devs to write cross compatible modules able to work on almost everywhere Orivon Modules does, giving huge improvement to developers experience

These benefit follows the users because they automatically get access to more Web3 products on more environments

Then Orivon Browser and Mobile Implementation do their part to spread Orivon making it practically viable for everyone with immense benefits