After your DePIN is fully integrated with the peaq network—complete with machine wallets, DIDs, and verifiable data flows—the next step is to determine how your users or devices will interact with the system in production.

There are several common deployment models depending on your use case, each with its own strengths:

• Server Implementation
• Mobile Application
• Web Application

Below is a high-level overview of how each approach works and what makes it unique. These models can also be combined depending on your architecture.

​

Server Implementation

A server-side deployment is the most flexible and common approach for DePINs, especially when dealing with multiple machines, background processes, or integrations with legacy infrastructure.

​

Key Characteristics

• Control of DID creation, wallet generation, and on-chain transactions.
• Ideal for IoT networks, machine fleets, or backend-only services.
• Can be scheduled, event-driven, or triggered via APIs from other systems.

​

Typical Use Cases

• Creating a machine DID as soon as a new device is provisioned.
• Running cron jobs or real-time services to monitor machine behavior and update DIDs.
• Hosting APIs that allow frontends (web/mobile) to interact with blockchain logic securely.

​

Tech Stack

• Node.js, Python, or Go backend
• Cloud infrastructure (AWS, GCP, Azure)
• Secure key management (e.g. HSMs, Vault, KMS)

Recommended when you need maximum control and scalability across a large number of machines or services.

​

Mobile Application

A mobile-based DePIN enables end-users to manage their machine identities or interact with the network directly from their smartphone.

​

Key Characteristics

• Local wallet generation and signing using device secure storage (e.g. Keychain, Keystore).
• Direct integration with peaq DID SDK and peaq storage via lightweight APIs.
• Enables machines controlled or managed via phones (e.g. mobility services, consumer DePINs).
• Integration with Account Abstraction solutions.

​

Typical Use Cases

• End-user onboarding flow to create a machine wallet and DID when setting up a device.
• Enabling rideshare drivers, delivery partners, or remote workers to verify data from their device.
• QR code scanning or Bluetooth-triggered DID operations.

​

Tech Stack

• React Native, Flutter, or native iOS/Android
• Lightweight backend for transaction relaying (optional)
• Integration with WalletConnect, push notifications, or secure enclave features

Recommended for DePINs targeting individual users, decentralized access, or mobile-first ecosystems.

​

Web Application

A web app-based DePIN allows machines or users to interact with the peaq network through a browser interface, offering a lightweight and accessible entry point.

​

Key Characteristics:

• On-demand wallet generation using browser-based tools (e.g. ethers.js, peaq-js-sdk).
• Great for dashboard-style tools, data viewers, or admin portals.
• Ideal for browser-based configuration or onboarding flows.
• Integration with Account Abstraction solutions.

​

Typical Use Cases:

• Admin portals that manage a fleet of machines via a web dashboard.
• Frontend tools that allow users to submit or verify data tied to machine DIDs.
• Public explorers, visualizations, or analytics for DePIN networks.

​

Tech Stack:

• React, Next.js, or Vue.js frontend
• SDK integration for DID operations and storage writes
• Optional backend for signing or relaying if key custody is needed

Recommended for data transparency, interactive dashboards, or lightweight onboarding experiences.

​

Choosing the Right Approach

Each deployment method is valid and can be adapted to your specific needs. In many cases, projects combine two or more approaches. For example:

• A server handles DID creation and background processes.
• A web app provides admin controls.
• A mobile app allows users to interact directly with machines.

Once you’ve chosen your approach, continue to the Pre-deployment Checklist below to ensure a smooth launch to peaq mainnet.

​

Pre-deployment Checklist

​

Security Audits and Final Checks

• Recommendation: Before deploying to peaq mainnet, perform a final security audit of the smart contracts and DID implementation. Doing so will ensure there are no vulnerabilities that could compromise the integrity of the system or the users’ assets.

Ensure all smart contracts and DIDs have passed a thorough security audit. Address any potential vulnerabilities and run additional stress tests to validate performance under mainnet conditions.

​

Community and Developer Engagement

• Recommendation: Engage with the community and developers during the launch phase. This will build trust and excitement while onboarding potential users and contributors.

Host an AMA (Ask Me Anything) or community event to showcase the deployment and answer questions about the project’s functionality, vision, and roadmap.

​

Documentation and Tutorials

• Recommendation: Provide clear, user-friendly documentation and tutorials for interacting with the system to reduce friction for new users and developers while improving adoption.

Publish step-by-step guides and developer tutorials to help users and integrators interact with your DIDs, smart contracts, and token on peaq mainnet.

​

Incentive Programs

• Recommendation: Launch incentive programs such as bug bounties, user onboarding rewards, or machine data upload. This will further encourage participation and will help identify potential issues post-deployment.

Introduce a bug bounty program to reward security researchers for identifying vulnerabilities. Consider offering tokens or perks for early adopters who test or contribute to the system.

​

Monitoring and Analytics Setup

• Recommendation: Set up monitoring tools to track performance and detect anomalies on the mainnet to respond quickly to any issues.

Implement blockchain analytics and monitoring tools to track transaction volumes, smart contract activity, and any unusual patterns post-deployment.

​

Integration Announcements

• Recommendation: Publicize integrations or partnerships that will launch alongside the deployment to highlight the ecosystem’s growth and potential.

Announce any collaborations, integrations, or ecosystem partnerships that will utilize your deployed DIDs or tokens on the peaq mainnet.

​

Governance and Tokenomics Introduction

• Recommendation: Provide detailed information on governance and token utility. This will help the users understand how to participate and what benefits the token brings.

Release governance details and tokenomics, including staking, voting mechanisms, or reward structures, to foster participation and transparency.

​

Post-Launch Support Plan

• Recommendation: Outline a plan for providing ongoing support and updates to build confidence in long-term reliability and engagement.

Share your post-launch roadmap and establish channels for technical support, including dedicated help desks, community moderators, or support emails.

​

Compliance and Regulatory Transparency

• Recommendation: Ensure the deployment complies with relevant laws and regulations. Doing so will mitigate the risks of legal issues that could arise post-deployment.

Provide transparency on regulatory compliance efforts and any legal frameworks adhered to during the deployment.

​

User Education Campaigns

• Recommendation: Educate end users about the system’s benefits, features, and how to use it to facilitate adoption and trust in the platform.

Conduct user education campaigns, including webinars, videos, and blog posts, to familiarize users with the functionality of your deployed solutions.