# "Yes, chef!" - ECC Weekly Update for April 19

**URL:** <https://forum.zcashcommunity.com/t/yes-chef-ecc-weekly-update-for-april-19/47477>\
**Category:** General\
**Created:** [April 20, 2024, 1:11am UTC](https://forum.zcashcommunity.com/t/yes-chef-ecc-weekly-update-for-april-19/47477 "2024-04-20T01:11:18Z")\
**Posts on this page:** 1\
**Showing post:** 36

<div class="post-metadata">

**Author:** ![skyl](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/skyl/32/2938_2.png) [@skyl](https://forum.zcashcommunity.com/u/skyl)\
**Post date:** [April 23, 2024, 6:28pm UTC](https://forum.zcashcommunity.com/t/yes-chef-ecc-weekly-update-for-april-19/47477/36 "2024-04-23T18:28:26Z")

</div>

> [@joshs](#):
>
> best bridge the gap between zebrad and zcashd to support a transition

A minimal, compatible RPC interface would be nice.

> [@daira](#):
>
> It’s incredibly frustrating, because the ZF and ECC engineers have never had this problem, and have always worked collaboratively to the best of our abilities within the resource and time constraints we’re under.

As a thought experiment, what would things look like without executives where the executive salaries (and perhaps other corporate overhead) were paid directly to developers? Maybe this could happen closer to the protocol and the devs could get more ZEC? What are the main benefits of the current corporate structures? Do these outweigh the costs? Perhaps the corporate entity structure(s) are needed for X or Y? What are these things?

Could the structures be minimized to send more value to engineers and waste less effort with politics? I’m not sure. I like drinking this koolaid from time to time: [Aftok Founding Principles](https://aftok.com/guide-foundation.html)

What are the biggest barriers to reducing or eliminating the corporate structures that seem to provoke politics and bickering (while spending money that might be better sent to individuals contributing code)?

---

_[View the full topic](https://forum.zcashcommunity.com/t/yes-chef-ecc-weekly-update-for-april-19/47477)._
