Try   HackMD

Introduction

First of all - very excited to take part in this cohort. Goal is to learn as much as I can by working on a good advance project and build my way up.

Exploring projects

The first step is to try find the project which I want to work on. So I went through the given project ideas and there were particulary 2 ideas that caught my interest -

  • Ephemery Testnet - By Mario Havel
  • ERC-4337 tooling support - By Yoav Weiss

I went ahead with the Ephemery testnet idea because it was something new to me and more cool.

ERC-4337 tooling support didnt seem that difficult to solve and big to work for months and I have seen some supports already built out so not that new. But its still a very good option!

Readings

Below are the readings I went through to get myself setup with the theory of Ephemery testnet.

Honestly some things while reading them did go over my head but its part of the process. I'll give it another go this week.

What makes me motivated to work on this is the concept and problem statement that Ephemery testnet solves -

This kind of testnet can provide an alternative environment for short-term testing of applications, validators and also breaking changes in client implementations. It avoids issues of long running testnets which suffer from state bloat, lack of testnet funds or consensus issues. Periodically resetting the network back to genesis cleans the validator set, returns funds back to faucets while keeping the network reasonably small for easy bootstraping.

Goal for this Week

Thanks to Mario for helping me onboard and suggesting some resources/methods to set up - goal is to work on them

Run a validator and make myself upto mark with all the theory

Bonus - See client implementation and work on them (pk910).

End

Thank you for reading this. Please comment any good reading resource you have related to above.

Last changed by 
 
Naman Garg
0
146

Read more

Bullshark

BullShark is a protocol that achieves Byzantine Atomic Broadcast (BAB) in a distributed system using a DAG. It lies in the DAG-Rider paradigm, optimized for the common synchronous case, and entails several main enhancements to ensure practical deployability. The core idea is to use the DAG to order transactions in a distributed Byzantine setting, and it gives a sound solution toward distributed consensus for deploying blockchain technologies. BullShark runs on a peer-to-peer message-passing model, where each message is a vertex in the DAG. The key primitive assumes a computationally bounded adversary who is allowed to corrupt at most a third of the parties. The notion of reliable link between honest parties means that all messages eventually arrive, which is what supports the operation of the protocol both in synchronous and asynchronous periods. The work adopts a GST model to be able to reason about synchronous network conditions. BullShark Core: DAG Constructions The protocol has a DAG construction at its core. Each party posts transaction proposals through messages into a DAG. In the DAG, vertices represent messages, and edges represent causal relationships. The parties make a new vertex through combining blocks of transactions and with references to messages which it has previously received. These references are either strong, hence link to vertices in the previous round, or weak, hence link to vertices in rounds which are earlier to ensure their eventual inclusion in the total order. BullShark relies on reliable broadcast mechanisms to give firm guarantees of message integrity, agreement, and validity among parties with the fact that all honest parties will eventually receive the same messages and have a consistent view of the DAG. The protocol further makes use of a global perfect coin for leader election and is charged with leaders who possess fairness and unpredictability in terms of leadership selections for message proposals. Advancing rounds in BullShark The protocol is built itself around certain conditions that drive the process of advancement. By feeding a round with enough vertices, specifically 2 f + 1, parties ensure advancement into the next. Advancing is guaranteed even when messages in the middle of the process of reaching another party are delayed. During synchronous periods, BullShark introduces timeouts to bound the round advancement protocol, and this dual approach gives the best of both worlds: very low latency and high throughput yet with liveness guarantee under worst-case asynchronous conditions

May 26, 2024
Mining Pool

https://github.com/kingstone888/hypepool

Apr 19, 2024
Consensus

https://www.paradigm.xyz/2022/07/consensus-throughput

Mar 18, 2024
Solo Home Staking

Finally my long left dream was to

Feb 21, 2024
Read more from Naman Garg
Published on HackMD