[2022-05-10] Tea Time Notes

What: Community Call
When: 2022-05-10T16:00:00Z
Facilitator: Gaian
Attendees: Gaian, aia, PostArchitekt, dendrons, zkchun, John Sterlacci, Chase Chapman, itsdanwu, julz.eth, Appt Pupil, Cadena


  • Intro (5-10 minutes)
  • Reflecting on common themes found in the previous meeting (10-15 minutes)
  • Asking the question, does SL want to have buy in to specific milestones or just aims and domains? (5-10minutes)
  • Seeing if we can settle on a GEFNSETT resource allocation system (20-25 minutes)
  • Closing, reflections and next steps(10 minutes)



  • Take a moment to mentally prepare for the next hour
  • Open space for people to share things they are grateful for
  • The goal today: Find something that is GEFNSETT for resource allocation

Reflecting on common themes found in the previous meeting

  • External funding
    • What happens when pods generate their own funds?
      • Not an immediate concern, so it is a hypothetical case → can be marked for later
    • The most direct form of funding for ON are internally sourced funds (internal within the Orca network)
    • If this situation changes in the short term, it will resurface as a tension to address
  • Autonomy
    • Tension: Boundaries around tokenomics and community autonomy are part of things that need to be made explicit
    • How can pods explore to generate their own funds?
    • Defining what we might mean by “tokenomics”
      • Protocol token strategy around Orca, exists as an SL domain
      • Coordinape’s $GIVE tokens, contributor NFTs, etc. could be considered outside of that
    • Outside grants and DAO partnerships → can be marked for later

What do we mean by commissioned domains?

  • Should all current AD be considered as commissioned domains? Implying that domains that are not open for ON to claim are non-commissioned.
  • Commissioned domains are domains that SL identifies are important for the Orca ecosystem, but can also live outside of the SL pods
    • Making funds available in the process
    • Source pod can then help find a home for it
  • Domains that arise from within ON, they may need to find another funding vehicle
  • Another way of framing this is ON internal vs ecosystem domains
    • Example: metagovernance vs ON treasury management
      • Metagovernance is valuable to the Orca ecosystem so would be commissioned
      • Treasury mgmt is valuable to ON internally
        • It may need to get funding other than direct-to-domain
        • It could, for example, pull this from a lump sum grant (such as the first X1 grant)
    • Tension: Lack of definition around commissioned vs non-commissioned domain
      • Commissioned vs NC is not a proxy for important vs non-important
      • NC may need request for funding proposals
      • Commissioned are an ongoing commitment from SL to keep it going
      • NC could become commissioned it context and situation changes

Does SL want to have buy in to specific milestones or just aims and domains?

  • I.e., does SL want to sign off on each milestone on a more granular level, or only the umbrella of AD?
  • When SL grants funds to a domain as the source, we could attach a time span to that and set a date for a retro around that domain
    • “Was the amount enough?”
    • “Were expectations met?”
  • Having retros is good
    • We’re all learning as we go
    • Things will jump out as sensible things to define KPIs around as we go

Seeing if we can settle on a GEFNSETT resource allocation system

  • Allocating based on domains, but deciding how funds are allocated at the pod level makes the most sense
  • If ON do coordinape style work should there be a standard way of doing it across pods?
  • Nav-naut currently the go-to pod for tooling, but having some autonomy for pods to experiment makes sense too as this makes us all learn quicker
  • To create a flexible organization:
    • Funding domains is better to keep things flexible
    • Funding pods maybe end up with pods having a budget they don’t know what to spend on
    • When domains get moved between pods, we should not tie people down to a pod and allow them to move with the domain they are most passionate about
  • Tension: We need a clearer interface between SL and ON when it comes to funding
    • Should this process involve negotiation?
    • What is the source pod’s role in this?
    • The process for going from unfunded to funded should not have too much friction
  • If allocated amount is less than asked, what is the time frame to come around and ask for a top up?
    • Pod can choose to start work in the domain with funding at that time
    • If the pod meets or exceeds expectations, the chance is high that more funding will be made available, as people will recognize that this can be done and that it’s valuable work
    • Ideally, we define criteria in the initial grant/ fund to move on to next steps
      • Perhaps some room for smart contracts to help with this step
      • Conversely, maybe the project gets terminated if it fizzles out if it turns out to be unproductive

Next Steps

  • Creating space for external funding + tokenomics discussion
  • Collaborate on framework for thinking about resource allocation
  • Tying progress of this to source pod meeting (2022-05-12T20:00:00Z)
  • At Friday’s community call, we reach general agreement or consent on basic framework for the specific topics we talked about
    • Then follow up on external funding

If anything is missing or inaccurate, please reply so I can correct it.