1, 2, 3, Blindspots check! Core Units we need? 🕊

As the Foundation keeps dissolving and handing over (or archiving) all the existing projects, we must guarantee continuity.
While new Core Units form and some people leap over to the DAO, it is essential to ensure that no vital function is left underserved.

Those of us on the receiving end would appreciate a heads-up if there’s anything we should take care of that is utterly crucial.
TechOps? A vet for the office dogs? The yoga teacher for the off-site meetings? Please let us know. Doing so will help direct new Core Units forming and nudge adjacent Core Units could take over the responsibility.

Happy to talk to discuss it in private if you feel like remaining anonymous.

Your Operational Support team.

PS, if no Core Unit can take over the responsibility, Operational Support will do it. @amyjung is already learning Kubernetes while I struggle with Vyper.

I might or might not be looking at you, @Derek, @wouter, @rune, @charlesstlouis, @brianmcmichael, @g_dip… and anyone that might have an idea (no matter how wild).


1. Community Management

I’m curious to hear people’s thoughts on what this transition means with regard to MakerDAO’s relationship with the community. CommDev has been responsible for this up until now and MakerDAO isn’t going to suddenly stop having a relationship with the community just because CommDev is going away.

In this new paradigm, I could see ‘community’ encompassing things like events, bounties and project-based jobs, recruitment, customer support, contests, and opportunities to feature community-created content. Some of these functions fall within the mandate of core units that have been proposed but maybe it would be helpful to have a Core Unit to centralize at least some of these efforts?

Whether it’s a Core Unit or just a project coordinated between members of different Core Units, I think we should continue to have a group responsible for community management.

2. Legal

@layerzero Any update on how things are coming with the Legal Core Unit? I think it’s in everybody’s best interest to have a well-compensated legal department responsible for mitigating legal risk for other Core Units and the DAO itself.

3. Tech Ops

What digital properties are going to be managed by the Dai Foundation vs Core Units? How are tech, content, and design going to work together to maintain web properties like makerdao.com?


This is great! Regardless of the subject of the topic, at least we can have a copy of UNI v1 or of CurvDAO now :slight_smile:. K8s, nice!

Is there a consolidated and summarized list somewhere of every proposed Core Unit? Would be very helpful in this exercise to identify gaps and potential overlap rather than scrolling through the MIPs forum and reviewing each proposal one by one.



Exactly, what I was looking for, thanks!

I’m surprised no one has mentioned Corporate Finance and Accounting - is Accounting being outsourced through AccountAble currently?

It is not.

@SebVentures has started exploring this space. He made a couple of really good presentations. I also believe there’s a Community Call somewhere where he goes more in detail.

The Real-World Finance Core Unit is dealing somewhat with that.
You can check MakerDAO financials here.

We also provide a financial presentation every month.

1 Like

I just wanted to say that this thread brings up a very good point. There are quite a few responsibilities the Foundation is taking care of that aren’t necessarily on the radar of the community.

We are working with the teams to list these responsibilities, as well as the code repositories that will be handed over. It may take a couple more weeks, but we’ll definitely put them here to create that comprehensive overview so that we can avoid anything important falling through the cracks.


In addition to the MIP Portal we will likely need a Core Unit Portal at some point.


In the interest of checking blind spots, I started a graphic showing which Core Units are proposing to take responsibility for all of the digital properties owned by MakerDAO and which channels they might need access to in order to fulfill their mandate. None of these are set in stone; please feel free to comment and I’ll do my best to keep it up-to-date.


Thanks, Seth, for getting this started.

Strategic Marcomms unit has listed social media, including Linkedin, Facebook, and Twitter, as part of their proposed mandate. Managing the content of MakerDAO homepage and Maker blog will also be key pieces and crucial for the unit.

The plan shared earlier in March in Rocket Chat’s #core-unit-operating-model-onboarding will be formally submitted for a request for feedback next week.


Great Figma diagram @seth ! I’d add to that list a front end/applications team responsible for building/extending the existing governance portal/governance tools, developer experience, mkrgov-type frontends as well. The foundation JS team is working on a MIP proposal for this at the moment.

^ This also makes me think about ownership of docs.makerdao , which at a first glance would probably be a combination of Integration team, SC, frontend team input for documentation support with overall site ownership held by an overarching group.


Thanks for the diagram, @seth!

Pinging @LongForWisdom to get his thoughts on the ownership of the Governance Portal.

1 Like

Having a tech-ops group keep these platforms running day-to-day is preferable I think. GovAlpha can organise changes and development work if it’s required (maybe with another core unit with that responsibility, or maybe with an external group.)


I was going to add “automation of governance” as use case along with k8s auto-deploy. But thought it could piss off people :wink:


I noticed the Maker Developer portal is missing from the chart. The ownership should presumably go under Front-End/Applications?

1 Like

That portal is for SCD, and is therefore very outdated. Did you mean docs.makerdao.com?

Were there any plans on updating that page? Or have we retired it and moved to docs.makerdao.com?