OPEN CALL / JULY 30, 2026
Welcome
to the GRID.
A call to the crypto community: developers, maintainers, organizers, moderators, writers, designers, researchers, educators, and operators. The machine layer is taking shape. Now we need the human network.
This is not a call to mine, host a node, or rent compute. This is a call to help build and steward the project itself.
Crypto talks endlessly about decentralization. But software does not become decentralized because a repository is visible, and a community does not become real because a Discord server exists.
Decentralization requires people who can understand the work, disagree in public, maintain what they did not invent, explain what they did not market, and carry responsibility without waiting for permission.
GRID began with a technical proposition: machines everywhere can become a useful compute fabric when resources, work, verification, identity, and settlement are coordinated. That proposition spans more than a protocol. It requires software, interfaces, documentation, events, support, governance experiments, security review, and durable contributor operations.
The project already has enough surface area that one person cannot responsibly remain the only center of context. That is not a weakness to hide. It is the exact moment when open source has to become a practice instead of a label.
We are not recruiting spectators around a token story. We are inviting people into unfinished work: code that needs review, tests that need depth, language that needs precision, communities that need care, and institutions that have not yet been designed.
PROJECT SNAPSHOT
The work is real. The contributor base is early.
Snapshot measured directly from the GRID workspace and production contributor database on July 30, 2026. Generated dependencies and build artifacts are excluded.
56,712
lines of source
Measured across Rust, TypeScript, TSX, CSS, Python, SQL, and shell code.
305
source files
Excluding dependencies, generated builds, distribution folders, and caches.
5
connected codebases
Core GRID, the website and portal, networking, coordination, and Solana integration.
68
web + API routes
Public pages, documentation, registry, explorer, contributor, mail, task, and admin surfaces.
6
contributor paths
Engineering, education, community, OTG, creative communications, and coordination.
1
approved contributor
The contributor system is new. The project is not waiting for a crowd to pretend it already exists.
Rust: 18,297 lines across 63 files.
TypeScript + TSX: 35,592 lines across 224 files.
Infrastructure: AWS SES/Lambda/DynamoDB and Cloudflare Workers/D1.
Quality gap: seven detected test files—an explicit invitation to QA contributors.
WHO WE ARE LOOKING FOR
Contributors of every kind—provided the contribution is real.
Open-source developers + maintainers
Rust, TypeScript, React, Cloudflare Workers, distributed systems, APIs, networking, cryptography, Solana, testing, release automation, and the unglamorous maintenance that keeps public software alive.
Review code. Open issues. Improve tests. Fix rough edges. Design APIs. Build examples. Make releases repeatable. Help turn a founder-led codebase into a contributor-owned practice.
Security reviewers + adversarial thinkers
People who notice trust boundaries, unsafe defaults, authentication mistakes, economic exploits, privacy leaks, dependency risks, and claims that outrun evidence.
Threat-model the system. Review passkeys, sessions, messaging, registry flows, resource verification, and operational boundaries. Teach us where the design is fragile.
Community managers + moderators
Not engagement farmers—stewards. People who can welcome newcomers, maintain standards, connect questions to answers, de-escalate conflict, and make participation legible.
Shape Discord channels, contributor onboarding, office hours, working groups, community safety, support practices, and a culture where serious people can do serious work.
OTG organizers + local conveners
Programmers of gatherings: speaker curators, workshop leads, venue operators, volunteer coordinators, local chapter starters, partnership builders, and production people.
Help make OTG more than a conference page. Produce build nights, technical workshops, local meetups, demos, contributor sessions, and the annual gathering itself.
Writers, educators + translators
Technical writers, documentation engineers, educators, DevRel practitioners, translators, diagram makers, and people who can explain difficult systems without making false promises.
Improve API docs, tutorials, architecture maps, examples, onboarding, release notes, accessibility, localization, and the plain-language bridge into GRID.
Designers, storytellers + communicators
Product designers, UX researchers, brand designers, motion artists, editors, video producers, social leads, press thinkers, and community storytellers.
Give GRID a coherent public language. Make tools usable. Document real people doing real work. Help communication remain accurate, memorable, and unmistakably ours.
Researchers + crypto-native operators
Distributed-systems researchers, mechanism designers, governance experimenters, DAO operators, grants people, legal and policy thinkers, and protocol historians.
Interrogate Proof of Resource, incentives, identity, reputation, coordination, public goods, contributor governance, and the boundary between a working pilot and a decentralized destination.
Project managers + quality operators
Issue triagers, release coordinators, QA leads, product managers, accessibility testers, program operators, and people who are unusually good at closing loops.
Turn ideas into scoped tasks. Keep decisions visible. Track dependencies. Reproduce bugs. Define done. Help contributors know what matters and where their work fits.
DISCORD + SLACK
Two rooms. Two different jobs.
Public Discord / the commons
Start in the open.
Discord is the public front door: meet the community, ask questions, share relevant work, find a working group, discuss events, propose an idea, or understand the project before requesting contributor access.
It should remain welcoming to curious people and useful to serious builders. No credential is required to begin participating.
Enter GRID Discord ↗Contributor Slack / operations
Coordinate trusted work.
Slack is for approved contributors doing active work: issue triage, release coordination, project channels, task assignment, working sessions, moderation operations, OTG production, and decisions that need accountable owners.
Access follows contributor approval. Every approved contributor also receives a @gridmail.dev identity, secure dashboard, task board, passkeys, and authenticator-based 2FA.
Request contributor access →THE ASK
Bring a skill.
Find unfinished work.
Leave it more open.
You do not need to be a protocol engineer. You do need to care about evidence, follow-through, public work, and the people beside you. Show us what you know, what you want to learn, and what you are ready to own.