Architecture - OLD

Blockchain Software Architecture

Table Of Contents

  1. Introduction 4 1.1 Purpose 4 1.2 Overview 4

  2. Architectural Representation 5

  3. Architectural Goals and Constraints 5

  4. Use-Case View 6 4.1 Use-Case Realizations 7

  5. System workflow 9

  6. Deployment View 9

  7. Implementation View 10

  8. Make, buy or re-use Consideration 10

1. Introduction

This document describes the architecture and design of the OODLZ application broken down into several key modules.

1.1. Purpose

This document provides a comprehensive architectural overview of the system, using a number of different architectural views to depict different aspects of the system. It is intended to capture and convey the significant architectural decisions that have been made on the system.

1.2. Overview

This document has several sections:

  • ARCHITECTURAL REPRESENTATION: This section describes what software architecture is for the current system, and how it is represented.

  • ARCHITECTURAL GOALS AND CONSTRAINTS: This section describes the software requirements and objectives that have some significant impact on the architecture

  • USE-CASE VIEW: This section lists user cases or scenarios from the use-case model if they represent some significant, central functionality of the final system.

  • SYSTEM WORKFLOW: This section describes the system's sequence of tasks that processes a set of data, providing the required functionalities.

  • DEPLOYMENT VIEW: This section describes one or more physical network (hardware) configurations on which the software is deployed and run.

  • IMPLEMENTATION VIEW: This section describes the overall structure of the implementation model, organization of static software modules, the decomposition of the software into source files and subsystems in the implementation model, and any architecturally significant components.

  • MAKE, BUY OR REUSE CONSIDERATION: This section provides an evaluation whether the product components should be developed, purchased, or reused based on established criteria.

2. Architectural Representation

3. Architectual Goals And Constraints

OODLZ Balance

The OODLZ-Balance is the basis by which the entire OODLZ Application is based.

OODLZ uses a tiered LEVEL system by which the more funds users have in their balance, the higher the user level and the more rewards and discounts they receive from all other products/modules offered via the OODLZ App.

When a user deposits FIAT, say USD, the OODLZ Application will auto-convert that to UST. OODLZ will utilize Automatic Market Makers (AMMs) to secure yield which is how OODLZ makes money and how OODLZ can provide an APY return to their users.

The OODLZ Application main menu (Wallet) will provide three main functions for funds/token transfer and one for getting updates:

  • Deposit funds: deposit (fiat), convert to stable coin, and earn interest via Defi.

  • Withdraw funds: stop earning, convert stable coin to fiat, and withdraw to fiat money.

  • Transfer funds: sending funds to other OODLZ-Products such as OODLZ-Invest or OODLZ-Lend, or in/out of FIAT-based accounts such as VISA/MASTERCARD Debit or Credit accounts. *Transfer features can only be worked on once new products and card integrations are approved.

  • Get earning updates: Retrieve interests and current balance.

OODLZ Cashback (fiat & crypto)

OODLZ Cashback is a traditional cashback system (Affiliate Marketing) where retailers reward users with a percentage of the user's spend.

This system will be provided by 3rd party EnactOn. EnactOn will provide the frontend and backend for this cashback service including updating the design to the new OODLZ design Sotatek is working on.

Once the Affiliate Networks (The Retailers) pay OODLZ the user's commission, OODLZ will pass on a percentage of this commission to the users via the OODLZ App.

OODLZ will add this commission to the user OODLZ Balance which auto-converts FIAT to Stable, so the user can benefit from the APY returns the OODLZ Balance offers - see OODLZ Balance.

OODLZ Token

OODLZ will reward users with the OODLZ Token (OODL) when cashback is received. This creates more demand for holding the token and increases its value.

The OODLZ Application will allocate a % of OODL token every time the user gets paid cashback to their Balance and the % of OODL token is dictated by the user's Balance-Level.

Constraints

Securities of the software must be held at maximum, follow all rules and principles of the blockchain. Stored data must be decentralized, no centralized storage or generation of user’s private keys.

4. Use-Case View

4.1. Use-Case Realizations

5. System Workflow

6. Deployment View

7. Implementation View

8. Make, Buy or Re-Use Consideration

Last updated