update Geth to execution client #343
Conversation
There was a problem hiding this comment.
Though you are right about the fact that one should try and address architectural commonalities between clients, the pools themselves might not be well specified across clients . What has to be investigated first is if all the execution clients are employing the legacy pool as defined here or are there differences... if there are, they should be highlighted here
|
Yes, you're right. However, the transaction pool here should be an abstract concept. Even if it has different names in different client implementations, it should exist architecturally, just like the explanation of STF in the above text. |
|
+1 I agree we should just use execution client and general term here. Maybe just add a clarification later that different clients implementation details differ and this is example of geth? |
Using Geth here is no longer appropriate. It should refer to all execution clients