---
# System prepended metadata

title: Ethereum Protocol Fellowship 2nd week update

---

# Ethereum Protocol Fellowship 2nd week update
## Self Introduction
I'm a PhD student in Syracuse University in Blockchain security area, and now working on the Ethereum Mempool Attack Detection. Very excited joining in the fellowship and make some contribution to the Ethereum Portocol.

## Process
I analyse the code in https://github.com/ethereum/go-ethereum/tree/master/core.
And I settle down on the txpool part and concentrate on the mempool workflow. 

After reviewing my labmate's paper on Deter Attacks happening in Mempool, I understand I need to know precisely where should I dig to find all these attacks happening.  So that, I can add some instrumentation in these parts to log the transactions getting into the mempool which may cause the attack.

##### Here is one of the transaction information appearing in the pending pool of Ethereum I got recently:

![](https://i.imgur.com/STZ6pBH.png)


#### Problem I got:
I can't get the exact mempool data in Ethereum to validate the instrumentation I added in the core code of go-ethereum.
The log data set I got for now is not complete.
From github comment, I can get help from someone on Geth team regarding the mempool tx handling.


## Future work
Dive into the code of go-ethereum/core/txpool about the workflow of how the transactions add to the mempool and how the transaction remove from the mempool after they get involved by the miner to the blockchain.

After finding the exact part of how they get into mempool and are chosen by the miner to the blockchain, I can add some conditions to not only keep the original basic admission rules but also can protect the insecure attack not happen in the pool again.




