Sharing Research & Projects

Overview

You have spent this track building lessons, running activities, and watching students make things. The natural instinct is to keep that work inside your classroom, to grade it, file it, and move on. This module asks you to do the opposite: to treat your teaching materials and your students' projects as work worth sharing, and to learn where and how to share it.

That is not vanity. Teaching XRPL well is still a young craft, and the people doing it are scattered across universities, schools, and training programs that rarely meet. When you publish a lesson that worked, propose a student project for a showcase, or write up a small piece of classroom research, you do two things at once: you give the next educator a head start, and you invite feedback that makes your own practice sharper. This is the closing module of the track because sharing is what turns a solo teacher into part of a community.

We will look at why open sharing matters, the specific channels XRPL Commons opens to educators and researchers, how to prepare work so a non-specialist can actually engage with it, how to run a feedback loop you would be proud for your students to imitate, and how to think about open licensing. No new XRPL mechanics here, just the practice of putting your work, and your students' work, in front of the people who can build on it.

Why share at all

The case for sharing is partly generous and partly self-interested, and both halves are real.

The generous half: educational work compounds when it is open. A lesson plan that stays on your laptop helps one cohort; the same lesson, published, can be adapted by a teacher you will never meet for students you will never see. This is the core idea behind open educational resources (OER), teaching materials released for others to use, adapt, and redistribute freely. The research on OER is encouraging on more than access alone: a 2023 meta-analysis and synthesis in the International Journal of Educational Technology in Higher Education found that open resources and open practices are associated with learning achievement at least on par with traditional materials, and that the practices around openness (collaboration, reflection, adaptation) are where much of the value sits. Sharing is not a tax on your time; done well, it improves the teaching.

The self-interested half: you cannot see your own blind spots. Work that never leaves the room never gets challenged. The moment you put a research brief in front of a peer or a student project in front of a wider audience, you get the one thing a closed classroom cannot give you, an outside reaction. Some of it will sting. Most of it will be useful. All of it is a model you want your students to watch you handle.

There is a quieter benefit too. When students know their project might be shown at a real event, or written up for an audience beyond the teacher, the work changes. The stakes feel authentic. "This is for a grade" and "this could be shown to the XRPL community" produce different levels of care, and the second is the one you want.

Where to share: the XRPL Commons channels

XRPL Commons runs several channels that exist precisely to surface community work. They differ in formality, audience, and what kind of artifact fits, so the skill is matching the work to the channel, not just broadcasting everywhere.

DoctorBlock is the showcase for research. Its premise is deliberately tight: present your blockchain research "in just 180 seconds." For an educator or a graduate student, that constraint is a gift; it forces you to find the single clearest claim in your work and say it to a non-specialist audience. If you have a classroom study, a small piece of pedagogical research, or a student's research project, this is where a distilled version belongs.

The Community Magazine is a quarterly publication covering the XRPL ecosystem. A magazine is a slower, more reflective format than a talk: it suits a written account of how a course went, a teaching method that worked, or a profile of a standout student project. If you have something that reads better than it presents, this is its home.

Meetups happen across Europe and beyond, local, in-person gatherings of people in the ecosystem. These are the lowest-stakes place to share. Bringing a student project to a meetup, or simply describing what you are teaching and asking the room what they would change, is often the fastest way to get honest, conversational feedback.

The podcast offers insights into people and partners in the community. It is a channel to be aware of rather than one you submit a paper to, but if your work or a student's story is genuinely notable, a longer-form conversation is one of the formats the community uses.

Beyond these live channels, XRPL Commons is building broader research infrastructure: a UBRI Research Corpus to gather academic work on blockchain across sectors, and a community Research Lab to advance tools and research on the ledger. These are emerging rather than open-submission today, so treat them as a direction the field is heading, not a form to fill in this week. The point for now is that the appetite for academic and educational contributions is real and growing; you are not shouting into an empty room.

Making work shareable

A research brief or project write-up only earns feedback if someone outside your head can follow it. The most common failure is not weak work, it is work explained as if the reader already lives in your classroom.

Three habits fix most of it. Lead with the claim, not the buildup. Whatever your one sentence is ("students grasped tokenization faster when they designed a loyalty scheme first"), say it first, then support it. The 180-second format of DoctorBlock is good discipline for this even when you are writing, not speaking. Strip the jargon, keep the substance. Your audience is fellow educators and a broad ecosystem community, not specialists in your subfield; a piece that needs a glossary will not get read. Show the artifact. A real lesson handout, a screenshot of a student's project, a short clip: concrete evidence invites concrete responses, where abstraction invites silence.

Crucially, ask for the feedback you actually want. "Thoughts?" gets you nothing. "Did the loyalty-scheme framing make tokenization clearer, or did it confuse the underlying mechanics?" gets you a real answer. Naming your one feedback question is the difference between publishing and merely posting.

The feedback loop, and modeling it

Sharing is only half a loop; the other half is receiving what comes back. This is a skill, and it is one your students are watching you perform whether or not you mean to teach it.

Receive critique the way you wish your students would. Listen for the signal before defending the work. Separate "I disagree" from "I feel criticized." Ask clarifying questions instead of explaining why the critic misunderstood. Then, and this is the part that closes the loop, visibly revise something based on what you heard, and say so. A teacher who shares a lesson, takes a hard note from a peer, and comes back with version two has just modeled the entire practice of open scholarship more vividly than any lecture could.

This is also how you should frame student showcases. When a student presents a project at an event and the audience pushes back, your job beforehand is to prepare them to hear it as a gift, not a verdict. The feedback loop you run on your own work is the rehearsal for the one you ask them to run on theirs.

Sharing openly: licensing in one breath

If you publish a lesson or resource and want others to genuinely build on it, say so explicitly. Releasing work under an open licence (a Creative Commons licence is the common choice for educational materials) tells the next teacher exactly what they may do: use it, adapt it, redistribute it, with attribution. Without a stated licence, a well-meaning colleague who wants to reuse your worksheet does not actually know whether they are allowed to. Open educational resources are defined as much by their licence as by being free to access. You do not need to become a copyright expert; you need to make one deliberate choice and attach it, so that "share" really means "others can build on this."

Check

You are done when you can move one real artifact from "finished" to "ready to share." Take something concrete from your own teaching (a lesson you ran, a research note, or a student project) and write a one-page sharing plan: name the artifact, choose the specific XRPL Commons channel for it (a 180-second DoctorBlock showcase, the Community Magazine, a meetup, the podcast) and say why that channel fits, identify the audience it reaches, state the open licence you will release it under, and write the single feedback question you most want answered.

The feedback question is the part that proves you understood the module. Anyone can publish; an educator who is genuinely sharing knows exactly what they are asking the community to help them improve. Hand your plan to a peer and have them confirm the channel fits the artifact and the feedback question is one they could actually answer.

Resources

• XRPL Commons
• Creative Commons licences