Development process

Select components from the module store and quickly integrate them into your application using the SDK.

🚀 Summary of EBN Modular Application Rapid Integration Development Process

The EBN platform, through its modular framework design, provides developers with a simplified and composable path to build L2 applications. The core of the entire development process lies in efficiently utilizing pre-built components from the module store and standardized SDK/API interfaces.

Core development paradigm: Plug-and-Play

This process overturns the traditional "build-from-scratch" blockchain development model, allowing developers to focus on innovation in the application logic layer.

1. 🔍 Module Selection & Architecture Definition

Objective: To identify the core functional components required by the application and decouple the underlying capabilities.

  • step:

    • Requirements Analysis and Module Positioning: Developers identify the required underlying technical capabilities (e.g., lending pools, cross-chain bridging, oracle modules) based on the application scenario (e.g., DeFi lending, cross-chain NFT market).

    • Module Store Search and Selection: Browse and search for standardized or customized components that have been listed and audited in the Module Store.

    • Architecture composition: Define the application's L2 architecture by using selected basic modules (such as transaction execution and state management) and functional extension modules (such as smart contract templates and bridging modules) as dependencies.

2. 🔌 Component Acquisition & One-Click Deployment

Objective: To quickly acquire and activate the required L2 smart contracts and backend services.

  • step:

    • Acquiring Components: Purchase or integrate selected modules. For community-contributed modules, this typically involves their pricing and revenue-sharing mechanisms.

    • Instant Deployment: Leveraging the features provided by the module store, quickly deploy the underlying smart contract logic (or WASM sandbox configuration) of a module to the EBN L2 network. This step significantly saves time on contract deployment, initialization, and security configuration.

3. 🛠️ SDK/API Integration & Customization

Objective: To efficiently integrate deployed module functionalities into the application front-end and business logic using a standardized toolset.

  • step:

    • Environment Preparation: Set up the development environment using the official SDK (supports TypeScript, Rust, Go, etc.).

    • API Call Encapsulation: Developers can call deployed L2 module functions (such as lockCollateral(asset, amount), batchMint(to[], metadata[])) through a unified SDK/API interface.

    • Security and Verification: The SDK automatically handles the underlying modular process encapsulation and necessary security verification, permission verification, and transaction signing logic.

    • Customization: Based on the simplified contract template provided by the SDK, differentiated application functions can be implemented by configuring parameters or integrating custom business logic code (such as GameFi's combat and interaction engine).

4. 🔗 Transaction Submission & State Synchronization

Objective: To ensure that application operations can be executed and synchronized efficiently and securely in the L2 network.

  • step:

    • Transaction Submission: Users send transaction requests to the L2 transaction execution engine/Sequencer via the application frontend's SDK/API call.

    • Batch Packaging and State Update: The Sequencer collects transactions, verifies, sorts, and batches them, updating the global state of the off-chain state manager.

    • Data Availability Proof: Transaction batch data is sent to the data availability layer for sharded storage and to generate Merkle proofs.

    • L1 Anchoring: The final state root/transaction batch data is periodically submitted to the Bitcoin mainnet for final verification.

5. 📊 Operational Monitoring & Iteration

Objective: To continuously monitor application performance and network health to ensure long-term stable operation.

  • step:

    • Real-time Monitoring: Utilize a visual operations and maintenance dashboard to view key metrics such as application module call volume, transaction latency (TPS), and TVL in real time.

    • Performance Optimization: Based on the data analysis results from the operations and maintenance dashboard, optimize and adjust modules or interfaces with high resource consumption.

    • Governance and Iteration: As ecosystem builders, application developers participate in the DAO governance process, proposing upgrades to protocol parameters or modules, driving continuous application iteration and expansion.

Summary of process advantages: By combining "module store + SDK", EBN effectively shifts the complexity of Layer 2 application development to the module design level, providing application developers with a highly efficient, low-cost, and highly composable integration environment, thereby significantly accelerating the innovation and iteration of the Bitcoin ecosystem.

PreviousDeveloper toolsNextBasic Token Information

Last updated