Skip to main content
The protocol is the shared rules and interfaces RNDRNTWRK is developing so different products and operators can work together—connecting identity, authority, ownership, and value. An activity can involve several services. Those services need to agree on who is acting, what they are allowed to do, what happened, who owns the result, and how any payment is handled.

What the Protocol Connects

Participants and authority

Identify the people, agents, companies, or services involved. Record the role each has, the resources it can use, and the limits on its actions.

Work and participation

Connect an activity to its participants and results. A contribution record needs enough information to explain what it represents and how it was checked.

Ownership and obligations

Keep track of who owns the work, how it may be used, and any agreed payment or other commitment arising from the activity.

Payment and settlement

Connect payment requests to the authority behind them, the intended recipients, and the outcome. Retain the information needed to follow an interrupted or incomplete operation.

Components and Roles

The component pages explain these roles and their design in more detail. A role in the system is separate from the capabilities offered by a particular product setup.

Participation and Evidence

A participation record can describe a game session, a contribution to a programme, or another defined activity. Checking the record means comparing it with the activity’s rules and the available evidence. The result needs to remain connected to the session, participant, and method used to check it. That helps an experience explain its scores, reports, or other uses of the record. Audience Inventory explores how participation records can inform media placements and commercial arrangements.

People and Agents

People and agents can participate through the same foundations. They may act separately, collaborate, or operate under authority delegated by another participant. Each role still has its own permissions, resources, and agreements. An agent’s record should identify what it was authorised to do and the activity carried out under that authority.

How Products Use the Foundations

  • 555stream: Media production, programming, publishing, and interaction.
  • 555 Arcade: Games, challenges, and interactive experiences with records of participation and results.
  • Alice: RNDRNTWRK’s agent for developing and testing research, planning, coding, and media operations.
  • Commercial programmes: Agreements about work, funding, recipients, and reported results.
SW4P connects payment instructions to route selection, fees, execution, confirmation, recovery, and accounting for the result. SW4P Earn extends SW4P’s economic model into source-aware allocation, claims, rewards, payout schedules, reserves, and reconciliation. Current status: SW4P Earn is not yet publicly available. No staking, liquidity, reward, or claim programme is currently open.

Working with the Component Documentation

Start with the component that matches the activity you want to support. Use its source and integration reference for the version you are working with, including its interfaces, authority requirements, and supported behaviour. The Roadmap explains how the broader system is intended to develop.

Go Deeper

VAP

Read about participation records and verification.

AGG

Follow the payment-routing model.

Hyperlink

See how payment and participation requests can be presented through links.

Economic Model

Understand funding, costs, payments, and the platform’s share.

Fee Distribution

Read about source-specific allocation policies.

For Developers

Explore the architecture and integration responsibilities.

Architecture

See how client, service, agent, and settlement components fit together.

SW4P

Read about the settlement engine and operation lifecycle.