deWeb Architecture

The deWeb Framework consists of three core components: User Authentication, Royalty Distribution and Token Engine.

 

User Authentication

This component handles the following:

User Sign-Up & Sign-In

Users create virtual accounts on EOS mainnet

Social sign-in support for all major social platforms and SMS

Users are associated to Marketers via the domain they use to sign-up

Interoperability

Support for cross-Operator and cross-Marketer transactions

Marketers

Configure their domains:

Language

deApps

Marketers are associated to Operators based on their domains

Account recovery

Marketers can recover accounts for users 

Operators can recover accounts for Marketers

Users can migrate between Marketers

Marketers can migrate between Operators

Royalty Engine

Every deApp needs a source of revenue. When revenue is received, it gets passed to the royalty engine and immediately gets divided between deWeb, Developers, the Operator and the Marketer that provided service to the user.

For example:

In this case, the revenue generated will be split:
30% to the three developers
20% to the Operator
45% to the Marketer 
5% deWeb

deWeb takes a 5% royalty for use of the deWeb Framework

The Operator selected by the Marketer charges 20% royalties

The Marketer leverages three deApps which charge 10% royalties each for a total of 30%

A Marketer running a service charges a fee from their customers 

 

Token Engine

The Token Engine is both a stand-alone deApp as well as a core module that can be used by other deApps. It currently enables:

Issuing Bancor Liquid Tokens on EOS with a USDB stablecoin reserve - at no cost to the token issuer

Buying/Selling tokens using credit cards, EOS, BTC, ETH, LTC and more

Transferring tokens between users

Token holder directories

Setting token weekly allowance:

If the allowance is off (set to 0%) then the token price will remain stable at $1

If the allowance is on (for example set to 2%) then:

The token will emit 2% of the reserve on a weekly basis, generating a recurring source of income to the token issuer. The income is subject to fees that are processed by the Royalty Engine and paid to service providers.

There are two ways value can get passed from the token to the Royalty Engine:

Burn

When a token is burned, the USDB stable coin in reserve gets passed to the Royalty Engine.

Allowance

As allowance removed value from the reserve, that reserve gets passed to the Royalty Engine.

 

Token Engine deApp

The Token Engine is both a stand-alone deApp as well as a core module that can be used by other deApps. It currently enables:

Tokens

There are currently three types of tokens available for creation.

Stable

Reserve is always 100%.  Value gets passed to the Royalty Engine via token burn.