📄
OurNetwork Learn Session 1: Syllabus
📄

OurNetwork Learn Session 1: Syllabus

Classes, times, and topics
There will be lectures on Tuesday and Thursday every week from 11 AM to 12 PM EST (For now, subject to poll in discord), and focus groups on Monday, Wednesday, and Friday at the same time (again hours may vary as weeks go on).
https://ournetwork.mirror.xyz/gP16wLY-9BA1E_ZuOSv1EUAgYGfK9mELNza8cfgMWPQ - all class recordings!
Attendance is expected, but recordings will be sent out in case of time conflicts.
  • Lectures are for learning high-level new material and SQL/Ethereum concepts.
  • Focus Groups are like office hours in university but will have prompts/protocol delegates around as well.
  • We'll have other events such as protocol presentations as well in the first two weeks.
The lesson plan is below, we may adjust this if the pace is too fast/difficult for everyone.
Week one: Learning to become an Etherscan detective, and understanding the data/token landscape!
Week two: Making sense of smart contracts, specifically learning to work with composable data!
Week three: Putting it all together, to become an open-source query Dune Wizard!
  • Lecture 6: All about Visualizations (Boxer)
Week four*: Dashboards and Storytelling, really connect with the community behind the data!
  • Lecture 8: Telling stories with your charts, formatting well (Boxer)
⚠ïļ
*The fifth and last week of the course is Thanksgiving week, but we will spend it reviewing all students' work and hosting daily office hours. Fourth-week bounties will be delayed to the end of the fifth week, so students have more time to work on their dashboards and write-ups.
Helpful Resources:
I'll compile a list of query resources below:
ðŸ”Ē
Web3 Query Quick Start Guide
🏓
Table Mapping Guide
⏱ïļ
Dune Utility Queries
📔
Reading Resources
Student Bounties
Bounties will be split between all students each week in the following order:
  1. 0.4 ETH: Solid basic understanding of token types and Web3 data, post a simple query showcasing this understanding.
  1. 0.6 ETH: Post a chart thread related to protocol questions (sub)
  1. 1.2 ETH: Commit to one of the protocols and dive deeper into the data to try and explain the context behind parameters needed to answer protocol questions (main)
  1. 2.2 ETH: Produce a dashboard/report on the protocol question and do a write-up on it!
For simplicity, qualification for the bounty will be based on the teachers' judgment of effort during classes and output by Sunday of each week. Student output should relate to protocol sponsors and be posted on Twitter. Protocol details are outlined in the page linked below (will be further detailed as we go on)
❓
Protocol Overviews/Questions
 
