Image link
TAKE A TOUR
WHO WE ARE AND WHAT WE DO

We are a team of talented engineers and industry experts spread across 4 continents with a common goal: approach the efficient software frontier. We focus on Ethereum and its ecosystem, by integrating our latest technologies to an efficient software frontier. Our name Erigon recalls the Macedonian river, also known as the Black River.

SWITZERLAND, 2017
BORN FROM AN IDEA

Create a client on the efficient software frontier for Ethereum

The founding father is software engineer Alexey Akhunov. He wanted to improve clients (besides Geth) in order to solve the Ethereum issues caused by the CryptoKitties Congestion Crisis. After several research, he found out where and how to build his client from Geth’s codebase. That’s how Erigon was brought to life. (Along the research journey he was joined by Andrew Ascikhimin, Igor Mandgrin and Alex Sharon).

THE RELEASE EVOLUTION

Image link
ERIGON
Turbogeth then, Erigon today

Besides Turbogeth’s innovations, Erigon in its first version proved to be the only Ethereum client able to synchronize in Full Archive Node mode without requiring professional hardware or weeks of time.

In the past Erigon was known as Turbogeth, a deeply modified fork of Geth.

On 30th July 2020, the first alpha of Turbogeth was born. Turbogeth brought several innovations to the architecture of Geth:

  • Staged sync
  • Plain state data model
  • Modular software design
  • Compact history storage

Erigon proved to be the only Ethereum client that could realistically be used as a Full Archive Node:

  • Disk footprint: 1.22TB @block 12,5 m
  • Performant RPC Daemon 
  • 80 hr to sync a full archive node
ERIGON 2
Born on 21 April 2022 to get the Ethereum client on the software frontier. Here are the 2nd version brand new features:
  • Concept of torrent sync
  • Data model improvement
  • Embedding of light Consensus Layer client
  • Gnosis Chain & Polygon Chain partnership

Here are the 2nd version innovations

  • BitTorrent downloader
  • Tx pool module
  • Embedded light Consensus Layer client
  • Gnosis Chain as official supporter
  • Disk footprint: 1.51TB @block 16m
  • 65 hr to sync a full archive node
Image link
Image link
ERIGON 3 & CAPLIN
Erigon becomes the first full-fledged or complete ethereum client, capable of operating on both the consensus and execution layers

In the course of 2023, Erigon reaches full maturity as a complete ethereum client (both CL and EL) on the efficient software frontier and in all conditions of use.

 

With Caplin, Erigon is aimed at reaching the following goals:

  • Ultra fast and compact sync for full archive nodes 
  • Flexible commitment
  • Easy consensus layer management
  • The full node on the software efficiency frontier

In this regard, Erigon 3 will provide different services that are:

  • Easier support for large chains (like Polygon)
  • Data granularity at transaction level
  • Consensus driven engine
  • Embedded full consensus layer client (Caplin)
  • Download state from BitTorrent instead executi0n replay
  • A more flexible commitment engine

DLT TIMELINE

Navigational DB Model
Two DB models became successful in this decade: a hierarchical one called IMS and a network model called IDS. IMS used blocks of data (segments) that contained several pieces of data (fields). Instead, IDS was an early network database system that became the basis for the CODASYL Data Model, which used two data storage methods, i.e BDAM and linked-list data structure.

Relational DB Model
During the 70s the hierarchical database models lost popularity in favour of two major relational models:

Ingres and System R. Ingres began as a research project at UC Berkeley, California. This SQL relational database system was largely used on DEC machines and was similar to IBM’s System R. This last one has been the first seminal database system to use SQL; it has also shown that relational DB models could provide good transaction processing performance.

Part One: Temporal DB Model (ledger)
The 1980s saw the query language (SQL) became the standard language used for databases. A key event in the mid 80s is the emergence of Object-oriented database management, which viewed data as ‘objects’. Additionally, a multi-model database management system was released: the Oracle Database. It was used for online transaction processing and data warehousing. PostgreSQL was developed at Berkeley to support multiple data types. Instead, IBM Db2 was created by IBM to support object-relational features.

Part Two: Distributed SQL DB Model
The advent of the World Wide Web impacted the history of databases. The Internet became a great resource for the development of the database industry. PostgreSQL 9.2 and IBM Db2 10 are two useful examples of advancements in technology. The first one counts several improvements as concerns scalability and flexibility. On the other hand, IBM Db2 10 is faster, works more efficiently and supports RDF (Resource Description Framework) data format.

Distributed Provable Ledger model (with commitment)
Technology has improved considerably over the last years, leading to a fourth generation of database: blockchains. These are distributed databases or ledgers that store data in specific blocks which are linked together via cryptography. Moreover, Spanner was developed by Google to perform arbitrary queries using SQL with relational data. Instead, Apache Ignite was developed by GridGain Systems to give high performance computing with in-memory speed. 

Image link
TEAM
PROFESSIONAL NETWORK
Administrators
0
Programmers
0
Nationalities
0
NETWORK
PARTNER & ECOSYSTEM

PARTNER

Gnosis Dao
Ethereum Foundation
Polygon

ECOSYSTEM

OUR TEAM

Paweł Bylica

Nane Vardanyan

Max Revitt

Evgeny Danilenko