Dual-Chain Operational Mechanism

Urgent operates on a dual-chain architecture comprising Urgent One Chain and Urgent Union Chain, each playing distinct but interlinked roles. These two blockchains are seamlessly connected through the Confidential Transfer Protocol (CTP) and Inter-Blockchain Communication (IBC), ensuring data integrity, privacy, and performance scalability.

1. Urgent One Chain: Public User-Facing Layer

1.1 Chain Characteristics

• Consensus: Proof-of-Stake (PoS)
• Execution Layer: ZKVM (Zero-Knowledge Virtual Machine)
• Native Token: $URT
• Data Sharding: User and transaction data are encrypted and fragmented across validator and archive nodes.
• Interoperability: Full IBC compliance (EVM and Cosmos-compatible)

1.2 CTP-Enabled DApp Ecosystem

Urgent One Chain serves as the public interaction layer for users and enterprises, allowing encrypted settlements, decentralized application (DApp) deployment, and on-chain visibility.

Key Features:

• Order = Transaction Hash: Every user order is stored as a blockchain transaction hash, eliminating the need for a separate order system.
• Public On-Chain Access: Explorers display transaction-level metadata (e.g., payment amounts, encrypted fields) that link to user and enterprise interactions.
• Encrypted Order Data: Includes encrypted name, address, and product information, signed with the user's wallet.
• CTP Protocol Transfer: Bundles user public key with the order, enabling secure, end-to-end encrypted forwarding to the Union Chain.

1.3 Typical Workflow:

1. User places an order in an enterprise DApp.
2. Smart contract accepts encrypted user input and payment.
3. Transaction hash is generated and returned as order ID.
4. Metadata is published to chain; private fields remain encrypted.
5. Encrypted package is forwarded via CTP and IBC.

---

2. Urgent Union Chain: Consortium-Level Infrastructure

Urgent Union Chain is a permissioned blockchain that supports enterprise-level data control, performance scalability, and regulated decryption workflows.

2.1 Node Hierarchy

• Root Node (managed by Urgent Network):

  • Central policy enforcement and metadata inspection
  • Stateless; does not store user data permanently

• Secondary Nodes (operated by trusted partners):

  • Improve network performance and lower latency
  • Cache encrypted payloads temporarily
  • Charged as premium services (3% commission to Urgent Network)

• Edge Nodes (enterprise access layer):

  • Entry nodes connecting Union Chain to enterprise IT systems
  • Subscription-based; include built-in RPC endpoints

2.2 CTP Confidential Transfer Workflow

1. Encrypted payloads from One Chain are transferred via IBC and CTP to the Union Chain Root Node.
2. Root Node verifies metadata and routes to secondary and edge nodes.
3. Temporary data storage happens in a Transient Memory Layer (TML).
4. Edge Nodes forward payloads to enterprise-controlled databases.

---

3. End-to-End Decryption Flow

Enterprises must acquire user consent for decryption. The mechanism ensures that plaintext is never exposed to the blockchain layer.

1. Enterprise initiates a decryption request to the Root Node.
2. Root Node relays the request to Urgent One Chain smart contract.
3. User confirms the request by re-signing through their wallet.
4. CTP module encrypts the decrypted content using Fully Homomorphic Encryption (FHE).
5. The FHE-wrapped ciphertext is returned via Root Node and decrypted only in the enterprise's secure compute layer.

This guarantees:

• Zero-trust compliance: Root Node cannot access decrypted content.
• Privacy-by-design: Users maintain complete control of sensitive data.
• Auditability: Consent events are recorded on-chain.

---

4. Technical Advantages

Feature	Traditional Blockchain	Urgent Network Dual Model
Identity Binding	Basic, externalized	On-chain zk-bound via CTP
Private Data Flow	Off-chain/manual	Encrypted, on-chain & auditable
Enterprise Integration	Limited or fragmented	SDK-based, fully composable
Decryption Governance	Lacking	Dual-consent model w/ traceability
Developer Experience	Low-level, multi-API	Unified SDK with IBC support

---

5. Use Case: Privacy-Preserving Logistics Handoff

A real-world cross-border logistics scenario demonstrates Urgent Network's unique capabilities:

5.1 User Side

• The user submits encrypted order details (name, address, product) through an enterprise DApp.
• The contract accepts stablecoin payment and generates a transaction hash.
• This hash functions as a tamper-proof order ID and metadata pointer.

5.2 Enterprise Side

• Receives encrypted payload via CTP from One Chain.
• Stores data securely; cannot decrypt without user's re-signature.
• When needed (e.g., dispatch or regulation), enterprise initiates Root Node relay and user re-authorization.

5.3 Delivery Chain

• Logistics A (Domestic Dispatch): Can see product type and target port only.
• Logistics B (Maritime Carrier): Sees origin and destination regions, no address.
• Logistics C (Last-Mile Carrier): Accesses full address to complete delivery.
• This selective disclosure ensures that only the final logistics company can access sensitive data, minimizing risk.

5.4 User Query System

• Users can query any order by its transaction hash.
• The system displays logistics chain actors and current package location.
• Real-time updates are pushed at every critical checkpoint.

This granular visibility plus selective information flow ensures privacy and traceability across complex logistics networks.