Diversity & Inclusion

Blockchain Academics is a small, distributed editorial operation. Our writers, editors, contributors, and educators come from a range of geographies, backgrounds, and entry-points into the crypto industry — engineering, traditional finance, journalism, academia, and on-chain native. We hire on craft and curiosity, not network.

Our public masthead is at /masthead and the editorial team page at /authors. Each profile lists role, expertise areas, credentials, location, and social links so readers can verify who wrote what.

We commit to fair, inclusive coverage that reflects the global nature of the technology we report on. Crypto is built and used everywhere — our coverage and our team should reflect that.

• Hiring & contributor onboarding — we actively seek qualified writers from regions and backgrounds that are under-represented in industry press: Africa, Latin America, Southeast Asia, the global South generally, and writers whose first language is not English.
• Sourcing — reporters work to expand source lists beyond default Western talking heads. When a story has the same five people quoted everywhere, that’s a signal to dig wider.
• Coverage — protocol launches, regulation, and adoption in non-US/EU markets get covered on their merits, not relegated to occasional “international roundup” posts.

Blockchain Academics has zero tolerance for harassment or discrimination of staff or contributors on the basis of race, ethnicity, gender identity, sexual orientation, religion, disability, or age. Internal complaints go to the founder directly. External harassment of our writers is documented and, where appropriate, escalated.

We are a small operation and we don’t pretend the team is larger or more representative than it is. We will publish numbers when the team is large enough that aggregate data is informative rather than identifying. Until then, the masthead is itself the report — click through, read the bios, see who is here.

If our coverage misses a region, community, or perspective that we should be reporting on, tell us: [email protected]. Concrete tips and source introductions are particularly welcome.