yorickdowne

Overview

Syncing an Ethereum node is largely reliant on IOPS, I/O Per Second. Budget SSDs will struggle to an extent, and some won't be able to sync at all.

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

For size, 4TB or 2TB come recommended as of mid 2024. A 2TB drive should last an Ethereum full node until late 2025 or thereabouts, with crystal ball uncertainty.

High-level, QLC and DRAMless are far slower than "mainstream" SSDs. QLC has lower endurance as well. Any savings will be gone when the drive fails early and needs to be replaced.

jpitts

Ethereum Protocol - Series 0.x

Version and Code Name	Block No.	Released	Incl EIPs	Specs	Impls
v1 - Frontier	1	07/30/2015			Geth v1.0.0
v1.1 - Frontier Thawing	200000	09/07/2015			Geth v1.0.1.1
v2 - Homestead	1150000	03/14/2016	EIP-2 EIP-7 EIP-8	HFM-606	Geth v1.3.4
v3-rc1 - DAO Wars	aborted	aborted			Geth v1.4.8
v3 - DAO Fork	1920000	07/20/2016		HFM-779	[Geth v1.4.10](https://github.com/ethere

chpatrick

#!/usr/bin/env python3

# let's say you have a C++ project in Nix that you want to work on with CLion so that the Nix dependencies are available
# put this script in your project directory
# then, in Settings -> Build, Execution, Deployment -> Toolchains set CMake to this script
# if you need any extra nix-shell arguments, add them to the invocation at the bottom

import os
import sys
import shlex

axic

ewasm “WRC20” token contract coding challenge

This document describes a simple contract in pseudocode and gives a couple of test cases for it.

The challenge is designed to be fairly easy to implement in a language of choice, compiled to wasm and interacted with. It is loosely based on the ERC20 token standard, named "WRC20", where the W stands for WebAssembly.

External interface

The contract has two features:

noamnelke

1. Converts the recipient's public key to PKCS8

ssh-keygen -f id_rsa.pub -e -m PKCS8 > id_rsa.pkcs8.pubkey

One way to obtain a recipient's public key is from GitHub, by adding .keys to their profile url, e.g. https://github.com/noamnelke.keys

2. Encrypt a string

This pipes a secret string into openssl, encrypts it with the recipient's public key and pipes the result to openssl again to transcode it into base64 (without the last step it would be binary, which is fine for a file, but harder to paste somewhere).

hugo-dc

• call_OOG_additionalGasCosts1
• callcall_00_OOGE_valueTransfer
• callcallcall_ABCB_RECURSIVE
• callcallcallcode_ABCB_RECURSIVE
• callcallcodecall_ABCB_RECURSIVE
• callcallcodecallcode_ABCB_RECURSIVE
• callcodeDynamicCode
• callcodeDynamicCode2SelfCall
• callcodeInInitcodeToEmptyContract
• [callcodeInInitcodeToExisContractWithVTransferNEMoney](https://gist.github.com/hu

hugo-dc

Transaction Gas:

libethcore/Transactionbase.cpp

In function baseGasRequired, print the initial g, it can be 'transaction cost' or 'create cost', and print g again before it gets returned, now it will contain the cost for the sent in the transaction.

https://github.com/ethereum/cpp-ethereum/blob/c7528cdcd417e50a01909c8b621ad12c7d491856/libethcore/TransactionBase.cpp#L202

libethereum/Executive.cpp

jwasinger

{
  "sealEngine": "Ethash",
  "params": {
    "accountStartNonce": "0x00",
    "maximumExtraDataSize": "0x20",
    "homesteadForkBlock": "0x00",
    "EIP150ForkBlock": "0x00",
    "EIP158ForkBlock": "0x00",
    "byzantiumForkBlock": "0x00",
    "minGasLimit": "0x5208",

axic

eWASM Roadmap 2017-2018

UPDATE: for a clearer and up to date picture please refer to https://github.com/ewasm and https://gitter.im/ewasm/lobby

(Intro: https://github.com/ewasm)

The goal is to launch a preliminary test environment ("test net") with eWASM very early 2018 and to have a stable eWASM test ecosystem by mid-2018.

Timeline:

klaaspieter

From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:

There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.

That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.