Architecture
The DRESSdio Bridge architecture is composed of four primary components: EVM-compatible smart contracts, Oracle services, a messaging layer, and a private chain interface. Each component is tightly integrated to ensure the security and scalability of the bridge.
1. EVM-Compatible Smart Contracts
Role of Smart Contracts: EVM-compatible smart contracts handle the locking and unlocking of DRESS tokens on the public chain (Ethereum network). These contracts act as the main gateway for processing user requests to convert DRESS tokens into DP.
Functional Elements:
Oracle-based Liquidity Pool Mechanism: The DRESSdio platform operates an oracle-based liquidity pool that applies price volatility without third-party intervention to support the stable interchange of DPs that maintain a fixed value to represent the price of physical products and DRESS whose price fluctuates on the exchange. The liquidity pool is built with DRESS liquidity provided by the platform and DPs issued based on it, and when a user places tokens in the liquidity pool and requests an exchange for another token, it is exchanged and provided based on the price provided by the oracle. A DP fee is deducted from every exchange, which goes into the liquidity pool."
: DRESS Price per unit of exchange
: Real-time market pricing from Oracle
f(V) : Percentage adjusted by liquidity protection mechanisms such as slippage adjustment, daily trading limits, etc. that are adjusted based on trading volume (V) with dynamic adjustment functions
Security Mechanisms:
Multi-signature Wallet: Critical functions of the smart contract, such as locking and unlocking assets, are approved through a multi-signature wallet to prevent a single point of failure.
Upgradeable Smart Contracts: The smart contracts are designed to be securely upgradeable, allowing for the addition of new features or security patches as needed.
2. Oracle Service
Role of the Oracle: The Oracle service plays a crucial role in relaying price data, transaction statuses, and other key information between the public and private chains. This is essential for maintaining the reliability of bridge operations.
Functional Elements:
Price Feeds: The Oracle provides real-time price data needed to determine the swap ratio between DRESS and DP. It collects data from multiple price feeds, averages it, and relays it to the bridge.
State Relay: The Oracle detects specific events on the public chain (e.g., DRESS token transfer) and relays this information to the private chain, triggering the issuance of DP.
Security Mechanisms:
Decentralized Oracle Network: The Oracle operates through a decentralized network, reducing the risk of single-point failures and data manipulation.
Encrypted Communication: All communication between the Oracle and smart contracts is encrypted to prevent data leaks and tampering.
3. Messaging Layer
Role of the Messaging Layer: The messaging layer serves as a secure and reliable communication channel for transmitting data between the public and private chains. It relays transaction statuses and events in real-time between the two chains.
Functional Elements:
Event Listener: The messaging layer detects and records all relevant events occurring on both chains in real-time. For instance, When a DRESS token is moved from the public chain to the WaaS, the messaging layer detects it and passes that information to the private chain.
Verification and Validation: It ensures that each message is accurately transmitted between the two chains and verifies the integrity of the data.
Security Mechanisms:
Message Signing: All messages transmitted by the messaging layer are signed to ensure their origin and integrity.
Dual Authentication Channels: Messages related to critical events are sent through dual authentication channels to prevent untrusted messages from being transmitted between the chains.
Last updated
Was this helpful?