RESTORE is open-source infrastructure. Nobody is hired in the conventional sense. Contributors earn Sovereign Credits, own the infrastructure they build, and get credited in every deployment that runs their code. These are the capabilities the network currently needs most.
All roles are volunteer-based in State 0. Contributors earn SC through verified builds and deployments. These are not job listings — they are invitations to co-own infrastructure that outlasts any company.
P2P Network Engineer — libp2p / State Machine
Own the State 1 → State 2 transition. Implement the Rust libp2p DHT genesis, BLE mesh handshake layer, and LoRaWAN fallback. This is the most critical piece of the stack — the moment the network becomes genuinely sovereign.
Cloudflare Edge Developer
Build the State 0 cloud-lite layer: Workers for SC ledger API, D1 for structured data, R2 for IPFS-pinned Merkle roots. Deliver sub-100ms response times globally while keeping the architecture migration-ready for State 2.
Security Researcher — Traffic Obfuscation Protocol
Audit and harden the Traffic Obfuscation Protocol (TOP): Query Padding to 2048-byte blocks, Chaffing ghost queries, and Delayed Batching (100ms–2500ms random). Prove metadata resistance against nation-state adversaries.
PWA / Frontend Engineer
Build the mobile-first Progressive Web App that serves as RESTORE's primary interface in State 0. Offline-capable service workers, BLE handshake UI, SC balance display, hex feed, Maker's Market listings. Ships before the native app.
Mobile Engineer — React Native / Expo
The native mobile app that replaces the PWA. Deep BLE integration for proximity handshakes, TEE-backed key storage, push notifications for mission completions and SC transactions. Android-first, iOS second.
Distributed Inference Engineer — Petals / WASM
Build the Mobile Agent Routing Architecture: LOCAL_ROUTER → TEMPLATE_RESPONSE → MICRO_LLM → P2P Petals tiers. Implement the physical buffer technique for smooth UX during inference latency. Port WASM models for State 2 edge inference.
Agent Prompt Architect — Six Agents
Design and iterate the six personal AI agents: Body (metabolic), Mind (cognitive), Freedom (legal/financial), Purpose (meaningful work), Tribe (social capital), Energy (resource independence). Each agent needs a distinct system prompt, tool set, memory protocol, and failure mode.
Anomaly Detection Engineer
Implement the Anomaly Engine: >300% velocity spikes, 50 users in 10m radius within 1hr, identical TEE payloads, Jaccard index vouch clustering. Build the sortition jury trigger and resolution pipeline. This is the fraud-prevention layer protecting the SC economy.
City Node Coordinator — Launch City
Own the physical rollout in one city. Recruit the first 200 players needed to trigger State 1 Activation. Coordinate Stewards, run BLE handshake events, document what breaks, and feed real-world constraints back into the protocol design.
Steward Programme Lead
Design and run the Steward onboarding programme. Stewards are the trusted nodes who anchor each hex — they hold 3-of-5 Social Guardian Key recovery shares, vouch for new players, and maintain community standards. The programme needs documentation, training, and ongoing support.
Ancestral Nutrition Advisor
Design the Body Agent's nutrition mission set. What verified food actions earn SC? How does the agent measure metabolic improvement over time? Bring real ancestral nutrition knowledge — organ meats, seasonal eating, fermentation, animal fats — into mission design.
Community Microgrid Engineer
Design the Energy Agent's mission architecture. How does RESTORE verify solar installation, battery storage, weatherisation? How are energy savings translated to SC mint anchors? What does a community microgrid look like at 200 players?
Food Sovereignty Network Builder
Connect RESTORE to real food producers — regenerative farms, community gardens, food co-ops. Build the supply relationships that give the Maker's Market Day 1 inventory. Design the farm-to-hex logistics protocols.
Protocol Governance Designer
Formalise the governance layer. How does sortition selection work in edge cases? What happens when a jury deadlocks at 7/12? How does the duty cap (2 per month, 8 per year) get enforced? Write the governance spec that makes the system self-governing.
Corporate Partnership Lead
Build the corporate contribution layer. RESTORE v6 is pragmatic about corporate involvement — companies can earn verified ESG data, contribute infrastructure, and reach players. Design partnership tiers, contribution verification, and the governance guardrails that prevent capture.
Documentary Filmmaker / Visual Storyteller
Document the first city deployment. Capture the first BLE handshake, the first SC transaction, the first hex that reaches 200 players. This is not marketing — it is the permanent record of an infrastructure transition that matters.
01 —
Infrastructure that outlasts you
RESTORE is public domain. No IP ownership. No company can be acquired and shut it down. Every line of code you write runs in a network that belongs to its users. Permanently.
02 —
Nobody tells you what to build
There are no product managers here. The whitepaper and blueprint are the spec. If you see a gap, fill it. If you think the design is wrong, propose a change. The network governs itself.
03 —
Your work is publicly verifiable
Every contribution is logged to the Merkle chain. Your builds, your mission completions, your SC earnings — all publicly auditable. The permanent record of your contribution to a piece of infrastructure that actually mattered.
04 —
SC rewards are real
Contributor SC earnings spend at the Maker's Market — real food, real services, real community resources. The more the network grows, the more SC can replace fiat for daily needs. You are building your own safety net.
05 —
The problem is actually solvable
RESTORE v6 abandons ideological purity in favour of pragmatic sequencing. State 0 works with existing infrastructure. State 1 transitions gracefully. State 2 delivers full sovereignty. The architecture is buildable by a small team over two years.
06 —
Mesh or die — the nodes stay on
The network is designed to survive hostile environments, power outages, and internet blackouts. In State 2, a hex can operate indefinitely on BLE mesh and solar power alone. You are building resilience that matters when everything else fails.
The capabilities above are what the network knows it needs right now. But RESTORE is being built by people who identify the gaps themselves. If you have a skill that belongs in this stack, tell us.
All applications are read by a human. Response within 7 days. The best way to get in immediately: join the Discord and show your work.
community
Start building in the Discord
The fastest path to contributor status is showing up and building something. Every line of code that ships earns SC.
// sign_in