Scoping 8304

Since last week's deep-dive into fundamental knowledge, I went on to explore the EIP-8304 spec for Trustless Logs Indexing in depth. And thanks to @RazorClient and a GitHub issue, I was once again working with the most recent data[1] rather than a stale link.

Changing the format a bit to be more succinct and point-oriented.

Areas of research were:

• 4788-style deployment[2]
  • The other similar use case (EIP-7002)[3] that can be used for reference
  • The other fellow we collaborated with, Vansh[4], seems to already have part of it covered
• Existing SSZ implementations[5] — found micro-eth-signer[6], which could be a good reference for the future
• EIP-8304 and Vansh's PoC[7]
• The geth client in dev mode, and exploration of the existing codebase, including the existing 7745 implementation

Clarified in the project proposal:

• One of the other fellows would need to figure out the Kurtosis testnet[8] and the tooling around it
• Testing would be similar to existing 4788-like implementations
• table_root is a potential integration point for parallel tracks

Output:

• For testing, we might not need to run a full sync, as the spec's suggested solution works on an isolated example
• Added to the proposal: the client library for testing would be viem as an experimental feature[9]. I'm quite familiar with the viem and wagmi codebases.
• We'd need to produce documentation for the Pureth docs[10]

Open questions:

• In the spec, the author references an SSZ list[11], which I assume means EIP-7916[12]

Collabs:

If anyone is also planning or would want to participate in a future EIP-8304 implementation project, reach out via Discord and we'll share an early project proposal draft.

Next:

For the next step, I'll continue reading into the dependencies of EIP-8304 and related knowledge to prepare a first public draft of the project proposal, with a proposed timeline and scope.

PRs:

• The first PR for Ethereum specs[13] got merged — there was a useful comment about[14] slotted_freezable.