Purpose 9ten is a decentralized music streaming platform leveraging peer-to-peer data sharing technologies and the W3C ActivityPub protocol to create a social network for artists and fans. The platform enables listeners to pay an optional monthly subscription fee, fairly distributed to their top 9 most-listened-to artists each month.
Vision Statement To revolutionize the music streaming industry by fostering a fair, transparent, and decentralized ecosystem that empowers artists and engages listeners. Our goal is to create a platform where the needs and rights of artists and listeners take precedence over large conglomerates.
- Fair Compensation
- Decentralization of Power
- Transparency in Operations
- Artist Empowerment
- Listener Engagement
- Responsive to Community Needs
- Developers: Implement and maintain the technical aspects of the platform, including ActivityPub integration and Hyperledger Fabric setup.
- Artists: Upload music, engage with fans, and manage earnings.
- Server Admins: Set up and manage 9ten server instances, ensuring data integrity and reporting.
- Listeners: Use the platform to stream music, support artists, and interact with content.
- Developers: Opportunity to work on cutting-edge technologies and contribute to an innovative project.
- Artists: Fair compensation, direct engagement with fans, and control over their content.
- Server Admins: Regular revenue from listener subscriptions and control over their instances.
- Listeners: Directly support favorite artists and enjoy high-quality, decentralized streaming.
Provide a high-level architecture diagram showing the interaction between various components (ActivityPub servers, Hyperledger Fabric nodes, client applications, etc.).
Illustrate the data flow from the point a user listens to a track, to how data is logged, verified, and payments are distributed.
- Adapt for Audio: Modify the codebase to support audio streaming, ensuring efficient handling of audio files.
- Custom Activities: Define new ActivityPub activities for music-specific interactions:
ListenActivity: Represents a user listening to a track.StreamActivity: Represents live streaming events.SubscriptionActivity: Represents subscribing to an artist or node.
- Custom Objects: Create new objects to represent musical content:
AudioTrack: Includes metadata like artist, album, duration, etc.Playlist: User-curated lists of audio tracks.
Extend the API endpoints to handle new activities and objects, ensuring compliance with the protocol.
- Deploy Hyperledger Nodes: Each ActivityPub server also runs a Hyperledger Fabric node.
- Chaincode Development:
- Subscription Payments: Logic for subscription payments, ensuring $1 goes to node operators and $9 is pooled for artists.
- Streaming Rewards: Distribute funds to artists based on verified streaming data.
- Transaction Verification: Ensure all transactions are verified and recorded on the ledger.
- Payment Handling: Payments are processed through listeners' digital wallets, interfaced with Hyperledger Fabric.
- Streaming Data: Nodes collect streaming data and report it to the ledger for data integrity and transparency.
Implement automated systems to detect anomalies in streaming data.
- Verification Process: Disputes are reviewed by the local node, a peer within the cluster, and an external node.
- Resolution Workflow:
- Flagging Discrepancies: Automatically flag potential disputes.
- Manual Review: Nodes perform manual reviews, consulting with other nodes as needed.
- Third-Party Arbitration: A node from another cluster can arbitrate using detailed logs and data.
- Achieve Consensus: Ensure all parties agree on the resolution.
- Record Keeping: Document all disputes, resolutions, and arbitration outcomes for transparency and audits.
Listeners pay $10 USD equivalent in USDP to their local node’s wallet. Payments handled externally through cryptocurrency wallets or payment gateways.
$1 to node operators on the 1st of each month for operational costs. $9 pooled for artist payouts, distributed by the 25th based on verified streaming data.
- Managed through secure payment gateways.
- Smart contracts record subscription details, ensuring continuous service.
- Multi-node verification ensures transaction validity and updates the ledger.
- Automated renewals and expirations handled through the system.
- Capture detailed streaming data, aggregated daily at node level.
- Automated anomaly detection for potential data issues.
- Data anonymized and encrypted for privacy and security.
- Compile daily reports into a comprehensive monthly report.
- Internal and peer reviews ensure data accuracy.
- Automated dispute resolution protocol for discrepancies.
- Verified data used for calculating artist payouts through smart contracts.
- Maintain comprehensive records for audits and regulatory compliance.
- Community Guidelines: Establish guidelines for community interaction and contribution.
- Governance Model: Define how decisions are made, who has voting rights, and how conflicts are resolved.
- Strategy: Outline strategies to attract early artists and listeners.
- Partnerships: Potential partnerships with music schools, indie artist collectives, and other music industry entities.
Describe how user data is protected and anonymized.
Outline the security protocols for transaction handling, data storage, and communication.
Provide a timeline for development phases, including major milestones.
Plan for alpha, beta, and public release, including testing and feedback loops.
Define key performance indicators (KPIs) to measure progress.
Define key terms and acronyms used in the document.
Include references to technical resources, standards, and external documentation.
Address common questions that stakeholders might have.