Conversation with Merlin [email protected] · Wed Dec 27 2023

You can find a summary of the article on Ethercluster, an open-source alternative to Infura, in the highlighted section.

Skip to main content Get the Reddit app Scan this QR code to download the app now Or check it out in the app stores Go to kubernetes r/kubernetes r/kubernetes Kubernetes discussion, news, support, and link sharing. Members Online yazanator Ethercluster: An Open-Source Alternative to Infura - Ethereum Classic - Medium medium.com Open Archived post. New comments cannot be posted and votes cannot be cast. Locked post. New comments cannot be posted. Top 2% Rank by size Set user flair Anon_but_u_kno_me Select your community flair

reddit.com

Open in app Write Ethercluster: An Open-Source Alternative to Infura Yaz Khoury Follow 6 min read Jul 1, 2019 -- Listen Share More We at the Ethereum Classic Cooperative are happy to unveil Ethercluster , a much-needed project we have been working on for a while. Ethercluster is an open-sourced Ethereum Virtual Machine (EVM) Remote Procedure Call (RPC) providing Ethereum Classic (ETC) and Kotti endpoints for free. It does so using the latest cutting-edge infra-as-code technologies such as Kubernetes , Terraform and Docker . It also scales easily with increased usage and demand. The Ethercluster website provides information and the endpoints, while the docs teach how to build it from scratch so you can run your own infrastructure. Motivations The main motivations behind building our own RPC endpoint infrastructure is due to not having Infura include Ethereum Classic as an option to connect to. That coupled with wait times to actually integrate with Infura, as well as wanting to provide a reliable, scalable and open-sourced alternative to Infura for not only Ethereum Classic but also any EVM-based network was the main reason we pushed to build this. Ethercluster serves both as a free endpoint for Kotti and ETC as well as a design specification for building scalable blockchain infrastructure for others. You can use the endpoint provided by us at the ETC Cooperative or check out our docs to building your blockchain infrastructure. Our documentation will have you learning to build your own node infrastructure in the cloud that can scale easily in no time. Thats right, youd be able to run an Ethereum-based Ethercluster following our docs if you want. Also, you can modify the manifests and specs in the docs to target your specific needs, even ones not related to EVMs ( Hint : You can essentially build your own scalable Proof-of-Stake node infrastructure with ease by building upon Ethercluster). Cloud Instantiation Our Ethercluster design specs first target a few things. We build our cloud set up using Terraform, an infra-as-code software to building your cloud setup in a version-controlled way. The docs go over Terraform and how to get started with it. Essentially, after installing Terraform, you can build your own cloud infrastructure with one command as shown in the following. Terraform: Create Your Cloud Infrastructure With One Command You can check out the GitHub for the Terraform files here . Currently, for this setup, we are using Google Kubernetes Engine on Google Cloud as our sole provider. This design isnt multi-regional yet and neither is it multi-cloud, which will be the aim for a future design that can be truly highly available no matter if there is a blackout in one datacenter or failure from one of the main Cloud Providers (Azure, AWS, GCloud). Furthermore, since we are using GKE for our Kubernetes cluster, it makes things a lot easier for managing after when you have a convenient dashboard to check out and help you debug. In the future, the ideal setup would be not to rely on GKE at all but instead customize the cloud instances to have a more robust cloud cluster. Cluster Design Our current Ethercluster design relies on being in one region and zone, but that can be easily expanded to multi-zone and multi-regional setting. For our Kubernetes architecture, we built the node deployments using StatefulSet because we want our Pods to easily pick up where they left off in resyncing the chain and nodes even when we restart them for updating images or adding more custom features. Using the StatefulSet allows us to preserve the state of our nodes. We also expand it to several replicas, have 4 nodes running as a default per StatefulSet deployment. Currently, the drawback to this design is that all those nodes are being run on the same

medium.com