⚠ïļ
Payouts will be handled in Mirror splits, which I will create each week. It's up to the student if they want to claim it each week or just claim it at the end of the four weeks. I'll live demo this as well the first week.
Logging Course Material Understanding and Students/Teachers Relationships:
This will be a more advanced test, but at the end of every week we'd love for students to allocate their 1000 GIVE tokens to others on coordinape based on:
  1. How much you understood that week (if you feel completely lost, then don't allocate more than 200 tokens).
  1. Who helped you learn or work with weekly material
So if I was a student and didn't really understand the material at all, I would allocate maybe only 100 tokens to the teachers. Or if my understanding was mostly bolstered by a fellow student, I could allocate more GIVE to the student rather than a teacher!
Teachers will also have 1000 GIVE tokens, and these should be given to students providing exemplary work or support.
This is an experiment to help us visualize course progress in a more Web3 native way, and I'll do a live tutorial the first time we allocate as well. We'll also adjust the pace/staffing of the course based on the weekly results.
We want to observe the cohort graph like this:
notion image
⚠ïļ
Coordinape allocations do not hold any monetary value and will not affect any bounties or payouts to students/teachers, this is purely for research purposes.
https://app.coordinape.com/
Success Metrics:
To be transparent, these are the general success metrics we'll be looking at for this course. There are some student-specific metrics as well based on background, but those won't be shared until the end.
  • Students output on Dune (# of queries, dashboards, likes)
  • Students engagement level with teachers/attendance
  • Students engagement level with other students
  • Students getting hired by a protocol within 3 months
  • Teachers are consistently around to answer questions
  • Teachers ability to communicate and pace course material
Now, let's all make sure we learn and have fun together! 🙂
Technical Stack for Course:
This is more just note-keeping, but here's the tech stack we'll be using for everything in this course:
POAPs:
  • protocols (issue later)
Mirror.xyz:
  • Auction (Protocol Sponsor)
  • Posting Lectures/Entry Editions (With Glass protocol token-gated content)
  • Splits (teacher payout and student bounties)
  • Applications (Typeform → python scripts)
Guild.xyz/Discord:
  • token-gated roles
  • token-gated lectures
  • scheduling with public gcalendar
Coordinape:
 
📄
OurNetwork Learn Session 1: Syllabus
📄

OurNetwork Learn Session 1: Syllabus

Classes, times, and topics
There will be lectures on Tuesday and Thursday every week from 11 AM to 12 PM EST (For now, subject to poll in discord), and focus groups on Monday, Wednesday, and Friday at the same time (again hours may vary as weeks go on).
https://ournetwork.mirror.xyz/gP16wLY-9BA1E_ZuOSv1EUAgYGfK9mELNza8cfgMWPQ - all class recordings!
Attendance is expected, but recordings will be sent out in case of time conflicts.
  • Lectures are for learning high-level new material and SQL/Ethereum concepts.
  • Focus Groups are like office hours in university but will have prompts/protocol delegates around as well.
  • We'll have other events such as protocol presentations as well in the first two weeks.
The lesson plan is below, we may adjust this if the pace is too fast/difficult for everyone.
Week one: Learning to become an Etherscan detective, and understanding the data/token landscape!
Week two: Making sense of smart contracts, specifically learning to work with composable data!
Week three: Putting it all together, to become an open-source query Dune Wizard!
  • Lecture 6: All about Visualizations (Boxer)
Week four*: Dashboards and Storytelling, really connect with the community behind the data!
  • Lecture 8: Telling stories with your charts, formatting well (Boxer)
⚠ïļ
*The fifth and last week of the course is Thanksgiving week, but we will spend it reviewing all students' work and hosting daily office hours. Fourth-week bounties will be delayed to the end of the fifth week, so students have more time to work on their dashboards and write-ups.
Helpful Resources:
I'll compile a list of query resources below:
ðŸ”Ē
Web3 Query Quick Start Guide
🏓
Table Mapping Guide
⏱ïļ
Dune Utility Queries
📔
Reading Resources
Student Bounties
Bounties will be split between all students each week in the following order:
  1. 0.4 ETH: Solid basic understanding of token types and Web3 data, post a simple query showcasing this understanding.
  1. 0.6 ETH: Post a chart thread related to protocol questions (sub)
  1. 1.2 ETH: Commit to one of the protocols and dive deeper into the data to try and explain the context behind parameters needed to answer protocol questions (main)
  1. 2.2 ETH: Produce a dashboard/report on the protocol question and do a write-up on it!
For simplicity, qualification for the bounty will be based on the teachers' judgment of effort during classes and output by Sunday of each week. Student output should relate to protocol sponsors and be posted on Twitter. Protocol details are outlined in the page linked below (will be further detailed as we go on)
❓
Protocol Overviews/Questions
 
⚠ïļ
Payouts will be handled in Mirror splits, which I will create each week. It's up to the student if they want to claim it each week or just claim it at the end of the four weeks. I'll live demo this as well the first week.
Logging Course Material Understanding and Students/Teachers Relationships:
This will be a more advanced test, but at the end of every week we'd love for students to allocate their 1000 GIVE tokens to others on coordinape based on:
  1. How much you understood that week (if you feel completely lost, then don't allocate more than 200 tokens).
  1. Who helped you learn or work with weekly material
So if I was a student and didn't really understand the material at all, I would allocate maybe only 100 tokens to the teachers. Or if my understanding was mostly bolstered by a fellow student, I could allocate more GIVE to the student rather than a teacher!
Teachers will also have 1000 GIVE tokens, and these should be given to students providing exemplary work or support.
This is an experiment to help us visualize course progress in a more Web3 native way, and I'll do a live tutorial the first time we allocate as well. We'll also adjust the pace/staffing of the course based on the weekly results.
We want to observe the cohort graph like this:
notion image
⚠ïļ
Coordinape allocations do not hold any monetary value and will not affect any bounties or payouts to students/teachers, this is purely for research purposes.
https://app.coordinape.com/
Success Metrics:
To be transparent, these are the general success metrics we'll be looking at for this course. There are some student-specific metrics as well based on background, but those won't be shared until the end.
  • Students output on Dune (# of queries, dashboards, likes)
  • Students engagement level with teachers/attendance
  • Students engagement level with other students
  • Students getting hired by a protocol within 3 months
  • Teachers are consistently around to answer questions
  • Teachers ability to communicate and pace course material
Now, let's all make sure we learn and have fun together! 🙂
Technical Stack for Course:
This is more just note-keeping, but here's the tech stack we'll be using for everything in this course:
POAPs:
  • protocols (issue later)
Mirror.xyz:
  • Auction (Protocol Sponsor)
  • Posting Lectures/Entry Editions (With Glass protocol token-gated content)
  • Splits (teacher payout and student bounties)
  • Applications (Typeform → python scripts)
Guild.xyz/Discord:
  • token-gated roles
  • token-gated lectures
  • scheduling with public gcalendar
Coordinape:
Â