Netrun: Foundations for a Connected Onchain World
Abstract
This discussion draft outlines a possible foundation for Netrun: a set of ideas for connected digital experiences on Solana. It considers how builders, participants, and shared infrastructure might work together within a clear and approachable system.
The document is illustrative. It describes areas for exploration rather than a deployed protocol or an approved technical specification. Product details, interfaces, and release plans will be defined through implementation and review.
Introduction
Useful digital systems bring people and information together. As more applications use shared onchain records, the quality of the connections between those applications becomes an important part of the user experience.
Netrun proposes starting with understandable interactions and explicit boundaries. The aim is to help builders reason about what their applications do, what participants control, and which assumptions an integration depends on.
The Problem
Builders frequently face a choice between designing a complete system from scratch and adapting their ideas to infrastructure created for a different purpose. Participants encounter the consequences through inconsistent interfaces and information that is difficult to move between applications.
A shared foundation could reduce that repeated work. To be useful, it must make its behavior predictable and its limitations visible, while allowing individual applications to develop their own experiences.
What Is Netrun?
Netrun is currently a project direction for exploring open, connected onchain experiences. This draft organizes that direction into records, application capabilities, and the processes that help contributors coordinate.
These ideas are intended to be evaluated independently. A builder should be able to understand one capability without adopting an entire product, and a participant should be able to identify what an interaction changes before approving it.
Shared Records
A shared record represents information that several participants or applications need to interpret consistently. Its design should explain who can create it, which fields may change, and how another application can verify its history.
Possible examples include a contribution record, an evolving game object, or a community membership. The exact representation and storage approach remain subjects for technical evaluation.
The Coordination Layer
Coordination begins with explicit responsibilities. Creators define an experience, builders implement its behavior, and participants decide how they want to use it. Supporting infrastructure should make the boundaries between those roles clear.
A $NETRUN token launch on Solana is planned. CA not available yet. The official contract address will be published on this website 5 minutes after the token launch. The token's role and mechanisms require a documented design and review.
Application Modules
A module would group a small, coherent capability behind a documented interface. It should state the data it accepts, the changes it can make, and the errors a calling application needs to handle.
Versioning is part of that contract. Builders need a way to assess updates, preserve compatibility, and understand when an integration requires changes. Examples and migration notes should accompany any published interface.
Decision Making
Project decisions should have a visible context: the problem being addressed, the alternatives considered, and the people responsible for carrying out the work. A public proposal process may become useful as participation grows.
The immediate priority is a clear record of decisions and an approachable route for feedback. Formal voting or other governance mechanisms would require their own specification.
Resource Allocation
Development requires attention, infrastructure, and maintenance. Planning should account for all three, including the ongoing cost of keeping documentation and integrations useful after their first release.
No token allocations, funding commitments, or reward schedules are defined in this draft. Any future resource program should publish its eligibility rules and the responsibilities of its participants.
Practical Utility
The value of a capability should be visible in a working interaction. For a creator, that may mean publishing information once and making it usable in several places. For a developer, it may mean replacing a fragile integration with a documented contract.
Prototypes should focus on those outcomes. Feedback from people completing real tasks will help determine which ideas deserve further development.
Interaction Costs
Participants need to understand the cost of an action before taking it. A future application should distinguish network costs from any service charges and explain what happens if a transaction is not completed.
This draft does not set prices or fees. Those parameters depend on the eventual implementation, and should be documented with the relevant user flow.
Areas to Explore
Several kinds of experience could benefit from more consistent shared foundations. Early exploration will favor small, observable interactions where the outcome can be evaluated directly.
- Portable records of community participation
- Digital objects that reflect activity over time
- Connected tools for creators and their audiences
- Shared experiences across games and applications
- Developer tools for inspecting and understanding data
Builder Ecosystem
A builder should be able to begin with a readable example and trace it through to a documented interface. Good documentation includes expected behavior, common mistakes, and the limits of what an example demonstrates.
We also want to learn from integrations that do not fit. Those cases often reveal assumptions that need to be made explicit or boundaries that need to be reconsidered.
Security and Infrastructure
Any onchain implementation must define its trust boundaries, permissions, and failure modes. Using an existing network does not remove the need to review application logic and the infrastructure around it.
Future technical documentation should cover authorization, transaction handling, data validation, and operational responsibilities. This website does not connect to wallets, process transactions, or implement a protocol.
Development Direction
Our launch sequence begins with the website, followed by the $NETRUN token and its official contract address.
Product research and prototypes will continue alongside the launch plan. Published interfaces and integrations depend on what those experiments demonstrate.
- Deploy the website: Publish the Netrun website, our mission, and the documentation. Give the project a place to grow.
- Launch $NETRUN: Launch the Netrun token on Solana. Launch details will be shared through our official channels.
- Publish the CA: The official contract address will be published on this website 5 minutes after the token launch.
Long-Term Vision
We are interested in a world where a useful contribution can become the starting point for someone else's work. Shared records, clear interfaces, and understandable permissions can help make those connections possible.
Netrun will develop through the people who take part and the problems they choose to solve. The goal is to keep the foundation clear enough to support ideas we have not yet imagined.
Document Status
This is demonstration content for the Netrun website. It is a discussion outline, not a statement of available product functionality, a financial offer, or a release commitment.
Replace this draft with the reviewed project specification before presenting it as a final whitepaper. The original-document link below will become available when a destination is configured.