OPIRS.
OPIRS / Child Architecture

A network of contributing children

The proposed child network will allow participants to opt in to bounded tasks, contribute compute and return results for independent validation.

Contribution accounting: Future child clients will receive signed, bounded tasks; accepted results—not claimed device uptime—will be eligible for non-financial OCC recognition. Learn about credits.

How a child will work

1Opt in
2Register securely
3Accept bounded task
4Return result
5Verify evidence

Coordination topology

Clients communicate with an authenticated HTTPS gateway—not directly with Mother or Redis. The gateway validates identities and resource permissions. An internal coordinator may use Redis Streams for work distribution, while PostgreSQL records durable task and evidence history.

Contributor control

Proposed clients will expose CPU/GPU, memory, scheduling and network limits, plus pause, opt-out and uninstall controls. Task formats, code signing, workload sandboxing, anti-abuse protections and result verification must be completed before release.

No child binaries are currently released. Mobile platforms may support limited or different forms of participation due to operating-system constraints.