Skip to content

Update milestones.md #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
arash009 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update milestones.md #25

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c5e77ad
Update milestones.md
arash009 Jul 31, 2025
e46fe3a
Update milestones info
cooganb Aug 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions docs/pos/tutorials/milestones.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,30 @@
<!--
---
comments: true
---
-->

# Understanding and Implementing Milestones with Bor and Heimdall in Polygon PoS

!!! info "5 Second Finality in Polygon"

NOTE: With the upgrade to Heimdall v2, deterministic finality on PoS is now achieved in between 3-5 seconds thanks to the subsecond block times in Heimdall, meaning miletones are voted on and finalized much faster.

## How to get Finalized Block

Simply use the standard eth_getBlockByNumber JSON-RPC method with the "finalized" block parameter to retrieve information about the most recently finalized block in Polygon PoS. Finalized blocks are considered highly secure and irreversible, making them crucial for applications requiring strong transaction certainty.

To get the finalized block, you can use the following JSON-RPC call:

Code

{
"method": "eth_getBlockByNumber",
"params": ["finalized", true],
"id": 1,
"jsonrpc": "2.0"
}

## Introduction to Bor and Heimdall in Polygon PoS

### What is Bor?
Expand Down