EPF4: UPDATE 8 'STARTING AND RESTARTING LODESTAR' 1. How is Lodestar started ? Lodestar is started using the beaconHandler. The explicit command responsible for this can be found here: . The most important function responsible for this implementation in that file can be found here:

EPF4: UPDATE 7 This is a direct follow-up to UPDATE 6, which is basically me reviewing the experimental code i have written prior for implementing ephemery reset using Lodestar. The most important takeaway is that i will be creating three major code files within the reset directory in lodestar's ephemery package: checkTestnet.ts resetTestnet.ts index.ts

EPF4: UPDATE 5 Neccessary Wanderings: After playing with geth for the past few weeks, lodestar has been a curveball in terms of the way its implemented First, lodestar is built binarily so the initial issues i had with running geth wherever in the terminal came up again In Lodestar's case, old tricks don't seem to work. I cant really solve it (yet?) because its built binarily, with all the files in place in its own directory. It's really quite different from geth, reth or any other clients i have installed on my local machine, which has everything abstracted into one executable file. I finally figured out how to make it work, thanks to Hol's prior experimentation here. Also later found a bounty of resources about Lodestar on HackMD, i will be linking some in the links subsection below.

EPF4: UPDATE 2 I finally got into active development this week, getting into Ephemery, nodes and clients. I wrote a little blog on my experience with running a node for the first time.. I also started studying the code behind the two repos on Ephemery, genesis & scipts I'm likely going to spend a lot of time studying and understanding because like i said in my notes, this all new to me. I also think the fact am working permissionessly reduces the pressure :)

EPF4: UPDATE 6 Got very busy with my other project this week, but i was able to dig into ephemery native retention scripts and understand how ephemery reset works manually and rewrote it in typescript. Typescript is the language of choice for Lodestar. I have written the purpose of this experimental code here, so i will just jump into my own impression of how to modify it within Lodestar here: import * as fs from 'fs'; import * as path from 'path'; import * as util from 'util'; import { exec } from 'child_process'; import axios from 'axios';

EPF4: PROJECT PROPOSAL Implementing Ephemery's Reset Mechanism Automatic reset implementation of the Ephemery testnet for client setups, starting with lodestar, then geth.. Motivation The goerli supply mess has made test tokens hard to come by. It is hamstringing validator and developers efforts to use the testnet adequately. It has also festered a growing tendency to hoard test tokens, creating token scarcity and price increase on an otherwise free token. Ephemery testnet is a unique solution aiming at solving these problems. It's being built based on the principle that testnets can be ephemeral, and if testnet are ephemeral, tokens are abundant and transient, and under these conditions it will never be hoarded because "it makes no sense to keep that which will be taken away after each reset". Ephemeral testnets have a short life-span, and create a new genesis state after each reset, effectively discarding every transaction that occured prior to it.

EPF4: UPDATE 3 This week i continue off from where i stopped last week, combing through: ephemery/genesis and ephemery/scripts. I also started looking at the EIP Draft, the specifications especially have helped put the genesis and scripts repo into context, i now understand better what is happening under the hood. I was able to finish scouring the genesis repo this week, and i have started writing my own version of the specifications because it's helping me understand it better. Also fell in love with reading the console logs line-by-line and asking GPT what it means, time-consuming but kinda fulfiling lol :)

EPF4: UPDATE 4 This week i got massively sidetracked by another project and my own emotions. I was able to finish scouring the genesis/scripts and writing my version of the specifications. I hope to be back fully next-week tuesday, when i will be done with my project.

EPF4: UPDATE 1 This week i got sucked into graphic drivers related issues on my laptop and didn't have much time to do research work. I did find this interesting rabbit hole related to timing games & transaction fees: Links Late block proposal problem Time in ethereum Timing games in POS

EPF 4: WEEK 0 Retoractive updates (from week 0 - week 4) because i am a bad boy and i have not been doing my job correctly. May the grand-wizards of the fellowship look upon my request from here on favourably :) In the very first week of the fellowship, circa July 14. I found the following projects interesting to contribute to: Staker Testnet Cryptoeconomic Models Staker testnet because i can immediately sense that this will give me a grounded understanding of how ethereum works especially on the client side.

Hii, this is my first post here and I will be using this medium to curate my journey through the ethereum protocol fellowship. My initial notes are actually here; there, you will find me going in on Ephemery, i also mention RIG's cryptoeconomic problems as well. The focus of today's post, will be on the the bugs i encountered while trying to reproduce the week2's Office hour tutorial organized by Mario on running a node and clients. The first 50mins of the presentation was actually smooth sailing for me, until we got to the part about running public networks like Ephemery. In retrospect all the bugs where directory related, and here they are: