# EPF6 - Week 9 Updates
## Summary
1. Updated [SSZ-QL full spec](https://hackmd.io/72WkdLi6T2eZX187cGWeqw) based on Jun's prior week update of [postSsz](https://hackmd.io/@junsong/rkAN9lIIxx) + Radek's feedback. Coding is a priority now. We are at week 9 and by week 12 we setup our first [milestone](https://github.com/eth-protocol-fellows/cohort-six/blob/master/projects/ssz-ql-with-merkle-proofs.md#implement-merkle-proof-generation-week-12) (SSZ-Query & GMP should be ready for first integration in week 13).
2. Coding [write-up](https://hackmd.io/Z9No8kSsQvaZt4XUE5bE7w)
3. Add issue to Prysm repo - refine task lists

## Details
### 1. New update to full SSZ-QL spec.
In this task I made a general review of the document, added several improvement in the *Introduction* and *Terminology&Notation* sections, updated the *API Rest* binding section taking into account prior week feedback from mentors and also, updated the given examples.
This *full SSZ-QL spec document is now frozen* in favour of coding v1.

### 2. Coding
This week I've tried to spend more time coding rather than documenting/catching up. I could not achieve the targets proposed in prior week next steps but, I got a better understanding of the project:
- For the hash_tree_root computation:
- For the merkle proofs, I tend to work with the [following struct](https://github.com/ferranbt/fastssz/blob/571a8a27b64b9e64ac9943ddb933040b695b2ba1/tree.go#L21-L26):

// Multiproof represents a merkle proof of several leaves.
type Multiproof struct {
	Indices []int
	Leaves  [][]byte
	Hashes  [][]byte
}

I personally opt for this option as per [CL spec](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md), also mentors' feedback and our own spec where we specify that a single proof is just a special case of merkle multiproofs. With this struct we can handle this properly.

### 3. Prysm repo: Issue + refined task lists
During this week I've created an [issue](https://github.com/OffchainLabs/prysm/issues/15598). Based on the [list](
https://hackmd.io/cOnjTyWIS1WVj0-7tOY1Bw).

### Next steps
- Push my code to Prysm repo and open a PR to track all the changes.