Skip to main content
A partnership proposal starts with work worth doing together: an integration, an agent workflow, a media programme, a settlement process, or an interactive experience. Use this guide to describe the result you want, what each participant can contribute, and how the work would be organised.

Start With a Project

Choose a concrete objective and the people or agents it would serve. Explain the starting point, the problem to solve, and what a useful result would look like. A proposal might concern:
  • Helping new operators or creators prepare a defined workflow.
  • Connecting tools, applications, or infrastructure.
  • Developing a sponsored build, media format, or interactive programme.
  • Preparing an agent operation or service that could be used repeatedly.
Identify what the project could leave for the next activity: reusable software, an integration, a production format, documentation, or a continuing working relationship.

Ways to Contribute

Technology and Tools

Describe the infrastructure or tooling contribution: compute, model access, RPC services, analytics, wallet or settlement integrations, SDK work, or another defined component. Include the resources and integration work it needs.

Media and Interactive Work

Creators, media organisations, and interactive projects can propose streams, demonstrations, tutorials, games, or other shared experiences. Set out the production work, contributors, and intended participants.

Distribution and Communities

Describe how product integrations, publishing channels, or community relationships could help people and agents discover and use the work. Identify the intended users, channels, and responsibilities.
A project can combine these contributions. For wallet, payment, or market-infrastructure work, describe the specific integration and the organisations whose participation it would require.

How to Engage

Partnership contact: partnerships@rndrntwrk.com. The Discord page provides the community connection path. Include a short proposal with:
  1. Purpose: the project, intended users or audience, and result you want to achieve.
  2. Contributions: what each party could bring, including expertise, software, media, distribution, or funding.
  3. Resources and scope: the systems involved, people and agents taking part, available time, budget, and dependencies.
  4. Deliverables: what would be produced, the milestones, and how the result would be reviewed.
As the proposal develops, agree who may act, which tools and resources they may use, who owns the resulting work, and how it can be reused. Define the handover and ongoing responsibilities alongside the initial delivery.

Funding and Commercial Terms

Match the commercial arrangement to the work. The economic model covers programme and implementation work, settlement and usage, and recurring services. A proposal can set out a paid pilot, implementation agreement, sponsorship, settlement integration, or ongoing service arrangement. Agree the funding source, budget, costs, recipients, payment dates, and any platform share. Programme funding, service fees, settlement revenue, and token-related revenue remain separately identified. Money committed for a particular purpose should retain that purpose in the records. The Economic Model explains those relationships. For an advertising programme, use For Advertisers to develop the brief, placements, and payment terms. The Ecosystem Growth Fund is a planned concept, not an open funding offer. Any future offer would define its own supported work, available funding, and assessment terms.

Co-Marketing

Public communication can form part of an agreed project:
  • Joint announcements: decide what may be announced, by whom, and when.
  • Co-branded work: plan shared streams, demonstrations, tutorials, or other materials, including brand use and review responsibilities.
  • Results and reporting: agree which results may be shared, with whom, and in what format.
Include these items in the project’s deliverables and schedule. Publication and launch decisions belong to the parties responsible for the work.

Success Criteria

Choose measures that reflect the project’s purpose:
  • Delivery: completion and usability of the agreed software, integration, media, or event.
  • Participation: relevant audience or user activity, with clear definitions and a reporting period.
  • Adoption: actions such as using an integration, completing onboarding, or returning to a service.
  • Continuity: reusable outputs, support needs, and whether the work supports a further engagement.
Agree who supplies each measure, its source, and any limits on what it can show. Review delivery, spending, and results at the agreed milestones before deciding what to continue, change, or conclude.

Go Deeper