Solution: dc/sl

Tradables solution utilizes our three core systems:

1. Shared Liquidity Hub(SL)

2. App-specific Modules- Distributed Compute(DC)

3. Omnichain IDs

The SL secures apps built on our system through the economic security of assets restaked in our Shared Liquidity Vault, while App Modules distribute user trading compute among other modules in the system, allowing apps and blockchains to tap into an omnichain shared liquidity.

Omnichain IDs are unique IDs assigned to user accounts by the controller, which allows them to deposit on entirely different applications on our network, sometimes from more than one chain, and be able to perform complex financial actions on other apps in our system without:

An example of this would be: Users can easily stake in our shared liquidity hub on (app A) and borrow a different asset on (app B) built on (Chain C) while arbitraging funding rates on DEXes D and E without moving their capital.

Apps must run as their base chain and to connect to Tradable's omnichain IDs. The base contracts function as the central intelligence of our system, overseeing critical operations such as tapping into the Shared Liquidity Module, Omnichain balance management and communication, app-specific agreements, and various configurations utilized across all smart contracts within our ecosystem, regardless of the chain they reside on.

For users who want to allow fresh deposits from users without omnichain IDs in their system, the side chain or side vault is the primary interface for collecting and managing liquidity deposited into their system. These smart contracts serve as gateways into apps built within the system and are deployed on all chains where developers want their services offered.

Sidechains gather user inputs related to Omnichain deposits and withdrawals in any form within different application use cases and other functionalities. Subsequently, each function executed on the side vault is encoded and relayed to the base chain using the Layerzero messaging layer for further processing and storage of information.

TradableBalanceVault [Base Contract]:

This contract is a versatile repository responsible for storing and managing user balances within the system.

TradableMarginHandler [Base Contract]:

The TradableMarginHandler contract orchestrates the intricate logic governing all constraints and conditions concerning user account deposits and withdrawals.

TradableSettings [Base Contract]:

TradableSettings is pivotal in managing and preserving all configuration variables essential for the seamless operation of the base-chain sidechain model. It is a centralized hub for setting and storing crucial parameters across the entire ecosystem.



TradableStaking [Base Contract]:

Responsible for managing staking-related operations at the base chain level, TradableStaking plays a critical role in facilitating liquidity provision. It governs the allocation of rewards and dictates the frequency at which they are disbursed.



TradableSettingsMessageAdapter [Base Contract]:

TradableSettingsMessageAdapter is a pivotal bridge that oversees the inflow and outflow of messages to and from the base chain. It executes pertinent response functions based on the transmitted messages, ensuring seamless communication within the ecosystem.