This proposal covers adding the “Protocol” newsletter (https://protocol.dappadan.xyz/), created by DappaDan, as a bi-weekly series to the Developer DAO newsletter.
The Protocol newsletter aims to provide Web3 Developers with guidance and insights into Web3 protocols and developer tools. It aims to be a unique asset in the community by being a place where developers can get answers, saving them time and stress on searching for and choosing tools.
Adding this to the Developer DAO newsletter will provide useful content to developers who are outside of the DAO. It will also be a great vehicle to grow new partnerships with protocols as well as deepen the relationship with existing protocols we work with.
Scope of Work
Domain of Operations & Team
In collaboration with the existing Newsletter team, we will work to:
Ensure content is edited and maintains a high-quality
Delivery of the newsletter to readers promptly
Develop a clear brand to avoid confusion with the core newsletter
Work within the DAO to ensure that pressing questions and topics of interest are covered in this series
Collaborate with the Partnerships team to seek opportunities to align on content
Foster a fun and safe Member experience
Provide DAO members with high-quality learning opportunities
Educate members on protocols and developer tools
Support DAO members to elevate their impact on the world
Giving newer writers an opportunity to contribute
Position the DAO structurally and financially for long-term success
Newsletter Subscriber Growth
Budget Request (Including value returned to the DAO)
Each issue takes ~3 days to research and write, so I am requesting 500 CODE to cover this plus any extra time to coordinate with others in the DAO. We may request further CODE in the future to incentivise more contributors to the Protocol Newsletter.
500 X 2/month x 3 months = 3,000 CODE
Optional section if drawbacks should be identified.
I am not familiar with paragraph; this post is my first encounter with paragraph. I do have some questions though;
how easy or difficult will the migration be from Substack to Paragraph?
what about the old contents on Substack, can we seamlessly move it to Paragraph?
There are some docs pages about migrating subscribers and content:
I have only used Paragraph without having to migrate so I can’t personally say if what the docs are saying is easy, but you can try to export at least.
My thoughts are that Paragraph offers a lot of crypto native features that would be good to incorporate either now or in the future of the newsletter. Things a farcaster integration, token gating and minting.It does have team management features as well, maybe not to the extent of Substack.
You can create communities to a newsletter in Paragraph as well so if we wanted to create a members edition of something, this could be done.
I would say the biggest difference is that I believe Substack has better discoverablity for new subscribers. I think this is something that Paragraph is focusing on here with their discover feed.
Awesome - is the banner image is an easy fix by just updating the aspect ratio?
Now this proposal has passed do you and @0x24bF6580ED276b6ff3 we need to make a decision on migrating Protocol Newsletter to substack or DD to paragraph. Maybe go back on the email chain with Colin at Paragraph to organise a call?
From my perspective I feel the following features would create value for us over Substack:
Capture emails in feed in farcaster via paragraph frame (see here) directly from our main target audience
Mint//collect editions (believe it’s valuable to bring media on chain in this way, also unlocks opportunities gamify newsletter engagement by rewarding collectors: code, unlocking discord roles etc.).
As @0x24bF6580ED276b6ff3 mentioned, Colin (founder) and the paragraph team will work with us. We mean something to them, we don’t mean anything to SubStack - this is shown by his response to the email asking about DD migrating (you’re looped on this):
Regarding a co-activation/promotion - absolutely! Here are some things we can do:
Share your new newsletter/posts on social media (Twitter/Farcaster)
Paragraph and seeing a lot of growth and attention at the moment. Our newsletter and all our posts being featured on their platform in this way whilst this is happening alone is a quite compelling to me.
They are also happy to prioritise features to make this easier for us.
We can prioritize this feature and get it shipped in the next couple weeks, if that works for you.
Yes, I agree. Being considered/influence on a product’s roadmap is definitely of a high value. Its why enterprises pay the premium.
I started using Paragraph over a year ago and the team definitely ships so I think the question is really a “when should we migrate” vs “if we should” as they continue to add more Web3 native features.
I agree there is not a ton of features we would implement immediately. But it is also is like I roast people on. Web2 is comfortable until its not. Better to this by choice instead having to do this in a rush if Substack decides to change content policies.