October 31, 2023

Agenda

  1. Member introduction

    1. Kshitij

      PM on Flow, protocol, tokenomics, governance for past year

      Previously PM at Amazon

      Involved in web3 for past 3-5 yrs as economist, thinking about networks from economic perspective. Dominant educational background here.

      Has thought about how blockchain should be governed from decentralised perspective

      Excited to bring up issues being faced and most need action

    2. Layne

      <add bio>

    3. Vishal

      PM for Flow Protocol

      Joined 2019 as engineer to work on networking layer Supported node operation team and transitioned to PM

      Now with the foundation Excited to have community driven approach to node operation especially

      Previously Akamai enterprise architect

    4. Jonny from Increment

      Defi project on Flow Working on DEX and token-fi for staking Previously, software engineer at Google Started with CryptoKitties and purchased lots of kitties on Ethereum

    5. Next Up:

      1. You?
  2. Meeting cadence
    1. Does monthly work?
      1. Yes
    2. Does the time work?
      1. Yes
    3. Questions:
      1. Process for ad-hoc meetings for urgent decisions?
        1. Discord channel to ping here + issue invite if there is something critical
          1. Examples:
            1. New node operator is needed for the next epoch switchover
            2. Fork coordination in case of chain divergence
      2. Is Tokenomics Working Group going to be merged with this call? What are next steps there?
        1. It will continue to function separately, just working to standardize approach
        2. Kshitij organizing next meeting soon
      3. Is service account owned by governance working group?
        1. Not owned by operationally supported by GWG
        2. Service account will continue to function as normal but may have requests from GWG to service governance actions
  3. Existing Priorities
    1. Permissionless node operation
      1. GWG ISSUE: Node selection process
      2. 2 issues:

        1. Node selection criteria for new nodes

          1. Have they run a node on the Flow network previously?
            1. Access
            2. Verification
            3. Collection
            4. Consensus
            5. Execution
          2. Have they run a node on other networks?
            1. Yes
              1. Which ones? (weighting for number of other chains supported)
            2. No
          3. Have they submitted a question on discord? on GitHub? the forum?
            1. Yes
              1. Share links
            2. No
          4. Have they submitted a Pull Request on GitHub?
            1. Yes
              1. Share links
            2. No

          REQUIRED CATEGORIES ABOVE

          WEIGHTED CATEGORIES FOR SCORE BELOW

          1. Can they self-stake minimum or are they relying on delegation/external funding?
            1. Yes
              1. Share account
            2. No
          2. Do they have broader assets under management to contribute further to the ecosystem? (threshold: 5x minimum stake)
            1. Yes
            2. No
          3. Are they offering a co-marketing opportunity to the ecosystem? (threshold: 100k users or 10k devs)
            1. Yes
            2. No
          4. Do they have dedicated on-call support for the node?
            1. Yes
              1. Contact info
            2. No
          5. Do they exist in a new jurisdiction? Do they add to the overall geographic and political decentralization of the network?
            1. Yes
              1. Where?
            2. No
          6. Criteria Check

            1. Required: Either

              1. A,C,D true
              2. B true

              +H always

            2. Weighted criteria

              1. E, F, G, I some or all true

            3. Slots are given based on rank as slots become available

        2. Apply that criteria to updating staking table

        3. Outstanding issue:

          • [x] draft selection criteria
          • [x] Decision on current operators requesting slots
            • [x] Quantnode
          • [ ] Next up: Publish the selection criteria + scoring matrix and share with node operator repo @Kshitij Chaudhary
      3. Existing issues:
        1. (pending) Quantnode - requesting collection, consensus node
          1. Run Flow node before/currently? No
          2. Other networks? Yes, Agoric, Aptos, Axelar, Graph Network, NYM, Persistence, Quasar, Sui and Umee
          3. Involved on discord? Only to ask about running a node
          4. Contributed to GH? No
          5. Minimum stake covered? Yes
          6. Assets under management? Yes
          7. Co-marketing for ecosystem? <unsure>
          8. Dedicated support? Yes
          9. Score: 3/5, should qualify
    2. Voting

      1. Contribute to product requirements for Flow’s voting tool https://cast.fyi/ in the following doc:

        77acaef6-5953-4aeb-9f37-26b920f6b9f2_Cast_PRD.pdf

      2. Is this currently impactful?

      3. Background: started July/August, project came from Collectives for anyone to vote + build proposals. Resurrected as primary tool for voting on FLIPs.

        1. 3 Phases:
          1. 🚧 Phase 0: revamp branding and update to vote predominantly on FLIPs (rather than supporting DAOs where there are stronger complimentary projects in the ecosystem)
          2. ✍️ Phase 1: update to on-chain voting
            1. Is it important to verify balance on chain?