A-Field Tech
AFT Console Login
  • Welcome to console.a-fieldtech.com
    • Console Login Page
  • Getting Started
    • Quickstart
    • Dashboard
  • Compute Power
    • Model Overviews
    • Create a Elastic Compute Service (ECS) - General Deployment Model
    • BMS (Bare Metal Server) Overview
    • Lightweight Elastic Compute Deployment Model (LECS)
    • Compute Management
    • Security
      • Generating an SSH Key Pair
    • ECS Models Reference
  • Network
    • Create a CIDR Block
    • Connectivity
    • Anti-DDoS Bandwidth Protection
  • TECH BLOG
    • This is the A-Field Tech - Tech Blog
      • Building Resilient Crypto Trading with Ultra-Low Latency (ULL): A Dual-Connection Setup for Speed an
      • Optimizing Crypto Connectivity: A Cost-Effective, Flexible Alternative to Cloud Dependency
      • Building Web3 Applications on Decentralized Edge Computing: A Hong Kong Case Study
Powered by GitBook
On this page
  • Introduction
  • Infrastructure Setup: Our decentralized cloud infrastructure consists of three crucial nodes:
  • Setup - Architecture
  • Setup - High Level Flowchart
  • Test Case Analysis:
  • The Setup
  • Testing 1 Results
  • Testing 2 Results
  • Key Advantages:
  • Conclusion
  • Our Web 3 Use Cases
  • Decentralized Document Verification System
  • NFT Marketplace with Regional Focus
  • Supply Chain Traceability
  • Digital Identity Management
  • Decentralized Content Distribution
  1. TECH BLOG
  2. This is the A-Field Tech - Tech Blog

Building Web3 Applications on Decentralized Edge Computing: A Hong Kong Case Study

PreviousOptimizing Crypto Connectivity: A Cost-Effective, Flexible Alternative to Cloud Dependency

Last updated 4 months ago

Introduction

The evolution of cloud computing is taking an exciting turn towards decentralization, particularly in the Web3 space. In this technical exploration, we'll dive into how we leveraged a decentralized edge computing platform across Hong Kong and the Greater Bay Area (GBA) to deploy and test Web3 applications.

Infrastructure Setup: Our decentralized cloud infrastructure consists of three crucial nodes:

  1. IPFS Node: Handles decentralized storage

  2. Optimistic (OP) Node: Manages Layer 2 to Layer 1 operations

  3. Ethereum Node: Interfaces with the Ethereum blockchain

3 x compute nodes builded from A-Field Tech Cloud Console

Each node has both private and public network addresses. Backend transactions occur within the private network, while the public addresses are used for frontend access.

Setup - Architecture

Setup - High Level Flowchart

Test Case Analysis:

  1. Upload Flow:

  • Frontend initiates file upload

  • Backend processes the file and interfaces with IPFS

  • IPFS generates and returns a unique hash

  • Smart contract on op-sepolia chain records the transaction

  • Process completes with frontend confirmation

  1. Verification Flow:

  • User inputs IPFS hash via frontend

  • Backend queries OP-node for timestamp verification

  • Timestamp data is formatted and returned to frontend

  • Provides proof of existence and timing verification

The Setup

We have 3 nodes ready, and we can deploy the Smart Contract via the OP node

Frontend script

Then, we prepared a backend script that configures the essential connections: the IPFS node location, the deployed smart contract address, and the OP (Optimism) node endpoint.

Next, on our Ethereum node, we enabled the HTTP ports to listen for and monitor incoming transactions.

Then, on our Optimism node, we enabled HTTP ports for the OP-Sepolia chain and configured it to connect to our Ethereum node through the private network.

For the IPFS node configuration, we set up the API listening address and configured the gateway address using our public IP, allowing file uploads from the internet. The gateway enables external access to the IPFS node.

Testing 1 Results

The file upload process worked successfully:

  1. The file was uploaded to IPFS

  2. The transaction passed through our smart contract

  3. The Optimism node relayed the Layer 2 (L2) to Layer 1 (L1) operations to the Ethereum node

  4. The system successfully returned the IPFS hash

Testing 2 Results

We completed the verification process:

  1. Copied the returned IPFS hash

  2. Sent the verification request to the blockchain through the Optimism node to the Ethereum node

  3. Successfully received the timestamp confirmation from the blockchain

Key Advantages:

  1. Geographic Distribution: With 30+ edge locations, applications benefit from reduced latency and improved regional access

  2. Decentralized Architecture: True to Web3 principles with distributed storage and computation

  3. Regional Focus: Optimized for Hong Kong and GBA markets to reach global network

  4. Development Flexibility: Supports local development environments that can seamlessly transition to production

Conclusion

This infrastructure demonstrates how decentralized edge computing can effectively support Web3 applications while maintaining the benefits of traditional cloud services. The setup provides a robust foundation for dApps requiring high availability, low latency, and regional compliance.

Our Web 3 Use Cases

Decentralized Document Verification System

  • Use Case: Legal document authentication in Hong Kong's financial sector

  • Implementation:

    • Documents uploaded through the Upload flow

    • IPFS ensures immutable storage

    • Smart contract on op-sepolia maintains verification records

    • Verification flow provides timestamp proof

  • Benefits: Reduces document fraud, provides audit trail, complies with regulatory requirements

NFT Marketplace with Regional Focus

  • Use Case: Digital art marketplace for GBA artists

  • Implementation:

    • Artwork files stored via IPFS

    • Metadata and ownership recorded on-chain

    • OP node ensures cost-effective transactions

    • Verification system confirms authenticity

  • Benefits: Lower gas fees, faster transactions, regional content delivery

Supply Chain Traceability

  • Use Case: GBA manufacturing verification

  • Implementation:

    • QR codes linked to IPFS hashes

    • Timestamp verification for production milestones

    • Smart contracts managing supply chain states

    • Edge nodes ensuring real-time data availability

Digital Identity Management

  • Use Case: Cross-border identity verification in GBA

  • Implementation:

    • Encrypted identity documents stored on IPFS

    • Verification flow for identity checks

    • Smart contracts managing access control

    • Edge compute ensuring data sovereignty

Decentralized Content Distribution

  • Use Case: Video streaming platform for Hong Kong content creators

  • Implementation:

    • Content stored on IPFS

    • Edge nodes optimizing content delivery

    • Smart contracts managing access rights

    • Verification system for copyright protection

  • Benefits: Reduced bandwidth costs, improved loading times, content authenticity

Next, we set up a test frontend HTML page & frontend script on our testing server to implement file .

upload and verification functions
Page cover image