Technology
The YOM technology framework represents a cutting-edge ecosystem designed to support the development, management, and delivery of highly interoperable browser-based UE5 experiences. Anchored in a decentralized architecture, this technology stack utilizes a blend of edge computing, peer-to-peer networking, Unreal Engine, AI, blockchain, web technologies, and pixel streaming.
These technological pillars enable YOM to offer dynamic platforms such as the Decentralized Cloud Gaming / Pixel Streaming Network (DePIN), the decentralized application (dApp), and the Software Development Kit (SDK). Together, these components create a robust environment for studios, artists, and developers to innovate and explore new realms within the Web3 space.
Technology Components
DePIN: DePIN is crucial for streaming high-quality digital content efficiently across the globe. Its sophisticated design minimizes latency and maximizes scalability, ensuring users anywhere can access content quickly and reliably.
dApp: The dApp is central to managing digital assets, configuring experiences, and engaging with the YOM community. Its wide range of functionalities includes asset management, user interaction tools, and community governance features, making it a comprehensive tool for ecosystem management.
SDK: The YOM SDK within Unreal Engine 5 offers a full suite of development tools that empower creators to build rich and interactive digital experiences. It encompasses everything from initial design to final deployment, providing a powerful resource for creators at every stage of development.
Key User Journeys
User Flow 1: Play a Game
Access the destination:
Navigate to any partner site hosting YOM games.
(Optional) Log in using a Web3 wallet for personalized experiences or token-gated content.
Stream Initiation:
Click "Play" to start any hosted game stream.
The system connects to an available Streamer Node through our orchestrator.
As the game loads, the player may see a custom loading screen or advertisements.
The YOM pixel streaming technology initializes, preparing the game for interaction.
Gameplay:
Once loaded, the player can interact with the game in real-time through their browser.
The player may interact with web widgets that our partner implemented via our SDK.
Utilize any other integrated features like voice chat or in-game purchases.
Post-Game:
After finishing the game session, players may see results, rewards, or prompts for community engagement.
The stream closes, freeing up the Streamer Node for other players.
User Flow 2: Setup a Node (app.yom.ooo/nodes)
Acquire Node NFT:
Purchase a Node NFT from the YOM marketplace or a secondary market.
Store the NFT in a compatible Web3 wallet (e.g., MetaMask).
Node Staking:
Log into the YOM dashboard using the Web3 wallet containing the Node NFT.
Navigate to the Node Management section.
Select the Node NFT and choose the "Stake" option.
Complete the staking process by performing the KYC.
Hardware Setup:
Receive the physical hardware (e.g., SSD) from YOM.
Plug ‘n Play your node into your system.
Node Activation:
Boot your PC - our custom OS will boot and automatically participate in the network.
The dashboard will update to show the node as "Running".
Monitoring and Maintenance:
Use the dashboard to monitor node performance, earnings, and network status.
User Flow 3: Setup a Stream (app.yom.ooo/streams)
Game Preparation:
Develop the game using Unreal Engine 5 and the YOM SDK.
Utilize the SDK's tools for web integration, mobile support, player handling, etc.
Test the game locally using the SDK's development environment.
Dashboard Access:
Log into the YOM dashboard with any wallet.
Navigate to the Stream Management section.
Stream Deployment:
Click "Create New Stream" and provide basic information (game name, description, etc.).
Use the drag-and-drop interface to configure stream settings:
Set quality parameters (resolution, frame rate, etc.)
Configure player limits and matchmaking rules
Set up virtual cameras for pre-game viewing
Upload the packaged game files to the YOM network.
Integration Setup:
Configure any external connections (e.g., website, domains, social media, data feeds).
Set up web widgets (JS SDK ) for additional functionality (chat, leaderboards, etc.).
Launch:
Perform a test stream to ensure everything is working correctly.
Non-Functional Qualities
To satisfy our user journeys, we defined the non-functional requirements, or the architectural qualities are defined as follows:
User Feedback: Measured through user feedback and technical performance assessments.
Authentication Speed: Speed and reliability of user access methods.
Latency: Regular testing to ensure latency remains below the 15 ms threshold.
Load: Capacity tests during peak traffic to ensure scalability under stress.
Security Audits: Frequency and outcomes of scheduled and random security audits.
Incident Reports: Tracking and resolution of security incidents.
Customization Utilization Rate: Frequency of use of customization features.
Developer Engagement: Active use and feedback on the modular tooling system.
Integration Points: Number of third-party integrations facilitated.
Cross-Platform Engagement Metrics: User interaction rates across different platforms.
Last updated