> For the complete documentation index, see [llms.txt](https://canopy-network.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://canopy-network.gitbook.io/docs/canopy-network/core-features/nestbft/poage-is-trustless.md).

# PoAge Is Trustless

### Canopy's Proof-of-Age

Canopy introduces a unique mechanism to allow trustless syncing of the blockchain:

{% hint style="info" %}
Verifiable-Delay-Functions are a cryptographic primitive that requires the execution of sequential work that is fundamentally resistant to hardware speedups.
{% endhint %}

In other words...VDFs are a reliable proxy for elapsed time. This enables Canopy to reliably utilize a fork-choice rule of the oldest (age) chain, allowing a syncing node **strong subjectivity** when choosing between two forks.

{% hint style="info" %}
TL;DR: Like PoW — Proof-of-Age enables trustless syncing, but without the energy costs!
{% endhint %}

### <mark style="color:blue;">The Result: NestBFT</mark>

NestBFT uses Proof-of-Stake for:

* Energy-efficient consensus
* Simple and self-reinforcing 'sybil attack' protection
* Instant finality with 20-second blocks
* Economic stability via bonding&#x20;

... and Proof-of-Age for:

* Verifiable mitigation of Long-Range-Attacks
* An additional layer of security against emerging threats
* Extending security to Nested Chains by offering decentralized Checkpointing-As-A-Service

The combination of the two ensures NestBFT is fundamentally more trustless than legacy PoS systems.

{% hint style="warning" %}
Since trust is involved with Ethereum's Gasper and Tendermint's BFT, how much of Web3 is truly trustless?
{% endhint %}

Read the full specification of [Canopy's Consensus](/docs/canopy-network/understand-the-protocol/consensus.md)!