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. Learn more →
Top 23 Go Blockchain Projects
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
fabric
Hyperledger Fabric is an enterprise-grade permissioned distributed ledger framework for developing solutions and applications. Its modular and versatile design satisfies a broad range of industry use cases. It offers a unique approach to consensus that enables performance at scale while preserving privacy.
-
go-ibax
An innovative Blockchain Protocol Platform, which everyone can deploy their own applications quickly and easily, such as Dapp, DeFi, DAO, Cross-Blockchain transactions, etc.
-
-
-
-
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.
-
-
-
-
-
-
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.
-
-
-
-
-
cli
Ignite is a CLI tool and hub designed for constructing Proof of Stake Blockchains rooted in Cosmos-SDK (by ignite)
-
node
Mysterium Network Node - official implementation of distributed VPN network (dVPN) protocol (by mysteriumnetwork)
-
IceFireDB
@IceFireLabs -> IceFireDB is a database built for web3.0 It strives to fill the gap between web2 and web3.0 with a friendly database experience, making web3 application data storage more convenient, and making it easier for web2 applications to achieve decentralization and data immutability.
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
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
Install LND: https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md#install-lnd Install Bitcoin Core: https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md#building-with-mingw-w64-cross-tools
Chainlink (LINK) – The Blockchain Oracle Giant
Project mention: Building Your Own Blockchain: A Beginner’s Guide to Setting Up and Using Cosmos | dev.to | 2024-04-10
Tendermint Core / CometBFT — a state machine replication engine (written in Go);
Project mention: AMD EPYC 7C13 Is a Surprisingly Cheap and Good CPU | news.ycombinator.com | 2024-03-27To 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!)
Project mention: Guide to Setting Up Evmos CLI for ERC20 to IBC Token Conversion | /r/EVMOS | 2023-11-24Go to Evmos Releases on GitHub.
Read the full release notes here: https://github.com/iotexproject/iotex-core/releases/tag/v1.11.0
Project mention: Layer 1 in Crypto: The Unsung Hero of the Blockchain World | /r/CryptoMoonShots | 2023-07-05
Official Ignite GitHub: https://github.com/ignite/cli
Project mention: How to store large amounts of blockchain data for analysis and low-latency querying? | /r/dataengineering | 2023-06-03search for trueblocks https://github.com/TrueBlocks/trueblocks-core
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 Blockchain related posts
- Building Your Own Blockchain: A Beginner’s Guide to Setting Up and Using Cosmos
- AMD EPYC 7C13 Is a Surprisingly Cheap and Good CPU
- Ethereum Foundation removes their canary
- Images altered to trick machine vision can influence humans too
- Best Crypto To Invest in 2024 [Expert Guide]
- Ignite Tutorials: (Part: 2) Create a Front-End App
- Bitnet is revolutionizing digital finance with its BTSHCE token standard, opening new doors for CBDCs and beyond. Dive into the dynamic future of money today!
-
A note from our sponsor - InfluxDB
www.influxdata.com | 24 Apr 2024
Index
What are some of the best open-source Blockchain projects in Go? This list will help you:
| Project | Stars | |
|---|---|---|
| 1 | go-ethereum | 46,000 |
| 2 | kubo | 15,777 |
| 3 | fabric | 15,368 |
| 4 | go-ibax | 7,883 |
| 5 | lnd | 7,477 |
| 6 | chainlink | 6,581 |
| 7 | cosmos-sdk | 5,914 |
| 8 | tendermint | 5,646 |
| 9 | quorum | 4,584 |
| 10 | blockchain_go | 4,004 |
| 11 | awesome-blockchain | 3,058 |
| 12 | turbo-geth | 2,938 |
| 13 | lotus | 2,767 |
| 14 | bsc | 2,562 |
| 15 | evmos | 1,623 |
| 16 | iotex-core | 1,528 |
| 17 | CovenantSQL | 1,469 |
| 18 | harmony | 1,463 |
| 19 | go | 1,266 |
| 20 | cli | 1,225 |
| 21 | node | 1,078 |
| 22 | IceFireDB | 1,075 |
| 23 | trueblocks-core | 1,021 |
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com