329780
Erigon
@erigon #329780
We build Ethereum technology on the efficient software frontier.
https://erigon.tech/
53 Follower 71 Following
new release: https://github.com/erigontech/erigon/releases/tag/2.60.8
This release schedules the Ahmedabad hardfork for the @0xpolygon mainnet and the Gandhinagar hardfork for Amoy. Thus it's mandatory for all Polygon users.
This release also fixes Issue #11936 debug trace RPC error in Polygon Amoy.
This release schedules the Ahmedabad hardfork for the @0xpolygon mainnet and the Gandhinagar hardfork for Amoy. Thus it's mandatory for all Polygon users.
This release also fixes Issue #11936 debug trace RPC error in Polygon Amoy.
new release: https://github.com/erigontech/erigon/releases/tag/2.60.7
WARNING :
As of this release, we are introducing some changes to our release process, PLEASE READ THE RELEASE NOTES 👇 👇 👇
WARNING :
As of this release, we are introducing some changes to our release process, PLEASE READ THE RELEASE NOTES 👇 👇 👇
Erigon 3 Alpha 3 released!
ATTENTION: resync required (well, not a big deal with Erigon 3)
coolest things in Erigon 3 Alpha 3:
1- mining support (Yeah!)
2- latest state (domain folder) size reduced by 30% (~200gb on bor-mainnet)
3- 2x reduced chaindata: 12Gb on eth-mainnet, 32Gb on bor-mainnet
4- 2x less RAM: 25Gb on eth-mainnet, 40Gb on bor-mainnet. We will reduce it in future
5- prune doesn't impact chain-tip performance
https://github.com/erigontech/erigon/releases/tag/3.0.0-alpha3
ATTENTION: resync required (well, not a big deal with Erigon 3)
coolest things in Erigon 3 Alpha 3:
1- mining support (Yeah!)
2- latest state (domain folder) size reduced by 30% (~200gb on bor-mainnet)
3- 2x reduced chaindata: 12Gb on eth-mainnet, 32Gb on bor-mainnet
4- 2x less RAM: 25Gb on eth-mainnet, 40Gb on bor-mainnet. We will reduce it in future
5- prune doesn't impact chain-tip performance
https://github.com/erigontech/erigon/releases/tag/3.0.0-alpha3
new release: https://github.com/ledgerwatch/erigon/releases/tag/v2.60.0
v2.60.0 The Last of Erigon 2 is out!
This release, v2.60.0, is the last significant release based on Erigon 2. There might be patch v2.60.x releases for critical issues, but by and large, we intend all future development to be based on Erigon 3.
v2.60.0 The Last of Erigon 2 is out!
This release, v2.60.0, is the last significant release based on Erigon 2. There might be patch v2.60.x releases for critical issues, but by and large, we intend all future development to be based on Erigon 3.
new rc-release : https://github.com/ledgerwatch/erigon/releases/tag/v2.60.0-rc1
Important: We plan this release, v2.60.0, to be the last significant release based on Erigon 2. There might be patch v2.60.x releases for critical issues, but by and large, we intend all future development to be based on Erigon 3.
Important: We plan this release, v2.60.0, to be the last significant release based on Erigon 2. There might be patch v2.60.x releases for critical issues, but by and large, we intend all future development to be based on Erigon 3.
new patch release: https://github.com/ledgerwatch/erigon/releases/tag/v2.59.2
This patch release fixes an MDBX size/performance regression introduced in v2.58.0.
This patch release fixes an MDBX size/performance regression introduced in v2.58.0.
We are proud to announce Erigon++ (E++), a set of C++ software libraries integrated into Erigon which harness the power of EVMONE.
Details in the post below:
https://erigon.tech/erigonpp/
Details in the post below:
https://erigon.tech/erigonpp/
new release (Polygon, Napoli HF): https://github.com/ledgerwatch/erigon/releases/tag/v2.58.2
Polygon mainnet users: You must upgrade to this release or later before the Napoli hard fork (March 20th, 2024)
Polygon mainnet users: You must upgrade to this release or later before the Napoli hard fork (March 20th, 2024)
new patch release: https://github.com/ledgerwatch/erigon/releases/tag/v2.58.1
What's Changed:
mainnet: remove beacon after 8M by @AskAlexSharov in #9480
snapshots: fix filesByRange by @battlmonstr in #9489
What's Changed:
mainnet: remove beacon after 8M by @AskAlexSharov in #9480
snapshots: fix filesByRange by @battlmonstr in #9489
We are thrilled to announce the arrival of Caplin archive format.
With Caplin archival mode is now possible to maintain an up-to-date history of the Beacon Chain.
more on our blog post 👇
https://erigon.tech/update-on-caplin-and-roadmap-building-a-consensus-layer-client-to-work-with-erigon-without-the-engine-api/
With Caplin archival mode is now possible to maintain an up-to-date history of the Beacon Chain.
more on our blog post 👇
https://erigon.tech/update-on-caplin-and-roadmap-building-a-consensus-layer-client-to-work-with-erigon-without-the-engine-api/
GM! Farcaster