Erigon 3 Update Slashes BSC Sync Time from Weeks to 10 Hours

Erigon
3,
the
latest
iteration
of
the
Ethereum
client
adapted
for
the
BNB
Chain
(BSC),
has
dramatically
improved
synchronization
times,
reducing
them
from
weeks
to
just
10
hours.
This
significant
update
incorporates
the
Parlia
consensus
protocol,
which
is
integral
to
BSC’s
speed
and
cost-efficiency,
supporting
its
extensive
decentralized
application
ecosystem,
according
to

BNB
Chain
Blog.

What
is
Parlia

Parlia
is
BSC’s
consensus
mechanism,
blending
Delegated
Proof
of
Stake
(DPoS)
and
Proof
of
Authority
(PoA).
This
hybrid
approach
allows
for
faster
block
times
and
reduced
transaction
costs.
Validators
are
elected
by
BNB
holders,
ensuring
decentralization
while
maintaining
efficiency.
The
integration
of
Parlia
into
Erigon
3
ensures
the
client
meets
BSC’s
operational
needs,
offering
enhanced
performance,
particularly
for
users
running
Archive
nodes.

BSC
Testnet
–
Sync
Time
Reduced
from
One
Week
to
10
Hours

Performance
metrics
from
the
BSC
Testnet
(Chapel)
reveal
substantial
improvements.
Disk
usage
has
been
cut
by
50%,
and
the
sync
time
for
Erigon
3
on
Chapel
has
been
reduced
to
approximately
10
hours,
compared
to
about
one
week
with
the
previous
version.

Current
State

The
latest
Alpha
2
version
of
Erigon
3
has
successfully
ported
the
Parlia
consensus
protocol,
ensuring
full
compatibility
with
BSC.
Users
can
now
benefit
from
Erigon’s
optimized
performance
and
reduced
resource
footprint.
The
testnet
snapshot
is
ready
for
trial,
and
users
are
encouraged
to
provide
feedback
to
identify
any
remaining
issues.
Notably,
Erigon
3
eliminates
the
need
for
manual
snapshot
downloads,
as
the
client
automatically
retrieves
the
latest
snapshot.

Mainnet
Plan

The
mainnet
version
of
Erigon
3
is
expected
to
be
released
around
September
30,
2024.
During
the
transition,
support
for
Erigon
2
will
continue
to
ensure
a
smooth
upgrade
process.

How
to
Try
Erigon
3

Using
Git
and
Building

Downloading
Pre-Built
Binary

Alternatively,
users
can
download
a
pre-built
binary
for
their
system
from

here

Using
Docker
Image

Notes:

• Replace “<your_data_path>”
  with
  the
  actual
  path
  where
  you
  want
  to
  store
  your
  data.
• Ensure
  the
  correct
  binary
  file
  is
  downloaded
  based
  on
  your
  operating
  system.

Image
source:
Shutterstock