Home Crypto News Passive Income Reviews Altcoin Projects Blockchain Game Reviews Community Speaks Crypto Education DAPPs Exchanges Technical Analysis Wallet Guides Blockchain Games Game Launches & Updates Gaming Interviews Gaming News NFTs Metaverse DeFi Search Wed, December 27, 2023 About Altcoin Buzz Weekly Newsletter Archive Contact Us Sign in Welcome! Log into your account your username your password Forgot your password? Get help Password recovery Recover your password your email A password will be e-mailed to you. Altcoin Buzz Home Crypto News Cryptocurrency News Controversial Claims Surround MEXC Exchange Practices Cryptocurrency News Etherscans Cross-Chain Portfolio View: Beyond Ethereum Cryptocurrency News The Secret Project Behind NEARs Big Price Increase Cryptocurrency News Uniswap Mobile App: Buy Crypto with MoonPay Debit Card Cryptocurrency News Polygons Milestone: High Inscriptions, Low Gas Fees Passive Income Passive Income TreasureDAO Airdrop Guide: How to Get $1000+ Worth in Free Tokens Passive Income 4 Questions About Staking Luna Classic and Luna Passive Income pStake Finance Brings Liquid Staking to the BNB Chain Passive Income Fantom Liquid Staking With Stader Labs Passive Income How to Get 12.7% APY Using Origin Dollar ($OUSD) Reviews All Altcoin Projects Blockchain Game Reviews Community Speaks Crypto Education DAPPs Exchanges Technical Analysis Wallet Exchanges Ray Youssef: P2P Trading from Paxful to NoOnes Altcoin Projects Top Low Cap DePIN Coins for 2024 Altcoin Projects Top Privacy Coins for the Next Bull Run Part 2 Reviews Top 10 Rules to Spot Next Crypto Gems Part 1 Guides Bitcoin & Crypto Guide Web3 Music Year in Review: Surprising Everyone in 2023 Bitcoin & Crypto Guide Top Avalanche Gems With 10x-100x Potential Bitcoin & Crypto Guide LUKSOs LSP7, LSP8, and LSP17 are Transforming NFTs Bitcoin & Crypto Guide Bitcoin at Christmas: Answering 5 Simple Questions for the Family Bitcoin & Crypto Guide Hot New Binance Labs Crypto Opportunity For 2024 Bull Run Blockchain Games All Game Launches & Updates Gaming Interviews Gaming News Blockchain Games How to Earn Aptos (APT) Tokens Playing This P2E Game Blockchain Games 7 Crypto Gaming Ecosystems to Watch in 2024 Blockchain Games Rekt Game, an Introduction Blockchain Games IQ Protocol Partners With Universus NFTs Metaverse DeFi Home Product Release & Updates Ethereum Classic Unveils Open-Source Substitute To Infura, Ethercluster Product Release & Updates Twitter Telegram

altcoinbuzz.io

provide me a step by step guide explaining how to build Ethercluster using Hyperledger-Besu, Kubernetes K3s, and local bare metal instead of a cloud provider

Building an Ethercluster using Hyperledger-Besu, Kubernetes K3s, and local bare metal can be a complex process, but the following step-by-step guide will help you get started:

Step 1: Set up the environment

1.1. Install Hyperledger Besu on your local bare metal environment. You can follow the official Hyperledger Besu installation guide to perform this step.

1.2. Install Kubernetes K3s on your local bare metal environment. You can follow the official K3s installation guide to perform this step.

Step 2: Configure the configuration files

2.1. Create a new directory for your Ethercluster configuration files.

2.2. Create a new configuration file called config.toml in the directory you created in step 2.1.

2.3. Update the config.toml file with the following configuration details:

[cluster] name = "Ethercluster" description = "My Ethercluster" type = "Kubernetes" [k8s] version = "1.19.3" [besu] version = "21.4.1" [network] credentials = "my-cluster-creds.yaml"

Replace the version values with the appropriate version numbers for Kubernetes and Hyperledger Besu.

Step 3: Create the Kubernetes cluster

3.1. Create a new Kubernetes cluster using K3s by running the following command:

k3s create cluster --name my-cluster

Replace my-cluster with the name of your cluster.

Step 4: Create the Hyperledger Besu configuration file

4.1. Create a new directory for your Hyperledger Besu configuration files.

4.2. Create a new configuration file called besu_config.toml in the directory you created in step 4.1.

4.3. Update the besu_config.toml file with the following configuration details:

[cluster] name = "Ethercluster" description = "My Ethercluster" type = "Kubernetes" [k8s] version = "1.19.3" [besu] version = "21.4.1" [network] credentials = "my-cluster-creds.yaml"

Replace the version values with the appropriate version numbers for Kubernetes and Hyperledger Besu.

Step 5: Deploy the Hyperledger Besu deployment

5.1. Use the following command to deploy the Hyperledger Besu deployment:

kubectl create deploy my-besu-deployment -f besu_config.toml --image besu/besu-node:v21.4.1

Replace my-besu-deployment with the name of your Hyperledger Besu deployment.

Step 6: Deploy the Ethercluster deployment

6.1. Use the following command to deploy the Ethercluster deployment:

kubectl create deploy my-ethercluster-deployment -f config.toml --image ethercluster/ethercluster-node:v1.19.3

Replace my-ethercluster-deployment with the name of your Ethercluster deployment.

Step 7: Expose the Ethercluster port

7.1. Use the following command to expose the Ethercluster port:

kubectl expose deploy my-ethercluster-deployment --port=8546 --type=NodePort

Replace my-ethercluster-deployment with the name of your Ethercluster deployment.

Step 8: Access the Ethercluster cluster

8.1. Use the following command to access the Ethercluster cluster:

kubectl exec -it my-besu-deployment-pod -- /bin/bash

