Introduction And Goals

1. Introduction And Goals

Dastan (home of Decrypt and Rug Radio) is working to build the world’s largest decentralized media network. Our mission is to craft an ecosystem that equitably benefits content creators and consumers alike, ensuring that every interaction enhances the collective value of our network.

This document lays out that vision over the next 12 months and is centered around four key areas:

Infrastructure Development: Establishing the foundational pillars of our decentralized network built on top of Arbitrum’s Layer 2 technology allowing for high-frequency micro-transactions at minimal cost, ensuring a smooth and efficient user experience.
Consumer Applications: Crafting applications to enrich user engagement within the Decrypt and Rug Radio ecosystem.
Creator Products: Developing comprehensive tools and resources to bolster creators' content production and monetization capabilities.
AdTech Network: We are re-imagining online advertising to show advertisers how much more value can be provided in a more holistic, community driven approach to attention.

Ecosystem Requirements The Dastan ecosystem includes four groups of participants.

The Company
Content Creators
Content Consumers
Partners

Each group plays a key role in supporting the others and architectural decisions are made to maximize the distribution of value to all four groups - not just the suits on Sandhill Road.

Table 1.1 The Company
No.	Requirement
R1.1	The company needs to be able to offer rewards to the community at scale.
R1.2	The company needs to be able to onboard thousands of creators and offer them the tooling and support they need to grow in the ecosystem.
R1.3	The company needs to be able to pair partners with creators for the best possible return on ad spend.
R1.4	The company needs to be able to easily plug in 3rd party networks, communities and projects that want to leverage the AdTech and Rewards Systems.

Table 1.2 Content Consumers
No.	Requirement
R2.1	Consumers need to be able to easily find high quality content that aligns with their interests and values.
R2.2	Consumers need to be able to discover new creators and new topics through search but also through suggested content based on their past behavior and user profile.
R2.3	Consumers need the ability to earn rewards for participating in the network. Engaging with content, learning in the LMS and interacting with partners will create opportunities for value accrual back to consumers.
R2.4	Consumers need the ability to participate on-chain in a way that is intuitive and does not require advanced training in blockchain technology.

Table 1.3 Content Creators
No.	Requirement
R3.1	Creators need tooling to enable them to create world class content.
R3.2	Creators need wider distribution for their content.
R3.3	Creators need to be able to monetize their content.

Table 1.4 Partners
No.	Requirement
R4.1	Partners need to be able discover the best creators in the network to partner with based on real world data about the creators network and reach.
R4.2	Partners need to be able deploy $MEDIA tokens to create campaigns and ads to the most relevant segments of the Dastan Ecosystem.

1.1. Quality Goals

Table 1.5 Quality Goals
No.	Goal	Description
G1	Usability	Prioritize a user-friendly experience by making the system easy and pleasurable to use by focusing on aesthetics, attractiveness, and intuitive interaction. Users will be able to utilize blockchain rails without worrying the needs of wallets, contracts or other advanced web3 technologies.
G2	Reliable	Ensure the system is available, robust, dependable, and fault-tolerant.
G3	Secure	Establish a consistent, accountable, confidential, and integrous system.
G4	Efficient	Optimize system performance in terms of speed, responsiveness, and efficient utilization of resources such as memory, CPU, threads, and the blockchain network. Maintain efficient development, maintenance, and operational processes.

1.2. Stakeholders

This table focuses on stakeholders of the system, i.e. all person, roles or organizations that

should know the architecture
have to be convinced of the architecture
have to work with the architecture or with code
need the documentation of the architecture for their work
have to come up with decisions about the system or its development

Table 1.6 Stakeholders
Stakeholder	Description	Expectations
Advertisers	Entities investing in campaigns; interested in overall system behavior and performance.	Understand the system architecture and how it impacts advertising campaigns, transparent communication on how their goals align with the architectural decisions.
Creators	Content producers using the platform; need to understand how their work integrates.	Grasp the architectural aspects that influence content creation, documentation that helps them navigate the platform’s architecture for optimal collaboration.
Developers	Individuals involved in system implementation; require in-depth architectural knowledge.	Have a deep understanding of the system’s architecture for effective coding and problem-solving, comprehensive documentation detailing the architecture and coding standards.
System Administrators	Responsible for platform maintenance, including managing the system’s whitelabel settings and related functionality.	Comprehend the architecture for efficient system maintenance, with a specific emphasis on managing whitelabel settings, clear documentation on system configurations, maintenance procedures, and guidance on adjusting whitelabel settings as needed.
Product Owners	Define system vision and direction; must align with architectural decisions.	Grasp the high-level architecture and how it aligns with business goals, documentation that communicates architectural choices in the context of business objectives.
Regulatory Compliance Officers	Ensure system compliance with legal and regulatory standards.	Understand the system’s architecture to ensure compliance, documentation detailing how the architecture meets regulatory requirements.
QA Team	Verify that the system behaves as documented; need detailed understanding of expected behavior.	Understand the architecture to perform comprehensive testing, documentation that outlines expected system behavior for accurate testing.
Technical Writers	Create and maintain documentation; require understanding of the architecture.	Grasp the architecture to create accurate and informative documentation, the architecture to be well-documented for clear communication.
Project Managers	Oversee project timelines and goals; need high-level understanding of system architecture.	Understand the system’s architecture to align project timelines with technical considerations, documentation that provides a high-level overview of the architecture.
Decision Makers	Individuals responsible for strategic decisions about system development and enhancements.	Understand the implications of architectural decisions on the overall strategy, documentation that outlines the strategic rationale behind key architectural choices.