# Harmony survey followup The following are some followup questions related to your initial answers to interop survey. Please add answers inline to the document. * (2.1) What's the update on the status of JVM libp2p? * (3.1) Are you using `beacon_blocks` method for syncing yet? If not, coordinated start should generally work for initial experiments * (3.3) Can you bootstrap syncing with a copy of sync data? * (5.1) Are you gossiping unaggregated attestations upon creation? Are you aggregating locally for block production? What's the status of your WIP attestation pool? * (8.1) Do you still _not_ verify proposer signature before relaying a block? * (15) Have you added any chainstart methods? Specifically, can you perform a "kickstart" from `(genesis_time, validator_count)` or can you start from a prepared SSZ genesis state? * Anything else you want to share or discuss before next week? ## answers - (2.1) Anton has finished libp2p API and started to integrate it into the client. It will take a time but we hope that it will be done this week. - (3.1) We're able to sync by requesting historic data via RPC requests identical to the spec but over a custom transport protocol. Moving to spec'd RPC is a part of (2.1) libp2p integration. - (3.3) There is a work in progress on that. Should be done it two days. - (5.1) The pool is 70% ready. I am going to release it this week either. Gossiping attestations is a part of libp2p integration as well. We're aggregating locally for block production. - (8.1) Yes, we're not. - (15) We are able to kickstart from (genesis_time, validator_count). Also, we'll be able to start from prepared genesis in yaml/ssz format, this is gonna be done as a part of (3.3) work. - Hopefully, we will have a discovery v5 client working this week. We don't have a detailed guide on how to use our client for interop. But I don't think it's necessary since one of us will be on site.