Replace my-besu-deployment-pod with the name of your Hyperledger Besu pod.

8.2. Once you are inside the pod, use the following command to access the Ethercluster node:

besu attach http://my-ethercluster-deployment-node-service:8546

Replace my-ethercluster-deployment-node-service with the name of your Ethercluster node service.

That's it! You have successfully built an Ethercluster using Hyperledger Besu, Kubernetes K3s, and local bare metal.

Getting Started Introduction Core Concepts Build your first Ethercluster API API Access This guide will help you build your own Ethereum Classic API service using Ethercluster. This guide currently features Ethercluster deployment on Google Cloud Platform. Step 01 - Setup Google Cloud # Signup for a Google Cloud account and create a new project . You can conveniently name your project, ethercluster . Setup billing if you're going to pursue making your Ethercluster. Enable Compute Engine API , Cloud Shell API , and Kubernetes Engine API which can be found in the Marketplace . For example: Setup Credentials which will generate a JSON file for you to download. This will be used to easily authenticate into Google Cloud from your local terminal. Step 02 - Install Terraform # Terraform is infra-as-code to allow you to provision your cloud infrastructure in a way that's clear and easy to roll-back and version control. This allows any changes you make to your cloud architecture to be reflected in code and saved, so that any new changes you add can be tracked and debugged. Download, unpack, and install Terraform via release binary for your operating system https://www.terraform.io/downloads.html . Downloading binary on Linux: Copy wget https://releases.hashicorp.com/terraform/0.13.4/terraform_0.13.4_linux_amd64.zip Unpack files: Copy unzip terraform_0.13.4_linux_amd64.zip At this point the executable terraform binary can be run. However, you may want to move it in a more appropriate location and add to your PATH. Copy sudo mv terraform /bin/ or move anywhere else and export to PATH Copy mv terraform / $HOME Copy export PATH = " $PATH :/ $HOME /terraform" Run terraform from a terminal Copy terraform Step 03 - Create a Terraform configuration for GKE # Create directory for your Terraform project and change directory into it: Copy mkdir Ethercloud && cd Ethercloud Initialize a new Terraform project: Copy terraform init Terraform will return the following since there's no existing Terraform config files. Copy Terraform initialized in an empty directory! The directory has no Terraform configuration files. You may begin working with Terraform immediately by creating Terraform configuration files. Now, create a new Terraform configuration file: Copy touch ethercloud.tf Using your preferred editor, we'll have to specify our Ethercluster infrastructure in ethercloud.tf like so: Copy provider "google" { project = "ethercluster" region = "us-central1" zone = "us-central1-c" } resource "google_container_cluster" "primary" { name = "ether-cluster" remove_default_node_pool = true initial_node_count = 1 master_auth { username = "" password = "" } } resource "google_container_node_pool" "primary_preemptible_nodes" { name = "my-node-pool" cluster = "${google_container_cluster.primary.name}" node_count = 3 node_config { preemptible = true machine_type = "n1-standard-1" metadata = { disable-legacy-endpoints = "true" } oauth_scopes = [ "https://www.googleapis.com/auth/logging.write", "https://www.googleapis.com/auth/monitoring", ] } } output "client_certificate" { value = "${google_container_cluster.primary.master_auth.0.client_certificate}" } output "client_key" { value = "${google_container_cluster.primary.master_auth.0.client_key}" } output "cluster_ca_certificate" { value = "${google_container_cluster.primary.master_auth.0.cluster_ca_certificate}" } resource "google_compute_address" "ip_address" { name = "ethercluster-address" } Understandi

etccooperative.github.io

