Austinhs

package observer

import (
	"context"
	"da/go-server/src/models"
	"da/go-server/src/utils/constants"
	"da/go-server/src/utils/database"
	"database/sql"
	"errors"
	"log"

yorickdowne

Overview

Syncing an Ethereum node is largely reliant on latency and IOPS, I/O Per Second, of the storage. Budget SSDs will struggle to an extent, and some won't be able to sync at all. IOPS can roughly be used as proxy of / predictor for latency. Measuring latency directly is arguably better.

This document aims to snapshot some known good and known bad models.

The drive lists are ordered by interface and then by capacity and alphabetically by vendor name, not by preference. The lists are not exhaustive at all. @mwpastore linked a filterable spreadsheet in comments that has a far greater variety of drives and their characteristics. Filter it by DRAM yes, NAND Type TLC, Form Factor M.2, and desired capacity.

For size, 4TB is a conservative choice which also supports a Fusaka "supernode". The smaller 2TB drive should last an Ethereum full node until at least sometime 2026, with [pre-merge history expiry](http

Cybourgeoisie

/**
 * Render CyberBrokers
 * Using the on-chain Broker renderer
 **/


// Change these variables as you see fit
const WEB3_PROVIDER_URL = "http://0.0.0.0:8545";
const TOKEN_ID = 0;
const SVG_SAVE_FILE_NAME = `${__dirname}/CyberBroker_${TOKEN_ID}.svg`;

BlueyNeilo

#!/bin/bash
yum update -y
curl https://sh.rustup.rs -sSf > RUSTUP.sh
sh RUSTUP.sh -y
rm RUSTUP.sh
yum install gcc -y
echo "Installing for ec2-user.."
cp -r ~/.{cargo,rustup,bash_profile,profile} /home/ec2-user/
echo "ec2-user ready."