# AIP 7: Network Parameter Updates for Faster Finality, Larger Blocks, and Improved Authoring Resilience

**URL:** <https://forum.availproject.org/t/aip-7-network-parameter-updates-for-faster-finality-larger-blocks-and-improved-authoring-resilience/1734>\
**Category:** Avail Improvement Proposal (AIP)\
**Created:** [October 9, 2025, 10:44am UTC](https://forum.availproject.org/t/aip-7-network-parameter-updates-for-faster-finality-larger-blocks-and-improved-authoring-resilience/1734 "2025-10-09T10:44:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Toufeeq\_Pasha](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.availproject.org/toufeeq_pasha/32/858_2.png) [@Toufeeq\_Pasha](https://forum.availproject.org/u/Toufeeq_Pasha)\
**Post date:** [October 9, 2025, 10:44am UTC](https://forum.availproject.org/t/aip-7-network-parameter-updates-for-faster-finality-larger-blocks-and-improved-authoring-resilience/1734/1 "2025-10-09T10:44:38Z")

</div>

**Author:** Toufeeq

**Technical Summary**

This AIP proposes a set of network parameters and node configuration updates that have already been deployed and validated on the **Turing testnet**. These updates aim to improve block finality times, increase block capacity at the node level, and enhance network resilience during temporary finality stalls. The key changes are:

- **Decrease finality gap** from 2 blocks to **1 block** from the best block, enabling blocks to finalise in ~20 seconds (down from ~40 seconds).

- **Increase supported block size** in the node binary up to **64 MiB** , allowing for significantly higher data throughput and scalability.

- **Update block authoring backoff strategy** to limit the maximum delay to **5 minutes** during finality stalls, preventing extended authoring inactivity.

- **Increase the number of primary slots** to a probability of **1/3** (from 1/4), improving slot utilisation and reducing missed block production when some validators are offline.

## **Motivation**

These proposed updates are part of the ongoing optimisation of Avail’s consensus and data-availability layers to support larger workloads, faster confirmations, and smoother authoring behaviour under varied network conditions.

1. **Faster Finality:**

2. **Higher Block Capacity:**

3. **Authoring Stability During Finality Stalls:**

4. **Improved Slot Coverage:**

## **Rationale and Reasoning**

All proposed changes have been successfully tested and validated on the **Turing testnet** under realistic network conditions. The results demonstrated:

- **No degradation in block propagation or finality metrics** at higher block sizes.

- **Stable validator performance** and resource usage during increased load.

- **Significant improvement in block finalisation speed** , now consistently around 20 seconds.

- **Reduced missed-slot occurrences** under partial validator downtime scenarios.

These adjustments ensure that Avail remains performant, responsive, and ready for scaling use cases that demand higher throughput and reduced confirmation latency.

## **Security Considerations or Risks**

Testing on Turing confirms that these updates introduce **no additional security or stability risks**.

- The finality gap reduction maintains safety guarantees of GRANDPA while improving finality.

- Larger block size support only expands node capacity limits and does not alter consensus rules.

- The backoff cap ensures predictable authoring recovery

- Adjusted slot probabilities retain fairness while improving overall slot utilisation.

The first three changes can be enacted through a binary release, while the fourth requires a governance proposal to update the relevant runtime configuration parameters.

## **Copyright Waiver**

Copyright and related rights waived via CC0.