# Internal Tasks

## Overview

Internal Tasks are consensus-based modules for ongoing maintenance of the AVS network. Each module is purpose-built for a specific function and is carried out by the AVS Operators. 

Each internal task is:

* Registered with a unique **Task Definition ID**
* Validated by Attesters
* Scheduled based on frequency configured via environment variables, which can vary depending on the operational requirements.

The execution and validation of internal tasks are facilitated by the same operator set and consensus engine used by the AVS, ensuring that they adhere to the same consensus standards as core AVS Tasks.

<figure><picture><source srcset="https://4144525652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYlSi30nrcEOossIDFFua%2Fuploads%2F54ENdvhhOwynqEvKQP6T%2FInternal%20tasks%20Dark%20Mode.png?alt=media&#x26;token=9334bd0a-3b28-416e-b9bc-ae8a989622a7" media="(prefers-color-scheme: dark)"><img src="https://4144525652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYlSi30nrcEOossIDFFua%2Fuploads%2FuFD579vn7jHSo4OTSVxe%2Fimage.png?alt=media&#x26;token=10306102-867c-4f9a-98d8-73ffa87f2bea" alt=""></picture><figcaption></figcaption></figure>

Whenever an internal task is executed, a proof of task is generated. The generated proof, along with task execution data, is broadcast internally to the P2P network. [**Attesters**](https://docs.othentic.xyz/main/core-concepts/operator-roles#attesters) validate the execution by verifying the proof and recalculating expected outcomes.

{% hint style="warning" %}
Internal tasks are only supported for Task Definition IDs greater than 0. To use internal tasks, ensure that you have created and configured a Task Definition.
{% endhint %}

#### Usage

* [Guide: Configure Internal Tasks](https://docs.othentic.xyz/main/user-guide/network-management/setup-internal-tasks) - step-by-step instructions to run Internal Tasks.

***

## Types of Internal Tasks

### 1. Sync Voting Power

**Task Definition ID**: `10001`

**Task Name**: `VOTING_POWER_SYNC`

The Operator's voting power is proportional to the amount of (re)stake assets locked to secure the AVS, and determine the influence of individual Operators over the consensus process.&#x20;

#### **Voting Power Calculation and Syncing Logic**

* Fetches the voting power from both L1 and L2
* Computes the difference
* Broadcasts a proposed voting power update to the P2P network.
* Attesters validate the proposed update against recalculated values.

***

### **2. Voting Power Sync Per Task Definition**

**Task Definition ID**: `10002`

**Task Name**: `VOTING_POWER_PER_TASK_DEFINITION_SYNC`

This task synchronizes voting power **specific to each task definition.**