# Executive Summary

The DeEEP Network by NerdNode is set to revolutionize the landscape of decentralized computing.  The DeEEP Network combines privacy focused technology with automated operations to create a secure, managed, and scalable platform for Web3 applications. Built by a team of experts with deep roots in blockchain and distributed edge computing, DeEEP is not just another network—it's the future of decentralized infrastructure.

{% hint style="info" %}
**Demand for web3 hosting is skyrocketing**

* Web3 market is projected to grow at a compound annual growth rate (CAGR) of 49.3% through 2030 in the US. ([Grand View Research](https://www.grandviewresearch.com/industry-analysis/web-3-0-market-report))
* Ethereum Validators grew 54.5% year-over-year​ ([CoinDesk](https://www.coindesk.com/consensus-magazine/2023/09/29/the-most-pressing-issue-on-ethereum-is-validator-size-growth/))​​ ([Blockworks](https://blockworks.co/news/post-merge-ethereum-climate-impact))​.
* Web3 gaming market is expected to grow from $4.6B in 2022 to $65.7B by 2027​ ([Play To Earn Games](https://playtoearngames.com/news/web3-gaming-update-investments-setbacks-and-2024-projections))​
  {% endhint %}

**Why DeEEP Network Stands Out:**

1. **Monetize Your Bandwidth:** Turn your excess bandwidth into a revenue stream. As a host for DeEEP, you can easily and securely monetize your unused bandwidth, contributing to the infrastructure of a cutting-edge decentralized network and earning real income in the process.
2. **Uncompromising Security in Untrusted Environments:** The DeEEP Network employs advanced secure computing, ensuring top-tier security through strict workload isolation and attestation. By leveraging hardware security solutions, we achieve unparalleled verification and protection. This robust setup ensures that workloads remain secure even when the physical location cannot be trusted, safeguarding against unauthorized access and tampering.
3. **Effortless Deployment:** Forget the hassle of managing your own nodes and validators. With DeEEP, you get a worry-free hosting experience. We handle all aspects of security, updates, and maintenance, so you can focus on your core applications and innovations without the constant firefighting.
4. **Versatile Service Support:** The DeEEP Network supports a wide array of services—from Web3 nodes and validators to IPFS servers and game servers. Our flexible framework allows for the seamless addition of new services, ensuring compliance with all necessary regulations and policies. This versatility makes DeEEP the ideal choice for a variety of decentralized applications.
5. **Community-Driven Growth:** We are committed to creating a fully decentralized network. Currently we manage thousands of Web3 nodes on NerdNode owned hardware, we plan to move all these workloads to the DeEEP DePIN.   We invite the community to join us in this journey, contributing to hosting, service additions, governance, and the ongoing development of the network.

**Our Beliefs and Vision:**

* **All parties in the Web3 chain deserve to be compensated fairly:** We ensure that hosts, developers, and users are all fairly rewarded for their contributions.
* **Web3 should run on distributed networks in a DePIN:** We envision a future where Web3 infrastructure is decentralized, secure, and efficient.
* **Web3 should be simple for anyone to host:** Our goal is to make it easy for all individuals to participate in the Web3 ecosystem.

**Join the DeEEP Revolution:**

The DeEEP Network isn't just a platform—it's a movement towards a decentralized future. With robust security, monetization opportunities, versatile service support, and a community-driven ethos, DeEEP is poised to become the backbone of decentralized computing. Be part of this revolutionary network and help shape the future of Web3.

The future is decentralized. The future is DeEEP. Join us today.


# How it works

The DeEEP Network has a marketplace to connect decentralized resources to host web3 with those who need web3 hosting. The marketplace includes all the stakeholders necessary to provide secure hosting of services, maintain service level agreements for them to keep running and provide the resources (hardware, bandwidth & power) to provide them.

These stakeholders include web3 service owners who need hosting, hardware owners, web3 service creators (such as game companies), and hardware manufacturers.

{% embed url="<https://www.figma.com/board/aVAOMr3qoOXYjU570ePVBl/Resolution-Workflow?node-id=305-547&t=FepJqh0sjCmAssUq-4>" %}

The marketplace consists of a web page, token, and smart contracts on the blockchain.  The contracts spell out what services get run, for whom, at what SLA, for how long, by what hardware provider, and for how much token.  This ensures a transparent and fair distribution to stakeholders relative to their value contributed to the network. Allocation and token emissions can be amended over time through Deeep Resolutions.

## How stakeholders interact with the marketplace: <a href="#how-each-stakeholder-interacts-with-the-marketplace" id="how-each-stakeholder-interacts-with-the-marketplace"></a>

### Web3 Service Owners

Pay to host a service (node, valadator, web3 service)&#x20;

A web3 service owner can be an individual who purchased a node, validator or rights to run a web3 service or it can be another web3 company who needs a safe, reliable place to run their software.  They  use the market place to sign a contract to host their service on the Deeep Network and the network then runs it according to the terms.

### Hardware Owners

Paid for hosting capacity utilized on DeEEP Network.

Hardware owners have purchased a DeEEP BOX NFT license and a DeEEP provisioned device. They simply plug the device into their power and internet.  Hardware owners can be located anywhere in the world.  Once plugged in the hardware shows up as an available resource on the DeEEP Network Marketplace for services to run on.  They are paid token based on contracted terms of services being run.&#x20;

### Web3 Service Creators

Want their software run on the DeEEP Network.

Web3 Service Creator develops a package to install, run, monitor and maintain services on the network.  They submit the package to the Deeep git repository containing the technical details and minimum requirements of running their service.  Once approved, the service is listed as available for use on the Deeep Network Marketplace by Web3 Service Owners.

### Hardware Manufacturers

Provide secure and capable hardware certified for the Deeep Network.&#x20;

The hardware used on Deeep Network requires specific security features to make the network safe to use for all parties.  Devices are preloaded from the factories with secret keys and a trusted boot chain.  The public keys are uploaded to the marketplace to establish the hardware is safe to use on the network.


# Services

Web2 or Web3 workloads that run on the Deeep Network

**DeEEP** can run Web3 services, such as **nodes**, **validators**, **oracles**, and **RPC (Remote Procedure Call)** **providers** alongside traditional Web2 services like **databases**, **computational work**, **game servers**, **websites**, and **storage**. This fusion is designed to provide users with a complete and seamless digital experience by utilizing the best features of both Web2 and Web3 technologies on a DePIN.

The **DeEEP Network** takes care of the complexities of running and managing diverse and complex Services with:

* **Single-click Deployments**: Simplifies the process of deploying Web2 and Web3 services, making it accessible even to those with minimal technical expertise.
* **Full management:** Ensures that all Services run smoothly, ensuring Devices are running at their peak efficiency and Services achieve the best uptime possible.
* **Ease of maintenance**: Reduces the effort and resources required to maintain and update services, allowing users to allocate more time to innovation and development.
* **Automated Failure Recovery:** If a service goes down on one node it is seamlessly moved to another device in the network automatically according its SLA.

#### Security at the Forefront

We prioritize security for both [Service Owners](/introduction/get-started/run-on-deeep) and [Device Operators](/introduction/get-started/host-for-deeep), ensuring peace of mind for all users. Our platform is built with advanced security measures, it's part of the name after all "**De**centralized **E**ncrypted **E**nvironment **P**roject", designed to protect your data and Services at every level.

* **Data Protection**: We employ end-to-end encryption to safeguard your data in transit and at rest, preventing unauthorized access.
* **Regular Security Updates**: Our system constantly updates to defend against the latest threats, ensuring your services remain secure.
* **Access Control**: Implement robust access controls to limit who can view or modify your data and Services, further enhancing security.

By focusing on these security aspects, you can trust the **DeEEP Network** to handle your Web2 and Web3 services securely, allowing you to concentrate on innovation and growth.

{% hint style="info" %}
If you're a project that wants to deploy on the **DeEEP Network** reach out [🤝 Partnerships](/introduction/get-started/partner-with-deeep)
{% endhint %}


# Why it works

#### Why DePIN?

A Decentralized Physical Infrastructure Network (DePIN) significantly enhances resilience of and reduces operational risks of web3 services. By distributing nodes globally, DePIN reduces the risk of single points of failure and mitigates potential shutdowns and service denials. It leverages blockchain technology to maintain trust through cryptographic means, eliminating reliance on centralized entities.&#x20;

DePIN also distributes the earnings amongst the community instead of enriching datacenter monopolies.  Revenues from the services can be distributed to all the players in the ecosystem fairly based on their contributions.&#x20;

#### Limitations

Despite its potential, the DePIN market faces several significant challenges that hinder its broader adoption. One major issue is compromises in privacy and security standards. Many DePIN solutions struggle to meet the stringent regulatory requirements necessary for various applications, leaving them vulnerable to compliance issues. ([Deloitte](https://www2.deloitte.com/us/en/pages/consulting/articles/blockchain-and-web3-adoption-for-enterprises.html))

Additionally, hosting on centralized platforms poses risks such as potential shutdowns and service denials, especially when terms of service are changed or enforced against blockchain operations. These limitations underscore the urgent need for a more robust, secure, and compliant Web3 infrastructure.

#### Web3 Growth Statistics:

* **Market Growth:** The Web3 market is projected to grow at a compound annual growth rate (CAGR) of 49.3%, reaching significant market milestones by 2030​ ([Grand View Research](https://www.grandviewresearch.com/industry-analysis/web-3-0-market-report))​​ ([Blockworks](https://blockworks.co/news/predictions-web3-in2024))​.
* **Adoption of Digital Assets:** The popularity of digital assets, including cryptocurrencies and NFTs, continues to rise, with significant growth in decentralized applications (DApps) and smart contracts. This trend is driving the exponential growth of the Web3 ecosystem​ ([Solid Metrics](https://www.solidmetrics.co/post/web3-growth-trends-2024))​.
* **Developer Growth:** The number of developers working on Web3 projects has hit an all-time high and is growing fast, reflecting the growing interest and investment in this space​ ([Grand View Research](https://www.grandviewresearch.com/industry-analysis/web-3-0-market-report))​.

These trends underscore the transformative potential of Web3 technologies and the promising future of decentralized networks like DeEEP.

#### [DeEEP Network](/) - Our Solution

These challenges are addressed by providing a platform with advanced security measures designed to protect data and Services at every level.

* **Management:** We ensure all Services are managed from their logs to their runtime. Making the entire process as transparent as you want it to be.
* **Data Protection**: Devices employ end-to-end encryption to safeguard your data both in transit and at rest, preventing unauthorized access and ensuring that your information remains secure.
* **Regular Security Updates**: Our system continuously updates to defend against the latest threats, ensuring that your services remain secure and resilient in the face of evolving cybersecurity risks.
* **Access Control**: We implement robust access controls to limit who can view or modify your data and services, further enhancing security and maintaining the integrity of your operations.

By integrating these comprehensive security measures, Deeep ensures a more robust, secure, and compliant Web3 infrastructure, addressing the critical issues currently faced in the DePIN market.


# Problems We Solve

### **Management of Nodes**

* **Simplified Operations**: Our platform eliminates the need for advanced IT skills by providing an intuitive interface for node management, reducing the reliance on command line and IT management tools.
* **Automated Maintenance**: We handle software updates, resource adjustments, and port management automatically, ensuring nodes are always up-to-date and maximizing rewards without manual intervention.
* **Reliable Uptime**: Continuous monitoring and automated maintenance minimize downtime and enhance the reliability of node operations.

### **Centralization vs. Decentralization**

* **Distributed Infrastructure**: By distributing nodes across a global network rather than centralized datacenters, we mitigate the risk of significant downtime due to single points of failure.
* **Compliance Assurance**: Our platform ensures compliance with provider terms of service, reducing the risk of sudden service cutoffs and maintaining network stability.

### **Security of Workloads and Data**

* **Enhanced Data Protection**: We implement robust data protection measures, ensuring that sensitive data is secure and accessible only to authorized users.
* **Secure Hardware Solutions**: By utilizing secure hardware solutions and decentralizing data storage, we provide an environment where high-value data can be protected and managed effectively.

### **Regulatory Compliance**

* **Built-in Compliance Features**: Our platform is developed t support compliance with regulatory requirements such as GDPR, HIPAA, and CCPA, facilitating adoption for projects handling sensitive data.
* **Data Management Tools**: We will provide tools for geolocation, encryption, and selective data deletion, helping projects meet stringent regulatory standards.

### **Cost of Computing**

* **Cost-Effective Solutions**: Our platform offers affordable node hosting options that scale with project needs, reducing the overall cost of maintaining web3 nodes.
* **Resource Optimization**: We optimize resource usage to ensure that nodes run efficiently without incurring unnecessary costs, making it easier for projects and owners to manage their budgets.


# Earning $DEEEP

Participants in the DeEEP network can earn $DEEEP, a utility token in the following ways.

* [Hosting Fees](#hosting-fees) paid by Service Owners
* [Plug-in Rewards](#plug-in-rewards) from [minting](/introduction/earning-usddeeep/tokenomics#minting)
* [Utilization Rewards](#utilization-rewards) from [minting](/introduction/earning-usddeeep/tokenomics#minting)

### **Hosting Fees**

Service Owners will pay for running their Services using $DEEEP, with fees pegged to the United States Dollar (USD) to maintain stability. The distribution of these fees is as follows:

* [Hardware Owners](/introduction/how-it-works#hardware-owners): 50%
* DeEEP Network Operations: 27%
* [Service Creator ](/introduction/how-it-works#web3-service-creators)Fees: 2.7%
* [Community Fund](#community-fund): 0.3%
* NerdNode Management, Sales & Marketing: 20%

<figure><img src="https://1998362903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEuDZ2zxXJpyX1YOwexzL%2Fuploads%2FEmt6TGx173qNqPjrYBNc%2Fimage.png?alt=media&amp;token=c1dfe98e-aa5e-4ec3-9cdd-08dff44ab1a6" alt=""><figcaption></figcaption></figure>

### **Plug-In Rewards**

**Plug-in Rewards** incentivize early participation in the DeEEP network and bootstrap the distribution of tokens. This reward system encourages the on-boarding of new devices, promoting the growth and decentralization of the network.

* **Tiers:** The reward structure is divided into tiers based on the number of devices on-boarded. Each tier represents 10,000 devices.
* **Reward**: 10,000 $DEEEP per month at the first tier, the reward amount is halved every tier.
* **Duration**: 12 months total, while they remain plugged in.

<table><thead><tr><th width="100" align="center">Tiers</th><th>Onboard Position</th><th>Maximum Reward</th></tr></thead><tbody><tr><td align="center">1</td><td>1 - 10,000</td><td>10,000/mo</td></tr><tr><td align="center">2</td><td>10,001 - 20,000</td><td>5,000/mo</td></tr><tr><td align="center">3</td><td>20,001 - 30,000</td><td>2,500/mo</td></tr><tr><td align="center">4</td><td>30,001 - 40,000</td><td>1,250/mo</td></tr><tr><td align="center">5</td><td>40,001 - 50,000</td><td>625/mo</td></tr><tr><td align="center">-</td><td>>= 50,001</td><td>0</td></tr></tbody></table>

{% hint style="warning" %}
Configuration:

* Devices plugged in [directly after the modem](/hardware/setup-your-hardware#recommended-setup) or with a [router configured to forward all ports](/hardware/setup-your-hardware/advanced-setups) with at least [100Mbps down and 20Mbps up](https://www.cooley.com/news/insight/2024/2024-03-28-fcc-adopts-new-minimum-standards-for-broadband-services) bandwidth to the device earn the full reward for their tier.
* Devices not configured as mentioned above or behind CGNAT will earn half of the maximum possible reward for their tier until the configuration is corrected. Missed rewards will not be retroactively earned.
  {% endhint %}

### **Utilization Rewards**

**Utilization Rewards** are designed to incentivize the effective utilization of network resources. These rewards are allocated to device operators based on the utilization of their devices.

Each device on the network has a limited amount of resources, the ability for the device to use these resources are rewarded via Utilization Rewards.

* **Initial Allocation**: Occurs when the Device is on-boarded on to the blockchain. The amount allocated depends on the **Calculated Performance Rating (CPR) of the Device multiplied by 600 $DEEEP .** These tokens are released when Service is ran. This mechanism ensures effective utilization of resources and incentivizes active participation in the network.

{% hint style="info" %}
The amount allocated per CPR (currently set at 600 $DEEEP) will be a blockchain configuration and can change depending on Network needs. Changes require a [proposal ](/introduction/using-usddeeep/governance#submitting-a-deeep-resolution)that's approved via a vote.
{% endhint %}

* **Gradual Release**: For each month a Service runs meeting its contracted SLA with available Utilization Rewards on the device it is running on the (Service CPR)\*(Token per Allocated CPR)/12 of the locked $DEEEP tokens is released to the distribution pool.
  * For instance a service using 16 CPR worth of compute in the initial batch of devices would make 16\*600/12 = 800 $DEEEP per month for running that service contributed to the pool.
* **Expiration**: The locked $DEEEP tokens on a device never expire.
* **Pool Distribution:** The daily pool is distributed after a 10 day settlement period.   All Devices that were online 99% and compliant with the rules established by the [Good Citizen Committee](/introduction/using-usddeeep/governance/deeep-committees#good-citizen-committee) of that day are eligible for the daily distribution.  The CPR value of each device is used to calculate their prorata percentage of the pool. &#x20;


# Tokenomics

The DeEEP Network Utility ($DEEEP) token is central to DeEEP Networks ecosystem, acting as the primary currency for transactions within the network. It facilitates payments for hosting services, purchasing future hardware, and attracting new service offerings. Additionally, $DEEEP is a core driver of [governance](/introduction/using-usddeeep/governance), staking, and balancing network capabilities with workloads.

The $DEEEP token is inherently inflationary, with tokens being minted in accordance with the growth of the Device network. As new Devices join the network, additional tokens are minted to match the increase, ensuring balance between token supply and the expanding infrastructure.

{% hint style="info" %}
This inflationary behavior is linked directly to an increase network computing capacity and only released as [Utilization Rewards](/introduction/earning-usddeeep#utilization-rewards)
{% endhint %}

## **Minting**

### **Device Operators**

The $DEEEP token is minted to Device Operators via two reward types:

* [Plug-In Rewards](/introduction/earning-usddeeep#plug-in-rewards) (only for the first 50,000 Devices)
* [Utilization Rewards](/introduction/earning-usddeeep#utilization-rewards) rewards minted for workloads run on the entire network evenly distributed between all active devices

{% hint style="info" %}
$DEEEP will not be pre-mined or airdropped. The only source of tokens is via the rewards above, [Founders Rewards](#founders-rewards), and the [Community Fund](#community-fund)
{% endhint %}

### **Testnet to Mainnet Conversion**

DeEEP with launch initially with a testnet for the first devices shipped.  For host participants in the testnet before the mainnet launch a fair conversion to the best of our ability based on work done will be applied to migrate testnet participants to mainnet.  Things we might do in testnet like accelerated time for testing contracts, bugs/errors, hacks, etc. will not affect the conversion.&#x20;

### **Community Fund**

To support network growth and community initiatives, a total of 575,000,000 $DEEEP tokens will be minted and locked for the community fund upon the token's release. The distribution of these tokens is designed to align with network expansion:

* **Unlocking Mechanism**: At the activation of the first DePIN device on the network, 1/2 of the community fund will be funded. Then, for every 2,000 DePIN devices activated, 1/50th (11,500,000 $DEEEP) of the community fund will be unlocked.
* **Usage:** Hackathons, community code contribution rewards, bug bounties, partnerships, and Governance Proposal incentives. Full details are on the [Community Fund](/introduction/using-usddeeep/community-fund) page.

### Founders Rewards

Founders Rewards will be minted to smart contract owned wallet(s) for distribution to Founders of the DeEEP network upon meeting performance metrics. &#x20;

There are **two sets** of metrics that **both must be met to unlock the tokens**.  Both sets are measurable by smart contract.

#### 1. Devices on the Network

For each DIN (device identity NFT) that is minted, 0.12 times the of the quantity tokens allocated to that DIN are eligible to be distributed to Founders, this rewards the founding team with the growth of new users on the network.&#x20;

#### 2. Performance of the Network

These tokens eligible by the DIN creation events are then unlocked to the Founders by smart contract upon the following milestones:

* 20% at mainnet launch
* 20% at 5,000+ devices and 50%+ filled capacity
* 20% for quantity of different node/service types deployed
  * 5% for the first 50
  * 5% at 100
  * 5% at 150
  * 5% at 200&#x20;
* 20% at 10,000 devices live
* 20% at DAO/DAC launch

{% hint style="info" %}
**Why are Founders Rewards pre-minted?**

We did not want to pre-mint founders rewards.  However, the guidance in the pending FIT21 legislation states that the 12 month clock classifying the token as a commodity by being sufficiently distributed would be reset by minting token to Founders *(affiliated person)* after the creation. In the pending [FIT21](https://www.congress.gov/bill/118th-congress/house-bill/4763/text#HF3B153F8836F4B99994DD333E0EC973B) it specifically calls out that tokens designated for non-end users (in this case founders) should be created at the initial block and "made available over time."  Based on our interpretation of this, the tokens need to be minted and locked.
{% endhint %}

### Maximum Supply

The maximum supply is 83,822,360,000 tokens.  This allows for up to 1,000,000 devices at the current Utilization Rewards rate.

## Examples

***

### Assumptions

* The launch Device is currently being approximated at having a Calculated Performance Rating (CPR) of 120. This would result in a [Utilization Reward](/introduction/earning-usddeeep#utilization-rewards) of 72,000 $DEEEP per device. *CPR can vary between different hardware devices, and in these models is assumed to stay constant at 120.*

### **Token Breakdown**

A Device which onboards in the first Tier:

* [**Plug-In Rewards**](/introduction/earning-usddeeep#plug-in-rewards): 120,000 $DEEEP
* [**Utilization Rewards**](/introduction/earning-usddeeep#utilization-rewards): 72,000 $DEEEP
* [**Hosting Fees**](/introduction/earning-usddeeep#hosting-fees): 50%

The following is based on the **initial batch of 1,776** DeEEP Devices.

* **Max Available Supply**: 669,411,040 $DEEEP
  * [**Plug-In Rewards**](/introduction/earning-usddeeep#plug-in-rewards): 213,120,000 $DEEEP
  * [**Utilization Rewards**](/introduction/earning-usddeeep#utilization-rewards): 127,872,000 $DEEEP
  * [**Community Fund**](#community-fund): 287,500,000 $DEEEP
  * [**Founders Rewards**](#founders-rewards)**:** 40,919,040 $DEEEP (Maximum unlockable)

<figure><img src="https://1998362903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEuDZ2zxXJpyX1YOwexzL%2Fuploads%2FP5xnhGyFSIcURRqBRVAz%2Fimage.png?alt=media&amp;token=24428564-81cd-47d0-ba61-0303932aceb7" alt=""><figcaption></figcaption></figure>

The following is based on **50,000** DeEEP Devices.

* **Max Available Supply**: 7,214,360,000 $DEEEP
  * [**Plug-In Rewards**](/introduction/earning-usddeeep#plug-in-rewards): 2,328,000,000 $DEEEP
  * [**Utilization Rewards**](/introduction/earning-usddeeep#utilization-rewards): 3,600,000,000 $DEEEP
  * [**Community Fund**](#community-fund): 575,000,000 $DEEEP
  * [**Founders Rewards**](#founders-rewards)**:** 711,360,000 $DEEEP (Maximum unlockable)

<figure><img src="https://1998362903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEuDZ2zxXJpyX1YOwexzL%2Fuploads%2Fy4paBp15tMaQOjDy4J66%2Fimage.png?alt=media&amp;token=622458f0-7d35-404d-8908-cba9fa3c188f" alt=""><figcaption></figcaption></figure>

The following is based on **60,000** DeEEP Devices.

* **Max Supply**: 8,020,760,000 $DEEEP
  * [**Plug-In Rewards**](/introduction/earning-usddeeep#plug-in-rewards): 2,328,000,000 $DEEEP
  * [**Utilization Rewards**](/introduction/earning-usddeeep#utilization-rewards): 4,320,000,000 $DEEEP
  * [**Community Fund**](#community-fund): 575,000,000 $DEEEP
  * [**Founders Rewards**](#founders-rewards)**:** 797,760,000 $DEEEP (Maximum unlockable)

<figure><img src="https://1998362903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEuDZ2zxXJpyX1YOwexzL%2Fuploads%2FIBrogCCDRhEbCxDIuTqD%2Fimage.png?alt=media&amp;token=63dabd12-c48e-46f6-82f9-c0703d72dd51" alt=""><figcaption></figcaption></figure>

The following is based on **1,000,000** DeEEP Devices.

* **Max Supply**: 83,822,360,000 $DEEEP
  * [**Plug-In Rewards**](/introduction/earning-usddeeep#plug-in-rewards): 2,328,000,000 $DEEEP
  * [**Utilization Rewards**](/introduction/earning-usddeeep#utilization-rewards): 72,000,000,000 $DEEEP
  * [**Community Fund**](#community-fund): 575,000,000 $DEEEP
  * [**Founders Rewards**](#founders-rewards)**:** 8,919,360,000 $DEEEP (Maximum unlockable)

<figure><img src="https://1998362903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEuDZ2zxXJpyX1YOwexzL%2Fuploads%2FKsGtw6tbR7hmpxm5ULqT%2Fimage.png?alt=media&amp;token=e9d7fbf0-8b62-444f-acd5-a142b9be9328" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1998362903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEuDZ2zxXJpyX1YOwexzL%2Fuploads%2FQG27UCW2eL6GyO1u1Bo5%2Fimage.png?alt=media&amp;token=debc85c0-7467-4a1a-8299-29d9551b10c4" alt=""><figcaption><p>A chart of maximum available supply with all smart contracts being fulfilled at 100%</p></figcaption></figure>


# Using $DEEEP

The $DEEEP token is designed to be a utility token that will progressively provide value to users of the DeEEP marketplace as the network evolves and expands. It is designed around a flywheel action where alternating cycles of supply and demand drive more adoption in the system.

<figure><img src="https://1998362903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEuDZ2zxXJpyX1YOwexzL%2Fuploads%2FbmSW1DIWTndAq8Y6vInb%2Fimage.png?alt=media&amp;token=67bc8c3e-1171-4182-bd2f-891483dc42ed" alt=""><figcaption><p>DeEEP Network Flywheel Action</p></figcaption></figure>

Our vision is to integrate the $DEEEP token into various aspects of the ecosystem, with a focus on unlocking benefits and driving user engagement. As we grow, we plan to implement the following features and use cases for the $DEEEP token:

1. **Transaction Fees:**
   * [**Hosting Services**](/introduction/earning-usddeeep#hosting-fees)**:** $DEEEP tokens are used to pay for hosting services on the DeEEP marketplace. Service Owners pay for running their nodes and validators, with fees pegged to USD for consistency.
2. **Incentives and Rewards:**
   * **Plug-in Rewards:** Incentivizing early adopters by rewarding the first 50,000 devices onboarded with $DEEEP tokens. The reward structure is tiered, decreasing as more devices are added to the network.
   * **Utilization Rewards:** Allocating tokens to Device Operators based on the effective utilization of their devices. This encourages active participation and efficient use of network resources.
3. [**Governance**](/introduction/using-usddeeep/governance)**:**
   * [**Voting Power**](/introduction/using-usddeeep/governance#voters)**:** $DEEEP tokens are used to participate in the governance process. Token holders can vote on proposals, delegate their voting power to Data Committee members, and influence network decisions.
   * [**Proposal Submission**](/introduction/using-usddeeep/governance/deeep-resolution)**:** To submit a DeEEP Resolution (DR), a certain amount of $DEEEP tokens must be locked as an initialization fee. This ensures that only serious and well-considered proposals are submitted.
4. **Staking:**
   * **Security and Trust:** Compute Owners may stake $DEEEP tokens as a form of collateral to enhance the security and trustworthiness of their services to meet SLA requirements. Staking can also be an SLA requirement for accessing certain high-value or high-stakes services on the network.
5. [**Community Fund**](/introduction/using-usddeeep/community-fund)**:**
   * **Development and Growth:** A portion of $DEEEP tokens are allocated to the Community Fund, which supports network growth and community initiatives. This fund can be used for hackathons, community contributions, bug bounties, and partnerships.
   * **Incentivizing Contributions:** The Community Fund can reward developers and contributors who create new service runners, improve network functionality, or enhance security.
6. **Service Discounts and Promotions:**
   * **Device Identity NFT (DIN) Traits:** Traits linked to DINs can provide discounts on services, faster release of rewards, or other benefits. These traits are unlocked based on milestones achieved during the BOX NFT sale.
7. **Monetization of Services:**
   * **Management Fees:** Fees for managing devices and keeping them up to date  and running in line with the SLA. These fees are paid in $DEEEP tokens and can vary based on the service level agreements (SLAs) and performance metrics.
8. **Ecosystem Development:**
   * **Partnerships and Integrations:** $DEEEP tokens can be used to incentivize partnerships with other projects and platforms, integrating new technologies and expanding the ecosystem.
   * **Marketing and Outreach:** Allocating $DEEEP tokens for marketing efforts, user acquisition, and outreach to grow the network and attract new participants.
9. **User Engagement:**
   * **Participation Rewards:** Rewarding community members for their active participation in governance, discussions, and contributions to the network's development and improvement.
10. **Development Bounties:**
    * **Bug Bounties:** Allocating $DEEEP tokens from the [Community Fund](/introduction/using-usddeeep/community-fund) to bug bounty programs, encouraging developers to identify and report vulnerabilities in the network.
    * **Feature Development:** Offering bounties for the development of new features, integrations, or improvements to the DeEEP Network ecosystem.
11. **Referral and Affiliate Programs:**
    * **Referral Bonuses:** Implementing a referral program where users earn $DEEEP tokens for bringing new participants to the network.
    * **Affiliate Rewards:** Partnering with affiliates to promote NerdNode services and rewarding them with $DEEEP tokens for successful referrals.
12. **Liquidity Provision:**
    * **Liquidity Pools:** Encouraging users to provide liquidity for $DEEEP trading pairs on decentralized exchanges (DEXs) and rewarding them with a share of transaction fees.
    * **Automated Market Making:** Using $DEEEP tokens in automated market maker (AMM) protocols to facilitate trading and improve liquidity.


# Community Fund

The DeEEP Network is committed to fostering a vibrant, engaged, and empowered community. To support our goal, we have established the Community Fund, a dedicated pool of resources designed to drive the growth, adoption, and long-term success of the network.

**Fund Allocation**

Upon the release of the $DEEEP token, a total of 575,000,000 tokens will be minted and locked specifically for the Community Fund. This allocation represents a significant investment in the future of the DeEEP Network and its community.&#x20;

**Unlocking Mechanism**&#x20;

To ensure a fair and progressive distribution of the Community Fund, the tokens will be unlocked in stages, tied to the activation of DePIN devices on the network. This mechanism aligns the fund's release with the growth and expansion of the DeEEP Network infrastructure.&#x20;

* 50% of the Community Fund (287,500,000 $DEEEP) will be immediately funded at the activation of the first DePIN device on the network.
* The remaining 50% will be unlocked incrementally, with 1/50th of the total fund (11,500,000 $DEEEP) being released for every 2,000 DePIN devices activated.&#x20;

**Fund Usage**

The Community Fund will be utilized to support a wide range of initiatives and activities that contribute to the growth, development, and engagement of the DeEEP Network ecosystem. These include:

1\. Hackathons and Developer Initiatives:

* Organize hackathons to encourage innovation, collaboration, and the creation of new applications and services on the DeEEP Network.
* Fund developer workshops, training programs, and resources to enable developers to build and deploy on the network effectively.

2\. Community Code Contributions:

* Reward community members who contribute code improvements, bug fixes, and new features to the DeEEP Network codebase.
* Incentivize the development of open-source tools, libraries, and integrations that enhance the functionality and usability of the network.

&#x20;3\. Bug Bounties and Security Audits:

* Allocate funds for bug bounty programs to identify and resolve vulnerabilities and ensure the security and integrity of the network.&#x20;
* Finance professional security audits to maintain the highest standards of security and protect user assets and data.

4\. Partnerships and Collaborations:

* Foster strategic partnerships with other projects, platforms, and organizations to expand the reach and capabilities of the DeEEP Network.
* Fund joint initiatives, co-marketing efforts, and collaborative development projects to drive adoption and create new opportunities for growth.

5\. Governance and Community Engagement:

* Provide incentives for active participation in the governance process, including rewards for submitting high-quality proposals and engaging in decision-making.
* Support community-driven events, meetups, and conferences to foster a sense of belonging, knowledge sharing, and collaboration among DeEEP Network stakeholders.

6\. Education and Awareness:

* Create and distribute educational content, tutorials, and guides to help users and developers understand and utilize the DeEEP Network effectively.
* Fund marketing campaigns and initiatives to increase awareness and adoption of the network among target audiences.

&#x20;7\. Research and Development:

* Support research projects that explore new technologies, improvements, and potential applications of the DeEEP Network.
* Fund the development of proof-of-concept projects and prototypes that showcase the capabilities and potential of the network.

&#x20;8\. Ecosystem Grants and Incentives:

* Establish a grant program to provide financial support to projects and startups building on top of the DeEEP Network.
* Offer incentives for liquidity provision, staking, and other activities that contribute to the stability and growth of the $DEEEP token economy.

&#x20;9\. Social Impact and Inclusion:

* Support initiatives and projects that align with the values of decentralization and use the DeEEP Network for social good.&#x20;
* Fund programs that promote inclusion, accessibility, and the development of underserved communities.

&#x20;10\. Emergency and Contingency Fund:

* Maintain a portion of the Community Fund as a reserve to address unforeseen challenges or critical issues that may arise.
* Ensure the network's resilience and ability to navigate unexpected situations effectively.

&#x20;The allocation and use of the Community Fund will be governed by the DeEEP Network's decentralized governance model. DeEEP Resolutions (DRs) related to the Community Fund will be subject to the standard voting process, ensuring transparency and community involvement in decision-making.

Regular reports and updates on the utilization of the Community Fund will be provided to the community, maintaining transparency and accountability in the management of these resources.

&#x20;**Conclusion**

The Community Fund is a vital component of the DeEEP Network's vision for a decentralized, inclusive, and thriving ecosystem. By allocating resources to support community-driven initiatives, foster innovation, and drive adoption, we aim to create a network that empowers individuals and organizations to build, collaborate, and succeed in the decentralized future.


# Governance

‌Governance refers to a set of operational policies centered around a decentralized voting system. It allows the Deeep Network participants the ability to directly contribute to the direction and policies that make up the Network. While it's not a pure democracy, it operates as a representative democracy with a Data Committee exercising the voting power vested in them by token holders.

{% hint style="warning" %}
This governance will take effect within 90 days of mainnet launch.  Until then NerdNode will review and approve resolutions off chain.
{% endhint %}

## **Members of Governance**

### **Voters**

**Data Committee Members:** These members are the designated voters on Deeep Resolutions. Their Voting Power is based on their locked $DEEEP and the amount of Voting Power delegated to them by Delegates.

### Delegates

**‌Token Holders or**  [**Data Committee Members**](#voters)**:** These individuals can delegate their voting power to Data Committee Members, ensuring their interests are represented in governance decisions.

### Resolution Author

The individual that follows the [DeEEP Resolution](https://github.com/nerdnode-io/gitbook/blob/main/technical-references/litepaper/governance/Deeep-resolution.md) (DR) process and successfully submits it to a vote.

## Submitting a DeEEP **Resolution**

All votes start by submitting a DeEEP Resolution, which must cite a budget and proposed funding source if there is a budget requirement among other things. This can include sources like the [Community Fund](/introduction/earning-usddeeep/tokenomics#community-fund), validator fees, etc.

{% hint style="info" %}
Want to submit a Deeep Resolution? Review the process [here](https://github.com/nerdnode-io/gitbook/blob/main/technical-references/litepaper/governance/Deeep-resolution.md) 🚀
{% endhint %}

## **‌Voting Procedure**

{% embed url="<https://www.figma.com/board/aVAOMr3qoOXYjU570ePVBl/Resolution-Workflow?node-id=103-1509&t=COCrmYCiOD5il9Ef-4>" %}
Normal Voting Process
{% endembed %}

### ‌**Voting Start**

**‌**Time: Voting starts on D+2 00:00 (UTC) from DR Submission

‌Once the DR is submitted, relevant notice is sent out on the NerdNode website, Discord and other communities

{% hint style="info" %}
Voting Power of all Data Committee Members are determined as per the snapshot taken at the DR submission. This will be the Voting Power used during the voting process. Any change of Voting Power during the vote will not be reflected.
{% endhint %}

### **Voting Procession**

**Period**: 7 Days (168 Hours)

‌**Vote Options**: One in favor, opposition, and abstention

**Status**:

* **Rejected** (>50% in opposition) - will not be implemented and [Initialization Fee](https://github.com/nerdnode-io/gitbook/blob/main/technical-references/litepaper/governance/Deeep-resolution.md#initialization-fee) is collected by [Community Fund](/introduction/earning-usddeeep/tokenomics#community-fund)
* **Approved** (>=50% in favor) - approved for adoption onto the network and [Initialization Fee](https://github.com/nerdnode-io/gitbook/blob/main/technical-references/litepaper/governance/Deeep-resolution.md#initialization-fee) is refunded to the author(s)

> **Quorum**: Quorum is the minimum number of votes required for a resolution to pass. Based on the number of votes determined by the snapshot at the time of voting start, the total number of votes excluding the abstention is considered valid. Quorum is defined as over 40% of these valid votes.

‌Voting is compulsory, and all Data Committee Representatives with active Voting Power based on the snapshot are required to participate in the voting process (responsibility imbued by authority).

{% hint style="info" %}
‌Voting may end early should the votes result in Rejected or Approve as described above
{% endhint %}

### Emergency Resolutions

In the event of a situation requiring action quickly for emergency situations (if someone is gaming rewards at the detriment to the community, a major security vulnerability is detected, or something is adversely affecting the Network) the Data Committee members may vote on a temporary resolution with a narrow scope to immediately stay the emergency event.

An emergency vote requires 67% of the Data Committee members to vote in favor.

Emergency votes in order to protect the security, major health factors, or other data breach risks may not be announced until the vulnerability they are addressing is patched to prevent additional abuse by the announcement. As such will not require public DR Submissions to implement. It requires a 67% vote of all [Data Committee](broken://pages/4TurvI5Ai2XJ8IObNjMx) members to withhold disclosure until the vulnerability is resolved, at which point it will be announced.

Any emergency Resolution shall be follower up by normal a DeEEP Resolution upon implementation which will contain the permanent solution to the emergency situation.

{% hint style="warning" %}
Emergency Resolutions will be automatically reverted after 14 days to prevent abuse of changing fundamentals of the Network without proper review, notice, and voting procedures.
{% endhint %}

### **Implementation**

**‌**There are three major ways that a Resolution may be implemented

‌**Immediate**: Resolutions that can be carried out immediately within the system. The code has already been completed or simple configuration changes.

**Core Team**: For resolutions originating from or sponsored by the Core Team. Once the vote results in an Approval the Core Team will work on the code and implement it according to the schedule that was approved.

**Community**: Resolutions that are not sponsored by the core team. The core team may not be assigned, but community members can develop the proposal into a working solution. It will then be reviewed for compliance against the proposal and coding standards and merged into production. Upon deployment this will result in the participants and author claiming the resolution funds according to the budget in the completed resolution.  The core team may choose to take projects like this on to win part of the associated budget.

## Future Models

The DeEEP Network is committed to achieving true decentralization and empowering its community of node owners and stakeholders. To fulfill this vision, we are developing a comprehensive plan to transition the network's ownership and governance to a a structure similar to a Decentralized Autonomous Organization (DAO) within a 12-18 month timeline, starting no later than the conclusion of the 50,000 piece device sale.  We will work to seek community input in this process to ensure that all voices in the DeEEP community are represented.


# DeEEP Committees

DeEEP is designed to be run for the web3 community, by the web3 community.  With that in mind the goal is to distribute the decision making to those with the right skillsets and interest that are supported by the community.

### Committee Frameworks

All committees members are nominated by a member of the DeEEP community and voted into their position for a term of 12 months. &#x20;

Committees shall meet at least every quarter in a public web meeting.  Committees may meet more often than quarterly and may meet in private, but should publish meeting minutes for the community.  Security focused committee(s) may designate portions of their meetings as restricted from the public to discuss threats that are under embargo and withhold publishing minutes for those portions.

Before the mainnet launch committees may be launched and members may be approved by a vote in Discord.

## Good Citizen Committee

The Good Citizen Committee is in charge of proposing and setting rules and guidelines for participation of all members of the DeEEP Community. &#x20;

Their responsibilities include, but are not limited to:

* Create rules preventing unfair gaming of rewards distributed to DeEEP members
* Setting standards for acceptable services that can run on DeEEP
* Setting community engagement rules and best practices to guide moderators (Discord, github, Telegram, etc)


# DeEEP Resolution

{% embed url="<https://www.figma.com/board/aVAOMr3qoOXYjU570ePVBl/Resolution-Workflow?node-id=103-1508&t=COCrmYCiOD5il9Ef-4>" %}

The process starts by starting a discussion on the NerdNode Discord in the Deeep DR channel. After soliciting feedback the author should [submit](https://github.com/nerdnode-io/dr/issues/new?assignees=\&labels=dr\&projects=\&template=proposed-resolution.md\&title=DR+--+New+Proposed+Resolution) the **Proposed Resolution** issue in the [nerdnode-io/dr](https://github.com/nerdnode-io/dr) Github repository.&#x20;

To officially submit the Resolution for voting, the author will submit a DR Submission on the blockchain. This transaction initializes the on-chain voting mechanism by requiring the author to lock $nu based on its category and creates the Proposal Fund.

**Required Information:**

* Title
* Author
* Change Type

<table><thead><tr><th width="329">Change Type</th><th>Initialization Fee</th></tr></thead><tbody><tr><td>Blockchain Configuration</td><td>100,000 $DEEEP</td></tr><tr><td>Smart Contract</td><td>100,000 $DEEEP</td></tr><tr><td>Architecture</td><td>10,000 $DEEEP</td></tr><tr><td>Infrastructure</td><td>10,000 $DEEEP</td></tr><tr><td>New Feature</td><td>10,000 $DEEEP</td></tr><tr><td>Tokenomics</td><td>1,000,000 $DEEEP</td></tr></tbody></table>

* Motivation
* Detailed Explanation
* Alternatives
* Budget / Proposal Fund

**Initialization Fee**

Is returned to the author on either a Pending Code or an Approved status of their proposal and on a Rejected status the locked $DEEEP is added to the [Community Fund](/introduction/using-usddeeep/community-fund).

**Proposal Fund**

An escrow account that's created on DR Submission onto the blockchain. It's used to collect development funds for implementing the resolution. The [Community Fund](/introduction/using-usddeeep/community-fund) can be used to bolster this based on the DR submitted.


# Get Started

Jump into the Deeep end with us! 🤿

The **Deeep** **Network** connects people with web3 assets to operate with hosts that can run them.  The network does the rest of the heavy lifting.

Which one are you?

* [**Service Owners**](/introduction/get-started/run-on-deeep): Someone who owns a web3 node, wants to run a validator, or has data that needs an permanent home.
* [**DeEEP Hosts**](/introduction/get-started/host-for-deeep): Those who host Devices in their home or business that run the Services, the backbone of the Deeep Network


# Run on DeEEP

If you're looking for a hassle-free solution to run your web3 nodes, validators and more without having to worry about security, updates, and constant firefighting, just deploy to **DeEEP**. We guarantee that your application is not just running, but also secure, up-to-date, and operating smoothly. Choose the **DeEEP Network** for a worry-free hosting experience.

## Supported Services

### Nodes

<table><thead><tr><th width="237">Service</th><th align="center">Status</th></tr></thead><tbody><tr><td><a href="https://support.gala.com/hc/en-us/articles/22440803846171-Install-the-Gala-Node-Software-on-Ubuntu-Linux"><strong>Gala Node</strong><br></a>- Founders<br>- Music<br>- Film<br>- Common Ground World<br>- Spidertanks<br>- Last Expedition</td><td align="center">✅ Available</td></tr><tr><td><a href="https://support.myria.com/hc/en-us/articles/13731603520148-Understanding-how-to-operate-a-Myria-Node"><strong>Myria Node</strong></a></td><td align="center">✅ Available</td></tr><tr><td><a href="https://support.connectunited.com/hc/en-us/articles/22584973269915-Software-Download-for-Mac-and-Linux"><strong>Smart Node</strong><br></a>- Win (Connect)<br>- Element<br>- Elevate<br>- Galvan<br>- Green<br>- Grow<br>- Lemonaide (Give)<br>- Liberty<br>- Nerd<br>- Opus<br>- Pixll<br>- Switch</td><td align="center">✅ Available</td></tr><tr><td><a href="https://nftd.gg/">NFTD</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://github.com/HYCHAIN/guardian-node-software">Hychain Node</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://xai-foundation.gitbook.io/xai-network/xai-blockchain/sentry-nodes-explained">Xai Sentry Node</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://nodes.presearch.com/run">Presearch</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://docs.aethir.com/checker-nodes-explained/how-to-run-checker-node/checker-client-linux-cli-guide">Aether Checker</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://whitepaper.starmech.io/iv.-sta-key-purchase-and-run-sta-node/running-sta-node-client">StarMech</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://docs.morpheusdata.com/en/latest/getting_started/installation/installation.html">Morpheus</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><p><a href="https://runonflux.io/nodes">Flux </a></p><p>- Cumulus<br>- Nimbus<br>- Stratus</p></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://github.com/NeoxaChain/Neoxa/tree/main/docker">Neoxa</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://docs.streamr.network/guides/become-an-operator">Streamr</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://medium.com/@BLOCX/host-your-blocx-masternode-via-flux-cloud-adcfb8a55ba6">Blocx</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://github.com/n3tsis/netsis">Netsis</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://reaction.network/">Reaction</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://subinetwork.com/">Subi</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://rheix.com/">Rheix</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://docs.mecuai.com/build-smartnode">Mecuai</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://github.com/binarybitpro/BNRY">BinaryBit</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://fsocietychain.com/docs/docs/smart-nodes/index.html">FSociety</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://maxeter.com/">Maxeter</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://varsechain.com/smartnode">Varsechain</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://fuertecoin.network/site/fuertecoin-smartnode/">Fuertecoin</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://docs.skytere.com/documents/smartnode/setup-smartnode-on-vps-linux">Skytere</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://github.com/gprotocolx/gainprox">GainproX</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://docs.raptoreum.com/raptoreum-docs/smart-nodes/smartnode-manual-setup/">Raptoreum</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://firo.org/guide/masternode-setup.html">Firo</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://github.com/aipowermeme/aipowermeme-node">AiPowerMeme</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://github.com/gaussaiorg/core">GaussAI</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://docs.thetatoken.org/docs/running-a-guardian-node-through-command-line">Theta Guardian Node</a></td><td align="center">⏳ DePIN Launch</td></tr><tr><td><a href="https://docs.gamestarter.com/game-node-keys/what-is-a-game-node/operating-a-game-node">GameChain</a></td><td align="center">Pending Node Release</td></tr><tr><td><a href="https://mergexchain.com/">MergeX</a></td><td align="center">Pending Node Release</td></tr><tr><td><a href="https://docs.carv.io/carv-protocol/verifier-node-explained">CARV Verifier Node</a></td><td align="center">Pending Node Release</td></tr><tr><td><a href="https://www.delysium.com/dma">Delysium</a></td><td align="center">Pending Node Release</td></tr><tr><td><a href="https://gunzillagames.com/en/">Gunzilla</a></td><td align="center">Pending Node Release</td></tr><tr><td><a href="https://galaxis-engines.com/">Galaxis Engines</a></td><td align="center">Pending Node Release</td></tr><tr><td><a href="https://www.metaxseed.io/nodes">Metaxseed</a></td><td align="center">Pending Node Release</td></tr><tr><td><a href="https://docs.xo-dex.com/docs/node-requirements">XODEX</a></td><td align="center">Pending Node Release</td></tr><tr><td><a href="https://docs.xally.ai/xally-ecosystem/xally-node/run-your-node/running-xally.ai-nodes/running-xally.ai-nodes-on-a-virtual-private-server-vps">Xally</a></td><td align="center">Pending CLI Node Release</td></tr></tbody></table>

### Block Chain Full Nodes

Many of these become validators with staking.

| Service                                                                                      | Status                       |
| -------------------------------------------------------------------------------------------- | ---------------------------- |
| [Bitcoin Full Node](https://bitcoin.org/en/full-node#other-linux-daemon)                     | ⏳ DePIN Launch               |
| [Base Full Node](https://docs.base.org/tutorials/run-a-base-node/)                           | ⏳ DePIN Launch               |
| [BNB Smart Chain](https://docs.bnbchain.org/docs/validator/fullnode/) Full Node              | ⏳ DePIN Launch               |
| [opBNB Full Node](https://docs.bnbchain.org/opbnb-docs/docs/tutorials/running-a-local-node/) | ⏳ DePIN Launch               |
| [Avalanche Full Node](https://docs.avax.network/nodes/run/node-manually)                     | ⏳ DePIN Launch               |
| [Polkadot Full Node](https://wiki.polkadot.network/docs/maintain-sync)                       | ⏳ DePIN Launch               |
| [Near Protocol](https://near-nodes.io/validator/hardware) Full Node                          | ⏳ DePIN Launch               |
| [Ethereum Full Node](https://ethereum.org/en/developers/docs/nodes-and-clients/run-a-node/)  | ⏳ DePIN Launch + SSD Upgrade |
| [Tron Full Node](https://developers.tron.network/docs/deploy-the-fullnode-or-supernode)      | ⏳ DePIN Launch + SSD Upgrade |
| [Pulse Chain Full Node](https://gitlab.com/Gamesys10/pulsechain-node-guide)                  | ⏳ DePIN Launch + SSD Upgrade |


# Host for DeEEP

The  Deeep Network (hardware) operators

Let your excess bandwidth make you some extra $$$.

If you're passionate about decentralized networks (DePIN) or seeking methods to monetize your unused bandwidth? If so, DeEEP can help!

**As a Device Operator, you can:**

* Help populate the infrastructure for a pioneering decentralized network.
* Monetize your unused bandwidth easily and securely.

Interested? Dive into the world of decentralized possibilities with the **DeEEP Network**!

Our [1776 Free Web3 sale](https://1776.deeep.network) is your first chance at joining us in this adventure!


# Device Sale

We will be offering a special [DeEEP 1776 sale](https://1776.deeep.network) for early adopters for those crypto patriots ready to join the revolution and free Web3 from public clouds.  These members will become the "Founding Fathers" of the DeEEP Network, earning the best rewards class and enjoying special privileges in the community.

{% hint style="success" %}
Shipments will prioritize buyers based on the their purchase time, so purchasing earlier will result in an earlier ship date.
{% endhint %}

### **Device Identity NFT (DIN)**

Each device connecting to the DeEEP Network will have a Device Identity NFT (DIN) linked to it. This NFT is linked to the private keys stored securely in a hardware TPM on the physical device. When paired with an individuals wallet the DIN instructs the network to deposit earnings from that physical device into the wallet it is tied to.  This NFT will be issued to the wallet of someone purchasing a DeEEP device when they first setup the device on their network.

## **Hardware Shipment**

The first 1776 devices will ship 10 weeks after ordering and be paired to testnet.  They will automatically be migrated to mainnet at the launch of the DeEEP mainnet!


# Partner with DeEEP

### Building the Future Together

We are committed to building the future of DePIN (Decentralized Physical Infrastructure Network) and leveraging it to build the next generation [Service](/introduction/how-it-works/services) provider. Whether you're part of a project team looking for an effortless way to deploy your Service(s) across the globe, a company eager to leverage a growing community built network, or developer looking to contribute in your free time.

#### Why build on Deeep?

* **Global Reach:** Leverage our extensive network to deploy your services worldwide effortlessly.
* **Enhanced Customer Security:** Utilize our platform to offer the the appropriate level of security to your customers and their data.
* **Quick Deployment:** Run your essential services globally with just one click.
* **Monitoring:** With 24/7 monitoring and our auto-heal system ensures that your services or project remain online when you need them to be.

Discover how you can become a part of this exciting journey with the **DeEEP** Network 🦈


# Adding Services

🚧 Work in Progress 🚧

## New Services

### What is a service? <a href="#what-is-a-service" id="what-is-a-service"></a>

The **Deeep Network** uses the word "service" to generically talk about services that are ran on the network for [Service Owners](https://app.gitbook.com/o/RagTBM9flC3Ew0PmTKDI/s/JbBweGiBOD94W5NP8Vig/introduction/get-started/run-on-deeep). These can consist of any of the following and more:

* Web3 Nodes
* Validators
* IPFS servers
* Game servers
* Web2 assets

#### What kind of services are accepted? <a href="#what-kind-of-services-are-accepted" id="what-kind-of-services-are-accepted"></a>

NerdNode only accepts services that comply with the following:

* Abide by the local laws, ordinances, and restrictions of where the service is being run
* NerdNode Services Terms of Service
* NerdNode Privacy Policy

Violations of these rules can result in permanent bans from the Network for that service and even service authors.

### How are new services added? <a href="#how-are-new-services-added" id="how-are-new-services-added"></a>

Creators of services or the community are welcome to add new services to the network. The primary requirement is that they must have software that can be ran on Linux without a Graphical User Interface (GUI).

#### Building a Service Support Package *(coming soon)* <a href="#building-a-service-support-package-coming-soon" id="building-a-service-support-package-coming-soon"></a>

* Fork the `Deeep Network Service Support Package` repository
* Copy the `template` folder and rename for your service, we recommend following the `company-service_name` format
* In the `ansible` folder modify it to support the following methods
  * `install`
  * `authorize`
  * `pre-start`
  * `start`
  * `stop`
  * `restart`
  * `deauthorize`
  * `post-stop`
  * `remove`
  * `upgrade`
* Ensure or add metrics via Prometheus
  * ​[Libraries for supporting this are provided by Prometheus project](https://prometheus.io/docs/instrumenting/clientlibs/)​
  * An example in python is provided to parse CLI outputs or log files if you cannot modify the service to support this natively
  * Make sure you are reporting at a minimum these required metrics
    * status: healthy, failed, starting, stopping, off
    * auth: authorized, authorizing, failed, missing, expiring, expired
    * uptime:
    * version: version information of the current running software
    * logs are planned to be pushed to IPFS and encrypted using the public key included in the manifest file
* Modify the local monitor script to trigger the right `start, stop, reset, install, authorize, etc` commands based on the Prometheus reporting.
* Fill out the yaml template with minimum requirements document that asks about RAM, IOPS, CPU usage, bandwidth, shared or dedicated VM, IPFS usage, secrets handling, geo-region restrictions, IPv4/6 support, logging levels, backup levels & file locations, authorization methods, public key for log and metrics encryption, etc. *(not all of these will be supported right away, but we want to capture them)*
* Using an official wallet from the organization sign the code of conduct, IP rights, and indemnification for operation in the geo-regions listed in the yaml file
* Test your service and fix any bugs
* Open a pull request in the git repo to have your service package accepted by the community.

#### Using a 3rd Party <a href="#using-a-3rd-party" id="using-a-3rd-party"></a>

Anyone, or group, can post a bounty for the community or NerdNode to create a Service Support Package.

Alternatively NerdNode can take these projects on directly. Contact <support@nerdnode.io> for more details about adding a service to the network.


# Setup your hardware

## Recommended Setup

1. Plug ethernet port 1 into your fiber/cable/DSL or other modem.
2. Plug ethernet port 2 into your router/switch/hub.
3. Plug in power to your DeEEP Device
4. Sit back and enjoy earning $DEEEP

## Alternative Setup (NAT or firewall)

You can also install your DeEEP compute box behind your router.

1. Plug ethernet port 1 into your router/switch/hub or other modem.
2. Plug in and power on your Device
3. Sit back and enjoy earning $DEEEP

{% hint style="warning" %}
Devices behind CGNAT or other NAT where ports cannot be opened are only eligible for half of the normal [Plug-In Rewards](/introduction/earning-usddeeep/tokenomics#plug-in-rewards). See [Advanced Setup](/hardware/setup-your-hardware/advanced-setups) for details on how to fix enable full rewards still.
{% endhint %}

{% hint style="info" %}
If placed after your router, for maximum rewards you need to [forward all ports](/hardware/setup-your-hardware/port-forwarding) on your router to the Device.
{% endhint %}


# Advanced Setups

DeEEP recommends using [UPnP](#using-upnp) if you already have it enabled.  If you are not already using UPnP on your router then using a [DMZ](#using-dmz-on-your-router) is the next easiest option.

## Using UPnP&#x20;

If your internet router supports UPnP *(about 3/5th have this enabled by default)* all you need to do is plug in your Deeep compute box to one of the router ports!

1. Remove the Deeep compute box from the box.
2. Plug ethernet port 1 into your router/switch/hub.
3. Plug in power to your Deeep compute box.
4. Sit back and enjoy earning $DeEEP.

## Using DMZ on your router

1. Remove the Deeep compute box from the box.
2. Plug ethernet port 1 into your router/switch/hub.
3. Plug in power to your Deeep compute box.
4. **Access your Internet Router Admin Panel**:
   * Open a web browser.
   * Enter the router’s IP address (commonly `192.168.0.1` or `192.168.1.1`) in the address bar.
   * Log in using your router's username and password.
5. **Navigate to DMZ Settings**:
   * Find the DMZ settings; it’s usually under the “Advanced” or “Security” settings.
6. **Enable DMZ**:
   * Turn on the DMZ feature.
   * Enter the IP address of the specific computer you want to place in the DMZ. This IP can often be found in the router’s DHCP client list.
7. **Save Settings**:
   * Save or apply the changes.
   * Restart your router if necessary.

## ISP with more than one public IP

[Many ISPs have the option to provide more than one public IP](/hardware/setup-your-hardware/isp-guidance-for-multiple-ips).  This is an ideal setup for Deeep.

1. Install a switch after your fiber/cable/DSL modem with a CAT5/6 cable
2. Plug the router you disconnected from the modem into the switch
   1. You may need to assign a static IP to your router depending on the instructions from your ISP
3. Plug ethernet port 1 into your router/switch/hub or other modem.
4. Plug in power to your Deeep compute box
5. Sit back and enjoy earning $DeEEP

## Behind NAT, CGNAT, or a strict firewall

You might find this on services like 4G/5G providers, Starlink, HughesNet or others that only provide carrier grade network address translation (CGNAT)

1. Remove the Deeep compute box from the box.
2. Plug ethernet port 1 into your router/switch/hub or other modem.
3. Plug in power to your Deeep compute box
4. Sit back and enjoy earning $DeEEP

{% hint style="warning" %}
Devices behind CGNAT or other NAT where ports cannot be opened will be eligible for half of the plugin rewards.
{% endhint %}


# Port Forwarding

## Detailed instructions for Various Routers

* [OpenWRT instructions](https://forum.openwrt.org/t/tutorial-how-to-add-a-device-to-dmz-on-openwrt/190247)

## Generic Router Step-by-Step Guide

**Step 1: Access Router Settings**

1. **Connect to the Router**: Ensure your computer is connected to the router via Wi-Fi or Ethernet.
2. **Open a Web Browser**: Launch your preferred web browser.
3. **Enter the Router's IP Address**: Type the router's IP address into the address bar and press Enter. Common router IP addresses are `192.168.1.1` or `192.168.0.1`.

**Step 2: Log in to the Router**

1. **Enter Username and Password**: You will be prompted to log in. Enter the router's admin username and password. If you haven't changed these, they are often set to default values like `admin` for both username and password. Check your router's manual for default credentials.

**Step 3: Locate Port Forwarding Settings**

1. **Navigate to Port Forwarding**: Once logged in, look for the Port Forwarding section. This may be under Advanced Settings, NAT, or similar headings.

**Step 4: Set Up Port Forwarding**

1. **Create a New Port Forwarding Rule**: Look for an option to add or create a new port forwarding rule.
2. **Configure the Rule**:
   * **Service Name**: Name the rule (e.g., "Open All Ports").
   * **Protocol**: Select both TCP and UDP.
   * **External Ports**: Enter a range from `1` to `65535`.
   * **Internal IP Address**: Enter the IP address of the DeEEP device. Ensure the device has a static IP address to prevent IP changes.
   * **Internal Ports**: Often, this will be the same as the external ports, `1-65535`.

**Step 5: Save and Apply Settings**

1. **Save/Apply Changes**: Save the new rule and apply the settings. The router may need to restart to apply these changes.


# ISP guidance for multiple IPs

#### Xfinity (Comcast)

1. **Check Availability**:
   * Navigate to Xfinity Support Rate Card and log in with your Xfinity account credentials.
   * Open the PDF file to check if "Additional IP address" is listed as an option.
2. **Request an Additional IP Address**:
   * If available, post a request on the Xfinity forum, specifying your interest in an additional IP address and confirming that you’ve checked the rate card.
   * A Comcast official employee will assist you from there.
3. **Considerations**:
   * Availability may be restricted due to the declining number of public IPv4 addresses. If your area no longer offers multiple IPs, existing add-ons may be grandfathered as long as no changes are made to the plan, account, or equipment​ ([Xfinity Community Forum](https://forums.xfinity.com/conversations/internet/answered-how-to-get-multiple-ipv4-addresses-for-your-modem/602daff6c5375f08cd1db24c))​.

#### AT\&T

1. **Contact Customer Support**:
   * Call AT\&T customer support or use the online chat to inquire about obtaining multiple IP addresses.
2. **Business Plan Requirement**:
   * Multiple IP addresses are often only available with business plans. Discuss with the support representative to see if your residential plan can be upgraded or if a business plan is needed.
3. **Configuration**:
   * If approved, AT\&T will provide instructions and possibly new equipment to configure the additional IP addresses.

#### Verizon

1. **Business Services**:
   * Similar to AT\&T, Verizon typically provides multiple IP addresses through their business services. Contact Verizon support to discuss your needs.
2. **Request and Approval**:
   * If you are a business customer or can upgrade to a business plan, request additional IP addresses.
3. **Technical Setup**:
   * Verizon will guide you through the technical setup and may provide a modem or router that supports multiple IP addresses.

#### Spectrum

1. **Customer Support Inquiry**:
   * Contact Spectrum customer support to ask about the availability of multiple IP addresses.
2. **Plan Upgrade**:
   * Spectrum may require an upgrade to a business plan for additional IP addresses. Discuss the options with the support representative.
3. **Setup**:
   * Once approved, Spectrum will provide the necessary configuration details and support to set up the multiple IP addresses.


# MS-01-DeEEP

We have partnered with MinisForums as our first [Hardware Manufacturer](/introduction/how-it-works#hardware-manufacturers).

<figure><img src="https://1998362903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEuDZ2zxXJpyX1YOwexzL%2Fuploads%2FiVrsZ925agqLTkaJX6vS%2Fimage.png?alt=media&amp;token=1c724230-62b4-4e92-9123-00200f68a296" alt=""><figcaption></figcaption></figure>

* **Overview**: Required for hosting the network, using off-the-shelf computers preconfigured for secure computing.
* **Specifications**:
  * Intel chipsets with vPRO Enterprise, TPM 2.0, encrypted RAM, complete boot validation.
  * 32GB RAM, 1TB NVMe drive, 2 free NVMe slots, full-size PCIe slot, dual USB 4 ports.
  * Dual NIC support with two 2.5Gbps ports and two 10Gbps ports.
* **Convertibility**: Can be reset to a normal computer using a BIOS and TPM reset if you want out of DeEEP.
* More specs can be found at <https://store.minisforum.com/products/minisforum-ms-01>


# Roadmap

The DeEEP Network project utilizes GitHub Projects to organize its roadmap through a series of milestones, where each task is categorized under Network, Devices, or Services categories using labels. The project board implements a swimlane view, allowing tasks to be visualized and tracked both by their milestone and category. While work can begin on tasks in later milestones, the completion of these tasks should not be expected until all tasks in the previous milestone are completed. This structure ensures systematic progress across all three technical domains (Network, Devices, and Services) while acknowledging dependencies between development phases.

{% embed url="<https://github.com/orgs/deeep-network/projects/1>" %}


# DeEEP Network

The DeEEP network was started in 2023 when the NerdNode team started to distribute their node management software. &#x20;

In June of 2024 the DeEEP network will launch publicly.


# NerdNode

NerdNode is the founding team behind the DeEEP Network.  Our goal is to make a safe, secure and efficient decentralized computing network.

NerdNode was created when our team came together with experience in blockchain gaming and distributed computing. On the blockchain side our team had built and invested in distributed ownership, governance, and hosting of games, media and other Web3 assets. With millions of dollars invested in Web3 nodes and assets, they were looking for a way to do actual distributed computing with them. The other half of the team had deep experience in distributed computing. Through IoT edge computing gateways and edge devices they put millions of edge workloads out into the field securely, used by leading brands worldwide, managed completely remotely and autonomously. While most of the world focused on centralizing in a few cloud datacenters. They were moving workloads to the very edge and keeping them just as simple to manage.

Looking at the Web3 space they came together to build NerdNode. Starting with a small, centralized solution that was local to the team to work through the issues and gradually growing the hardware, management software and customer base into a scalable solution. The system has grown to manage many thousands of nodes with a profitable revenue base. After about 2 years of work the team is now ready to launch the DeEEP DePIN network that can scale globally and permit true decentralization with secure computing.

At the launch of the DeEEP Network, NerdNode is hosting many thousands of web3 nodes running on NerdNode owned hardware that is semi-decentralized.  NerdNode is commuted to moving all of this to a fully decentralized DeEEP Network and growing the ecosystem.


