-
Notifications
You must be signed in to change notification settings - Fork 75
Eth2.0 Implementers Call 1 Agenda #2
Comments
I don't have time to join these meetings but I'll be posting updates via https://twitter.com/DropsOfDiamond. For details of gossipsub implementation see libp2p/rust-libp2p#291. |
Thanks Danny! Here's a couple of things I'd like to talk about:
Looking forward to it :) |
If there's time I'd like to give a quick update on the network simulations I've been doing here: https://github.com/jannikluhn/sharding-netsim |
I will be watching. Cheers |
To clarify, I don't have time to spend unpaid such as in these meetings when I haven't received a grant yet for sharding development (to now deprecated specifications) and gossipsub work. I've tried to clarify with the grants team how much more progress is needed to get a grant, e.g. specific milestones to achieve, but I didn't receive a reply. It seems to me that the Ethereum Foundation may have a preference for funding development of clients that it owns: Geth, Py-EVM, Java, JavaScript, etc. This is based on the lack of funding so far, as well as Vitalik seeming to favour promoting Prysmatic Labs without mentioning the names of other teams. Other devs have contributed such as @ChosunOne, Luke Scoen, and Tim Siwula, but they have understandably dropped out, while many more others may have contributed if funds were available. I have changed careers from renewable energy and left a full time job. I can't fathom why a grant was given to Prysmatic Labs for Geth-sharding back in March, yet no grant has been received yet for any other sharding team. Nor do I know how long a lack of funding will drag out for. Is the Ethereum Foundation trying to manipulate developers? Given that the sharding aspect of the software of a client is a public resource and has no inherent revenue, funding needs to be obtained via alternative means, e.g. grants, donations, employment from the organisation that owns the client, etc. Having an ICO, DAICO, DAII, VC funding, etc. seems to be out of the question since it's a public resource without revenue directly related to sharding development, only indirectly e.g. via the below forms of revenue and driving ecosystem growth (and thus potentially portfolio growth). I have sought grants and donations and even VC funding, and approached Parity and the Web3 Foundation, but people have been non-responsive or at best apologetic. There are ways for clients to generate revenue, e.g. full nodes serving light clients to access data, VIP node, EIP 908, Pocket Network, etc. |
Hey James, I'm unaware of the conversation you have had to date with the grants team, but I'll nudge them to make sure you aren't left in the dark. As for EF grants in general, it is a powerful tool, but one that has taken time to figure out best practices and get fully into motion. EF just released the third wave of grants yesterday which did include some funding for sharding/beacon-chain work to Harmony, and at the same time signaled that the EF is interested in funding "more shasper implementations". The amount of grant funding or praise that a team receives is in direct relation to past work, the caliber of the team, and the needs of the ecosystem. The EF does not play favorites or attempt to "manipulate developers". |
I've invested months into learning, education (e.g. editing the white paper, yellow paper, wiki, etc.), and development of sharding and gossipsub. It's frustrating that I haven't received funding, apart from paying for flights and accommodation to Taipei. I don't want to continue living off my savings for much longer, and will need to get a job if funding isn't obtained, which will reduce the time that I have available for gossipsub/libp2p and shasper development, and is not ideal as it's diluting focus and long-term development. If you want to talk further privately feel free to on Gitter: gitter.im/jamesray1. |
Eth2.0 Implementers Call 1 Agenda
Meeting Date/Time: Thursday 2018/8/16 at 14:00 GMT
Meeting Duration 1.5 hours
YouTube Live Stream Link
Agenda
The text was updated successfully, but these errors were encountered: