Go Ethereum

Open-source Go projects categorized as Ethereum

Top 23 Go Ethereum Projects

  • go-ethereum

    Go implementation of the Ethereum protocol

    Project mention: Ethereum Foundation removes their canary | news.ycombinator.com | 2024-03-20

    Even more relevant would be the Ethereum Improvement Proposal repo (where people submit proposals to change the spec):

    https://github.com/ethereum/EIPs

    Or the go-ethereum execution client (the most popular execution client):

    https://github.com/ethereum/go-ethereum

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • optimism

    Optimism is Ethereum, scaled.

  • quorum

    A permissioned implementation of Ethereum supporting data privacy

  • prysm

    Go implementation of Ethereum proof of stake

    Project mention: Did I break CURL ? can't update my validator from github | /r/ethstaker | 2023-07-22

    curl -LO https://github.com/prysmaticlabs/prysm/releases/download/v4.0.7/beacon-chain-v4.0.7-modern-linux-amd64

  • awesome-blockchain

    ⚡️Curated list of resources for the development and applications of blockchain.

  • turbo-geth

    Ethereum implementation on the efficiency frontier

    Project mention: AMD EPYC 7C13 Is a Surprisingly Cheap and Good CPU | news.ycombinator.com | 2024-03-27

    To be clear, it was a CPU fault that doesn't occur at all when running e.g. stress-ng, but only (as far as I know) when running our particular production workload.

    And only after several hours of running our production workload.

    But then, once it's known to be provokeable for a given machine, it's extremely reliable to trigger it again — in that it seems to take the same number of executed instructions that utilize the faulty part of the die, since power on. (I.e. if I run a workload that's 50% AES-NI and 50% something else, then it takes exactly twice as long to fault as if the workload was 100% AES-NI.)

    And it isn't provoked any more quickly, by having just provoked it with the last hard-fault — i.e. there's no temporal locality to it. Which would make both "environmental conditions" and "CPU is overheating / overvolting" much less likely as contributing factors.

    > There have been enough of them in private hands for long enough that if there were widespread issues they would be well-known.

    Our setup is likely a bit unusual. These machines that experienced the faults, have every available PCIe lane (other than the few given to the NIC) dedicated to NVMe; where we've got the NVMe sticks stuck together in software RAIDO (meaning that every disk read fans in as many almost-precisely-parallel PCIe packets contending for bus time to DMA their way back into the kernel BIO buffers.) On top of this, we then have every core saturated with parallel CPU-bottlenecked activity, with a heavy focus on these AES-NI instructions; and a high level of rapid allocation/dellocation of multi-GB per-client working arenas, contending against a very large and very hot disk page cache.

    I'll put it like this: some of these machines are "real-time OLAP" DB (Postgres) servers. And under load, our PG transactions sit in WAIT_LWLOCK waiting to start up, because they're actually contending over acquiring reader access to the global in-memory pg_locks table in order to write their per-table READ_SHARED locks there (in turn because they're dealing with wide joins across N tables in M schemas where each table has hundreds of partitions and the query is an aggregate so no constraint-exclusion can be used.) Imagine the TLB havoc going on, as those forked-off query workers fight for time.

    It's to the point that if we don't either terminate our long-lived client connections (even when not idle), or restart our PG servers at least once a month, we actually see per-backend resource leaks that eventually cause PG to get OOMed!

    The machines that aren't DB servers, meanwhile — but are still set up the same on an OS level — are blockchain nodes, running https://github.com/ledgerwatch/erigon, which likes to do its syncing work in big batches: download N blocks, then execute N blocks, then index N blocks. The part that reliably causes the faults is "hashing N blocks", for sufficiently large values of N that you only ever really hit during a backfill sync, not live sync.

    In neither case would I expect many others to have hit on just the right combination of load to end up with the same problems.

    (Which is why I don't really believe that whatever problem AMD might have seen, is related to this one. This seems more like a single-batch production error than anything, where OVH happened to acquire multiple CPUs from that single batch.)

    > It's possible that AMD didn't order enough capacity from TSMC to meet demand, and couldn't get more during the COVID supply chain issues.

    Yes, but that doesn't explain why they weren't able to ramp up production at any point in the last four years. Even now, there are still likely some smaller hosts that would like to buy EPYC 7xxxs at more-affordable prices, if AMD would make them.

    You need an additional factor to explain this lack of ramp-up post-COVID; and to explain why the cloud providers aren't still buying any 7xxxs (which they would normally do, to satisfy legacy clients who want to replicate their exact setup across more AZs/regions.) Server CPUs don't normally have 2-year purchase commitments. It's normally more like 6.

    Sure, maybe Zen4c was super-marketable to the clouds' customers, so they negotiated with AMD to drop all their existing spend commitments on 7xxx parts purchases in favor of committing to 9xxx parts purchases. (But why would AMD agree to that, without anything the clouds could hold over their head? It would mean shutting down many of the 7xxx production lines early, translating to the CapEx for those production lines not getting paid off!)

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
  • bsc

    A BNB Smart Chain client based on the go-ethereum fork

  • evmos

    Evmos is the first decentralized EVM chain on the Cosmos Network. It's implementing the first EVM stack focused on native, cross-chain applications. Evmos is the flagship implementation of Ethermint, an EVM library built for the Cosmos Network by the Evmos Core Developement Team.

    Project mention: Guide to Setting Up Evmos CLI for ERC20 to IBC Token Conversion | /r/EVMOS | 2023-11-24

    Go to Evmos Releases on GitHub.

  • bee

    Bee is a Swarm client implemented in Go. It’s the basic building block for the Swarm network: a private; decentralized; and self-sustaining network for permissionless publishing and access to your (application) data.

  • open-ethereum-pool

    Open Ethereum Mining Pool

  • mev-boost

    MEV-Boost allows Ethereum validators to source high-MEV blocks from a competitive builder marketplace

    Project mention: mevboost proposal error | /r/ethstaker | 2023-07-07
  • trueblocks-core

    The main repository for the TrueBlocks system

  • bor

    Official repository for the Polygon Blockchain

    Project mention: Best Crypto To Invest in 2024 [Expert Guide] | dev.to | 2023-12-29

    Polygon (MATIC) – Scaling Ethereum Today

  • polygon-edge

    A Framework for Building Ethereum-compatible Blockchain Networks

  • status-go

    The Status module that consumes go-ethereum

  • go-livepeer

    Official Go implementation of the Livepeer protocol

  • firefly

    Hyperledger FireFly is the first open source Supernode: a complete stack for enterprises to build and scale secure Web3 applications. The FireFly API for digital assets, data flows, and blockchain transactions makes it radically faster to build production-ready apps on popular chains and protocols. (by hyperledger)

  • ethgo

    Ethereum Golang API

  • mev-boost-relay

    MEV-Boost Relay for Ethereum proposer/builder separation (PBS)

  • core

    Decentralized Fog Computing Platform (by sonm-io)

  • atomic-swap

    💫 ETH-XMR atomic swap implementation

    Project mention: MAGIC Monero Fund 2024 Election - If you would like to contribute to an organization that funds R&D and educational outreach for Monero consider participating as a voter or a committee member! | /r/CryptoCurrency | 2023-12-07
  • snowbridge

    A trustless bridge between Polkadot and Ethereum

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
NOTE: The open source projects on this list are ordered by number of github stars. The number of mentions indicates repo mentiontions in the last 12 Months or since we started tracking (Dec 2020).

Go Ethereum discussion

Log in or Post with

Go Ethereum related posts

  • AMD EPYC 7C13 Is a Surprisingly Cheap and Good CPU

    1 project | news.ycombinator.com | 27 Mar 2024
  • Ethereum Foundation removes their canary

    4 projects | news.ycombinator.com | 20 Mar 2024
  • Best Crypto To Invest in 2024 [Expert Guide]

    5 projects | dev.to | 29 Dec 2023
  • Em Defesa de Anti-Crypto

    1 project | /r/literaciafinanceira | 9 Dec 2023
  • MAGIC Monero Fund 2024 Election - If you would like to contribute to an organization that funds R&D and educational outreach for Monero consider participating as a voter or a committee member!

    1 project | /r/CryptoCurrency | 7 Dec 2023
  • How I Contributed One Line of Code to Ethereum

    7 projects | dev.to | 26 Nov 2023
  • Guide to Setting Up Evmos CLI for ERC20 to IBC Token Conversion

    1 project | /r/EVMOS | 24 Nov 2023
  • A note from our sponsor - SaaSHub
    www.saashub.com | 24 Jun 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Index

What are some of the best open-source Ethereum projects in Go? This list will help you:

Project Stars
1 go-ethereum 46,574
2 chainlink 6,804
3 optimism 5,191
4 quorum 4,599
5 prysm 3,394
6 awesome-blockchain 3,115
7 turbo-geth 3,021
8 bsc 2,627
9 evmos 1,643
10 bee 1,442
11 open-ethereum-pool 1,373
12 mev-boost 1,115
13 trueblocks-core 1,036
14 bor 983
15 polygon-edge 983
16 status-go 717
17 go-livepeer 534
18 firefly 484
19 ethgo 467
20 mev-boost-relay 408
21 core 359
22 atomic-swap 339
23 snowbridge 280

Sponsored
Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com