Notes:

• Could be better for the EWASM implementation as Linear Storage is part of that spec. Increasing operability with existing libraries. Example using a Red-Black Tree implementation compiled from another language using linear storage.
• Most developers already think in Arrays over Maps. Unnecessary internal complexity arises from implementations where Devs use an array because traditionally arrays are simpler where currently the inverse is true.

Here are the ones I know about. Please add others that are missing:

• Meeting 7 (#8): https://www.youtube.com/watch?v=Va2fdfH5lic
• Meeting 6 (#6): https://youtu.be/TcWY8vmdh-k
• Meeting 5 (#4): https://youtu.be/tBnDcnAbdYo
• Meeting 4 (#3): https://soundcloud.com/lane-rettig-154644600/ethereum-cat-herders-meeting-4, https://youtu.be/1idlBHNGzqA
• Meeting 3 (Jan. 22 - no agenda?): https://youtu.be/e1_MadD8tAU

Brought up by Alexey -- if we're going to have Working Groups -- we need to fund them, and we need to gather people who can work on it.

Copy pasted it from Gitter/ Eth-magicians

Steps to be done if we want to see ProgPoW live with Istanbul hardfork

(1) get money into the audit bounties.
(2) Then the audit needs to come back with corroborating results
(3) then it gets added to the next hard fork (Istanbul if it happens soon enough)
(4) then the hardfork happens.

The bounty that has to be funded for ProgPoW audit:
https://gitcoin.co/grants/82/official-progpow-technical-audit-funding
we need to fundraise $50k for Least Authority audit

Additional information:
ethereum/EIPs#1804
https://eips.ethereum.org/EIPS/eip-1679
https://en.ethereum.wiki/roadmap/Istanbul
https://www.reddit.com/r/ethereum/comments/b49c26/clarification_on_the_acceptance_of_progpow_into_a/
https://medium.com/ethereum-cat-herders/progpow-audit-goals-expectations-75bb902a1f01

@timbeiko you were the one discussing this with me so I’m tagging you again ;)

I would suggest this get done in North America.

Do we need one before the October hardfork? What timelines should it sync up with?

Proposed this as a meeting topic for meeting 8 (#16)

There is a possibility that looking at the difference between the previous state can be used to reduce state size. There is also a possible there is an optimal n-states to consider. This can be discovered through testing.

Q1 to Alexey: is his prototype using hexary trees or binary?

Q2 there's two levels of "non-naiveness": the first level is that if two merkle branches share the same node you merge the node, the second level is that if you get all children of a node you don't need to include the parent of the node
I'm guessing it's just the first level that gives the 3x improvement, correct?
If it's hexary, I suspect the second level would give a tiny gain

For @AlexeyAkhunov to answer.

Danno @shemnon wrote up a suggested cadence of hard forks in the EthMagicians thread https://ethereum-magicians.org/t/more-frequent-smaller-hardforks-vs-less-frequent-larger-ones/2929/28?u=boris

It showcases 4 months vs 6 months.

Danno, can you add this to agenda for an upcoming Core Devs Call and be a point of contact for this?

A few clients are starting to use these yet there doesn't exist a format that would allow interoperability between clients.

If you’re interested leave a comment and we’ll message where the comms channels are.

@AlexeyAkhunov

An anonymous community member has offered a bounty on this task (see Gitcoin bounty info, below). Here are the requirements:

1. Buy a domain name such as "Progpowcarbonvote.com"
2. Set up a carbon vote (https://github.com/EthFans/carbonvote) on the domain with the question, "Should Ethereum change the proof of work algorithm to ProgPoW?" The only possible answers should be "yes" or "no".

Task should be completed by 23:59pm tomorrow (Feb. 9) Pacific Time.

Call details in ethereum/pm#82. Please reference ethereum/pm#69 for more detailed instructions.

Date and Time

Proposed time is 14:00 UTC on Tuesday, March 26th, 2019.

Location

Zoom: The link will be posted in the Gitter channel and sent to attendees.
YouTube Livestream Link: https://www.youtube.com/watch?v=xLR5V0DGZxE

Agenda

1. Update on ProgPow Audit

   • Hudson to give update
   • Subcommittee update
   • When are we shutting down progpowcarbonvote.com? Need to announce that now

2. Hard Fork Coordination Update

3. Process Management

   • #13
   • https://github.com/ethereum-cat-herders/PM/blob/5ed9af00d79e31a330203d7e0186f16a8ac9725f/ECHTaskList.md

4. Moloch DAO & Aragon Review

5. Updates on the action items from Constantinople post-mortem

6. Update on the Ethereum Development Portal designs/structure

7. Community Outreach

8. Replacing Afri as multisig keyholder

9. Eth2 coordination help

10. Ethereum.org website update

11. Communicating about all core devs

12. Any Other Business

13. Review of Actions from Meeting 7

    • ACTION 6.3: ProgPoW subcommitte to review feedback from stakeholders to see if anything should be included in technical audit.
    • ACTION 6.4: Joseph to post the updated communications checklist to the ECH internal gitter channel.
    • ACTION 6.7: Hugo & Joseph to work together to write up a general overview of how Moloch DAO might benefit the Ethereum Community.
    • ACTION 7.1: Identify if the new Gitcoin grant was for the Whiteblock audit
    • ACTION 7.2: Tim Beiko: Add comment to the All Core Devs Agenda regarding tentatively adding the ProgPoW EIP into Instanbul pending audit. Lane to assist with making it an agenda item.
    • ACTION 7.3: Hudson to provide feedback on Hard Fork Coordinator/s.
    • ACTION 7.4: Pooja to manage. Cat Herders to review Pooja's initial master document to manage process flow and start to build this process - here.
    • ACTION 7.5: Cat Herders to look the Handbook proposed by Luke Schoen and discuss over the next couple weeks - here.

14. Next Meeting

Date and Time

Proposed time is 14:00 GMT on Tuesday, February 19th, 2019.

Location

Zoom. The link will be posted in the Gitter channel and sent to attendees.

Agenda

1. Update on ProgPow Audit
   1.1 Hudson feedback from meeting (ACTION 1)
   1.2 Subcommittee update
   1.3 Update on Carbon Vote (ACTION 2)
2. Constantinople Go Live
3. Updates on the action items from Constantinople Post mortem (ACTION 6)
4. Community Outreach
   4.1 Post Eth Cat Herders Blog Post (ACTION 5)
   4.2 Pooja's post - feedback (ACTION 3 & 4)
5. Update on the Ethereum Development Portal designs/structure
6. Any Other Business

Action items from Meeting #5

ACTION 1: Hudson to provide update on discussion and further action required from the ProgPoW subcommittee.
ACTION 2: Lane to launch the Carbon vote for ProgPoW.
ACTION 3: Pooja to launch her community post in reddit and medium.
ACTION 4: Pooja to provide Lane with Medium handle to be added to Ethereum Cat Herders Medium.
ACTION 5: Brett to launch "Further Introduction: The Ethereum Cat Herders" post in medium once confirmation is given by Lane and Hudson.
ACTION 6: Pooja to work with Charles on the Constantinople Post Mortem action items.
ACTION 7: Lane will work on combining it the various repositories under PM.
ACTION 8: Hudson add Afri to managers to Ethereum Cat Herders Github.
ACTION 9: Hudson will merge Pooja's work in Github.

Possibly extending from Vitaliks proposal.

Capture action items of RPC changes needed, client changes, and identifying hard forks

Tie into larger testing initiatives

Date and Time

Proposed: 1400 GMT on Tuesday 5 February

Location

Zoom. Links will be sent to attendees.

Agenda

Please add comments below if you would like to propose items to be added to the agenda

• Update on Actions from Meeting #3 (see below)
• ProgPOW Audit - Requirements / Plan / Roadmap
• Ethereum Developer Portal
• Finalize website (by date)
• Early findings in Aragon DAO research (CH, CSt.L)
• Handbook or Guidelines for the community
• Any Other Business
• Review Actions from Meeting #4

Roles

• Moderator: Charles St. Louis
• Notes / Actions: Brett Robertson
• Recorder: Zoom

Notes will be published in the comments after they have been finalised.

Action items from Meeting #3 (written up by @Souptacular):

• Create post-mortem Constantinople delay blog on our Medium and a permanent Github location for post-mortems.
• Finish website (it looks amazing!).
  • Hugo is creating a Google Doc to collect needed links for the site.
  • Please send a square photo of either yourself or whatever picture you want to use to represent yourself + your name or screenname to hugo. It will be put on the cat herders website.
• Create cat herders introduction blog post.
• Secure Twitter handle
• Clean up document that has all of the links to exchanges/miners and add a sheet with blank data as a template for next time (not urgent).
• Afri has a subcommitee on hard fork planning and EIPs people can participate in.
• Create an agenda either via Github issues in one of our repos (maybe in a private repo where we coordinate internal stuff?).

@tintinweb presented on adding Security Considerations to EIPs by default

Will make a PR against EIP-1

Date and Time

Proposed time is 14:00 UTC on Tuesday, April 30th, 2019.

Location

Zoom: The link has been sent to attendees.
YouTube Livestream Link: TBA

Agenda

1. Update on ProgPow Audit
2. Hard Fork Coordination Update
3. Moloch DAO & Aragon Review
4. Updates on the action items from Constantinople post-mortem
5. Update on the Ethereum Development Portal designs/structure
6. Website Design
7. Discussion on Fund allocation
8. ECH Zoom Pro Account
9. Any Other Business
10. Review of outstanding action items from Meeting 10

• ACTION 6.4: Joseph to post the updated communications checklist to the ECH internal gitter channel.
• ACTION 7.3: Hudson to provide feedback on Hard Fork Coordinator/s.
• ACTION 7.5: Cat Herders to look the Handbook proposed by Luke Schoen and review/discuss - here.
• ACTION 9.1: Hudson to work with Charles on making a post about ProgPoW audit.
• ACTION 9.4: Multisig keyolders to work on seperating the funds.
• ACTION 10.1: Hardfork Coordinators call to be setup post Berlin meetup, current proposed date 2pm, 24 April 2019.
• ACTION 10.2: Invite all Cat Herders to participate in the Website call or to provide ideas via the gitter channel.

1. Next Meeting

Take it down in two weeks, as decided on yesterday's call.

Date and Time

Proposed time is 14:00 UTC on Tuesday, April 16th, 2019.

Location

Zoom: The link has been sent to attendees.
YouTube Livestream Link: TBA

Agenda

1. Update on ProgPow Audit
2. Hard Fork Coordination Update
3. Moloch DAO & Aragon Review
4. Updates on the action items from Constantinople post-mortem
5. Update on the Ethereum Development Portal designs/structure
6. Any Other Business
7. Review of outstanding action items from Meeting 9

• ACTION 6.4: Joseph to post the updated communications checklist to the ECH internal gitter channel.
• ACTION 6.7: Hugo & Joseph to work together to write up a general overview of how Moloch DAO might benefit the Ethereum Community.
• ACTION 7.3: Hudson to provide feedback on Hard Fork Coordinator/s.
• ACTION 7.5: Cat Herders to look the Handbook proposed by Luke Schoen and discuss over the next couple weeks - here.
• ACTION 8.6: Pooja to engage with Charles and Hugo regarding the website.
• ACTION 9.1: Hudson to work with Charles on making a post about ProgPoW audit.
• ACTION 9.2: Pooja to create a draft for process for the hardforks and submit as a pull request.
• ACTION 9.3: Hugo is set to work on website
• ACTION 9.4: Multisig keyolders to work on seperating the funds.
• ACTION 9.5: Multisig keyolders to bump the authorisation of multisig to 2-of-3.

1. Next Meeting

@DBrettRobertson said that he would see about granting me access to this repo.

Please let me know if this is possible and/or who has control over this repo and can get it done.

On Twitter / Reddit, @Souptacular announced that only a few people know how to livestream.

It would be good to document this and give other people permission.

See https://en.ethereum.wiki/infrastructure#all-core-dev-calls for a start and some questions

Call details in ethereum/pm#83. Please reference ethereum/pm#69 for more detailed instructions.

Date and Time

Proposed time is 14:00 UTC on Wednesday, April 24th, 2019.
Meeting duration: 1 hr

Location

Zoom: The link will be shared soon.

Agenda

1. Berlin meetup update.
2. Discuss ECH issues (Istanbul / upgrade process specific), volunteer for tracking and closing?
3. Status on EIP proposed.
4. EIP approval process. Who are the decision makers?
5. Improvements to Hardfork Meta process #1852.
6. EIP 1929(ECH proposal for HF coordination).

Next meeting

Date and Time

Proposed time is 14:00 UTC on Tuesday, March 12th, 2019.

Location

Zoom. The link will be posted in the Gitter channel and sent to attendees.
YouTube Link

Agenda

1. Constantinople Go Live1.
2. Update on ProgPow Audit
   2.1 Hudson to give update
   2.2 Subcommittee update
3. Hard Fork Coordination
4. Updates on the action items from Constantinople Post mortem
5. Moloch DAO & Aragon Discussion
6. Community Outreach
7. Update on the Ethereum Development Portal designs/structure
8. Any Other Business
   8.1 Issue 12: Process flow of Cat Herders
   8.2 Handbook or Guidelines for the community
   8.3 Ethereum Website
9. Review of Actions from Meeting #6

Action items from Meeting #6

ACTION 1: Hudson to coordinate setting up of Bounties and Gitcoin funding for ProgPoW audit.
ACTION 2: William and Hudson to engage with Least Authority via call.
ACTION 3: ProgPoW subcommitte to review feedback from stakeholders to see if anything should be included in technical audit.
ACTION 4: Joseph to post the updated checklist to the ECH internal gitter channel.
ACTION 5: Hudson to review Ethereum Cat Herders draft before Brett posts to Medium.
ACTION 6: Chris to continue to work on Aragon DAO for ECH to manage funding.
ACTION 7: Hugo & Joseph to work together to write up a general overview of how Moloch DAO might benefit the Ethereum Community.
ACTION 8: Pooja to set up a Telegram group for the Constantinople Delay ACTION ITEMS subcommittee.

10. Next Meeting

Do we know who is in charge with that forum? It looks abandoned and also there are questionable ads of miners chassis right in the forum header.

@bmann said on ECH gitter that it's probably should be taken down.

The footer of https://blog.ethereum.org has a LinkedIn icon that links to https://linkedin.com/in/ethereum -- this is a person, not an

I couldn't find the source of this blog, otherwise I would have made a pull request to help fix it.

If we're going to link to LinkedIn at all, people probably meant to link to https://www.linkedin.com/company/ethereum/ -- which should be labelled as Ethereum Foundation.

Date and Time

Proposed time is 14:00 UTC on Tuesday, April 2nd, 2019.

Location

Zoom: The link will be posted in the Gitter channel and sent to attendees.
YouTube Livestream Link: TBA

Agenda

1. Update on ProgPow Audit
2. Hard Fork Coordination Update
3. Moloch DAO & Aragon Review
4. Updates on the action items from Constantinople post-mortem
5. Update on the Ethereum Development Portal designs/structure
6. Eth2 coordination help
7. Any Other Business
8. Review of Actions from Meeting 8

• ACTION 6.4: Joseph to post the updated communications checklist to the ECH internal gitter channel.
• ACTION 6.7: Hugo & Joseph to work together to write up a general overview of how Moloch DAO might benefit the Ethereum Community.
• ACTION 7.3: Hudson to provide feedback on Hard Fork Coordinator/s.
• ACTION 7.5: Cat Herders to look the Handbook proposed by Luke Schoen and discuss over the next couple weeks - here.
• ACTION 8.1: Need to give warning to community that the ProgPoW carbonvote is shutting down. Two week warning - 9 April 2019 (block/time to be confirmed)
• ACTION 8.2: Pooja to present EIP tracker idea to Core Devs on Friday call.
• ACTION 8.3: Review Pooja's ECH task list and merge it.
• ACTION 8.4: Lane to add Charles to multisig.
• ACTION 8.5: Mikerah to bring the idea of getting the Ethereum Cat Herders to assist coordinating tasks to establish a multiclient Beacon Chain testnet at the Ethereum 2.0 call and will provide feedback at the next meeting.
• ACTION 8.6: Pooja to engage with Charles and Hugo regarding the website.
• ACTION 8.7: Brett to setup gitter channel for those interested in managing the notes and summaries of the Ethereum Core Devs.

1. Next Meeting

As discussed on today's call, the multisig now contains > $14k USD as a result of the progpow grant. Let's bump it up to a 2-of-3, and if possible, move the progpow funds to a separate multisig for accounting and accountability purposes.

In Gitter:

@lrettig We are all drowning in too many channels and too much communication. I really cannot keep up with all of the dialog in this channel (or most other channels, for that matter)

I personally think that everyone is in agreement on this and would love to work to help improve things. The community just needs some direction. Just having meetings isn't enough. There needs to be an overall process and flow. I'd argue to also reduce the number of channels.

This is an issue to better document the cat herders PM process (in no particular order):

1. Define the flow necessary in order to better communicate effectively.
2. Work to lower the information overload.
3. Take ownership of the process.
4. Own the flow of information.
5. Provide guidance to new members.
6. Lower barriers to entry.
7. Reduce duplicated information.
8. Define the members of the cats and their roles.
9. Provide transparency.

I'm sure there is more, but this is a few things that I see as necessary in a PM role. I'm also clearly not saying 'how' to do this, I will leave that up to the cat herders.

I think the site is being generated from here: https://github.com/ethereum-cat-herders/ethereum-cat-herders.github.io

Although the www repo is ALSO being generated, so it is duplicated here http://www.ethereumcatherders.com/www/

So, I think the WWW repo can be deleted.

https://solc-bin.ethereum.org/ has an expired SSL cert which is causing issues for remix-ide

Via @p-s-dev in community Gitter

Call details in ethereum/pm#89. Please reference ethereum/pm#69 for more detailed instructions.

Date and Time

Proposed time is 14:00 GMT on Tuesday, February 12th, 2019.

Location

Zoom. The link will be posted in the Gitter channel and sent to attendees.

Agenda

1. Update on the progress of the ProgPow Audit
2. Website completion
3. Post Eth Cat Herders Community post (how to get involved etc..)
4. Updates on the action items from Post mortem and how we plan to track them (Subcommittee: Brett, Charles, Hugo, Poojaranjan)
5. Update on the Ethereum Development Portal designs/structure
6. Subcommittee to help Afri with tasks related to hard fork coordination and EIPs monitoring

Action items from Meeting #4

1. ProgPOW Audit - Requirements / Plan / Roadmap / Auditor Options (Highest Priority)
2. Finish Website and Host it on Github Pages (By today. Subcommittee: Charles, Hugo, Adam)
3. Eth Cat Herders Community post (how to get involved)
4. Action items from Post mortem (Subcommittee: Brett, Charles, Hugo, Poojaranjan)
5. Ethereum Developer Portal (design, details, and drafting up an MVP - pick a date)
6. Afri to create a subcommittee for hard fork coordination and EIPs monitoring

In order to track progress for the Istanbul hard fork, we should maintain an Istanbul Hardfork Tracker on the Ethereum Wiki, here.

Past the following deadlines, from the Istanbul Roadmap, here is what we should expect in the tracker:

2019-07-19 (Fri) soft deadline for major client implementations

Suggestion: Track implementation by linking specific "work tickets" related to EIPs (ex: JIRA tickets, Github issues, etc.) instead of simple checkmarks/tickboxes.

2019-08-14 (Wed) projected date for testnet network upgrade (Ropsten, Görli, or ad-hoc testnet)

Suggestion: List client versions for Istanbul
Suggestion: Track "Istanbul-readiness" for testnets

2019-10-16 (Wed) projected date for mainnet upgrade (“Istanbul”)

Suggestion: List client versions for Istanbul
Suggestion: Track "Istanbul readiness" for mainnet.

In order for the tracker to be visible, it should probably be linked on the AllCoreDevs Agenda.

There was a discussion, and this came up to verify as one developer pointed out a possible implementation complexity.

In order for the community to know what is required to propose a Core EIP, we should document the process and "non-spec" requirements. Spec requirements can be found in EIP-1.

The process documented should ideally cover everything from "I have an idea to an EIP" to "my EIP is live on mainnet". This includes, non-exhaustively:

• Proposing an EIP
• Socializing an EIP / getting community support
• The technical requirements for an EIP to be implemented (working code, test vectors, etc.)
• Client or financial support for implementation
• etc.

If someone in the Ethereum community doesn’t know where to file an issue — we should invite them to do it here.

In general, except for very project / repo specific issues, it would be helpful to have all ECH projects have issues here. We can split up when there is more volume.

Also, let’s use Projects! And labels!

Current STARKS use 2^n Galois fields. These are efficient for addition operations however, this is not ideal for the state proofs being considered to reduce state size. Prime fields are a much better candidate, but currently there is no existing implementation. This is something Alexey needs help to proceed.

I use the Netlify CMS https://www.netlifycms.org/ to manage content in Git repos, which is controlled by who has maintainer access to a repo.

Would the EthCatHerders like me to install this? Could be installed in the Jekyll site https://github.com/ethereum-cat-herders/ethereum-cat-herders.github.io

Would mean that notes could all be done on the website, but still be committed to Github. And people who like Git can still use Git.

P.S. @DBrettRobertson was going to see about getting me maintainer access to this repo.

During the latest cat herders calls, there was some interest in helping project management ETH2.0. I am starting this issue with resources to try to get interested members up to speed on the teams.

ETH2.0 Teams Summary
ETH2.0 PM Repo

Person of contact for each team:
ChainSafe - @Mikerah
Prysmatic Labs - @terenc3t
Sigma Prime - @paulhauner
Yeeth - @decanus
Nimbus - @arnetheduck
Artemis - @dangerousfood
Parity - @sorpaas
Harmony - @mkalinin
Trinity - @hwwhww

The more immediate goal is a multi-client testnet and the longer term goal is mainnet launch.

cc'ing @CPSTL, @poojaranjan, @mariapaulafn, Helena Flack

What is the home for Eth1.x specific discussions?
Is it ethresear.ch, ethmagicians, or would it be best to have it's own focused environment?

This is from my own observation that many of the replies to Eth1.x related discussions on ethresear.ch is some form of "this isn't an issue when we move to PoS". How many Eth2 eyes need to see eth1.x and visa versa?

Perhaps mixing the discussions makes finding the relevant discussions more difficult.
Perhaps it is better to have both in the same place as to keep both updated on progress.

@expede presentation on EVM Evolution / EIP615 https://drive.google.com/open?id=1_taRpfsEF-ofF0UpwKyGOH-ogPqxmpUD

Question / comment from @AFDudley -- will JIT'ing optimized code have impact on miners, including uncle rates.

One big point is: we need to do analysis of smart contracts in the wild, and make sure that optimizations don't cause increased forks.

@AFDudley Making it optional is more dangerous -- rather than just make the changes and then it just runs on the network.