Open in app Write How to create a permissioned blockchain with Hyperledger Besu? Zeeve Follow Published in Zeeve News 8 min read Jun 26 -- Listen Share More In our previous article on Hyperledger Besu, we highlighted the signi ficance of Besu for developers. Today, we will walk through a step-by-step process of how to create a permissioned blockchain with Hyperledger Besu , completed with technical requisites, setup process, and more. Note that these instructions are designed for developers who wish to set up a local environment to experiment with Hyperledger Besu. However, we will also discuss how they can easily configure a production-grade Hyperledger Besu permissioned network at the end of this article. What makes Hyperledger Besu an ideal platform for permissioned blockchains? Hyperledger Besu is like any other Ethereum execution client that manages and updates the blockchain state on the Ethereum networks execution layer. However, Besu stands out for a variety of reasons, including the ability to support both permissioned and public blockchains , as well as its compatibility with popular test networks like Rinkeby, Ropsten, and Gorli. The platform is optimized to implement three prominent consensus algorithms Proof-of-stake , Proof of Authority, and Proof of Work. Also, it offers world-class storage through RocksDB key-value database and implementing Enterprise Ethereum Alliance (EEA) specification to create a common interface across the diverse open-source and closed Ethereums projects. Developers wanting to build decentralized enterprise solutions and private blockchains can use the Besu ecosystem to leverage its unique features and power their product with high scalability, customizability, and security attributes. Get an high-level overview of Besus architecture for private blockchains explained in the given image: One thing to note here is that: A permissioned network on Ethereum doesnt mean we are free of all sorts of common Blockchain vulnerabilities . We still need to be cautious about security threats to protect our systems. Read more on: Most Common Blockchain security Vulnerabilities and how to protect your nodes against them? Tech stack for building a Besu Private network Tech stack and system requirements to create a permissioned blockchain with Hyperledger Besu may vary on a range of factors, such as the size of the network, total transactions submitted on the blockchain, the gas limit for the block, and finally, the complexities of handling JSON-RPC , PubSub, or GraphQ queries by the node. This guide explains the development of a permissioned blockchain with IBFT 2.0, PoA consensus on Besu with local node and account permissions. Following are the tech stack you require: Windows OS Binaries Docker. Java virtual machine with 4GB memory. VM with 6GB memory size and a virtual hard disk with a minimum 10GB space. Developer tools and IDEs Local SSD storage. Interested in deploying Public networks with Besu? Read: How to deploy an Ethereum node using Hyperledger Besu for Public Networks? Creating a permissioned blockchain with Hyperledger Besu: 12 Steps to follow Step1: Installing Besu Install Besu using Developer Quickstart . Also, you need to install Docker image and Binaries to get more stable versions of Besu. Either way, you can install Hyperledger Besu from source code with the instructions given here . Step2: Downloading Curl Use this link to download Curl, which mostly offers the source package required in Besu network development. Now, lets create the blockchain. Our network infrastructure on Besu will basically include four nodes. You can add/reduce the nodes corresponding to the requirement. Step3: Creating folders Each node that upholds the Besu network will require a directo

medium.com

Open in app Write How to deploy a Hyperledger Besu network on Kubernetes? Zeeve Follow Published in Zeeve News 9 min read Jul 9 -- Listen Share More Hyperledger is gaining popularity, with prominent companies like LACChain, Poste Italiane, and Public Mint building innovative enterprise solutions on the top of its ecosystem. Knowing this, our previous articles on Hyperledger Besu have covered a dedicated developers guide , node deployment on Besu, and Ethereum node deployment on Besu . Adding more to the series, lets discuss how to deploy a Hyperledger Besu network on Kubernetes. Over the past few years, Kubernetes is becoming the choice of most web3 developers and is highly recommended for Hyperledger-specific component deployment. Hence, lets get started! Why Kubernetes for Besu Network deployment? Kubernetes is perfect for Hyperperledger Besu deployment as it has awesome capabilities to manage, scale, and Orchestrate distributed networks. Kubernetes clusters offer a range of benefits over traditional and virtualized deployment (as explained in the below image), such as managing containerized services and workloads, declaratory configuration, and automation. For a production environment, containerized systems run the applications seamlessly and ensure no downtime. For example, if one container is in downtime, another container starts immediately and handles the network. Thats the reason why Kubernetes is gaining overwhelming popularity across the developer community. Looking for other deployment methods than Kubernetes? Check this out: How to create a permissioned blockchain with Hyperledger Besu? Deploying a Hyperledger Besu network on Kubernetes: 9 Simple steps Following is a step-by-step process to deploy a Hyperledger Besu network on Kubernetes. However, these are the instructions for private Besu network setup; you can deploy a public network by referring to Besus official documentation . Prerequisites Create a local or cloud Kubernetes cluster. Clone the Quorum-Kubernetes repository . Install kubectl in your local machine to run commands against the Kubernetes Clusters. Install Helm3 to manage Kubernetes packages, widely known as charts. Ensure if you are able to connect to the cluster through kubectl Upon successfully setting up a running cluster, you must verify that kubectl is connected to the cluster like below: kubectl version Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.1", GitCommit:"86ec240af8cbd1b60bcc4c03c20da9b98005b92e", GitTreeState:"clean", BuildDate:"2021-12-16T11:41:01Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:35:25Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"} Change directory to helm as we will use Helm charts in our deployment process: cd helm Creating the namespace Use the following command to create the namespace. kubectl create namespace besu As you can see, we have picked besu as the namespace, but you can choose any name during deployment. Creating the genesis file with genesis chart The genesis chart in the Besu deployment creates the genesis file and necessary keys for the validators. Genesis file is a very important JSON file that defines all the instances related to your private network. For example, token allocation, network behavior, total validators allowed, member nodes, RPC nodes, and bootnodes count, default network parameters, and other essential information. To implement all these networkwide settings, ensure that all the nodes in your network must use one genesis file. Create a JSON genesis file and then specify the genesis file by

medium.com