Unity SDK

[boorich]

Project Name

Sablier Integration Module for web3.unity SDK

1. General Information

• Team Name: ChainSafe
• Funding Details:
  • Funding Address: To be provided upon request

2. Project Overview

2.1 Project Pitch

The project aims to develop a module for ChainSafe's open-source web3.unity SDK that integrates Sablier Streams, enabling Unity game developers to utilize real-time token streaming within their games. This integration provides a seamless and innovative monetization model for game developers by leveraging broker fees to create sustainable revenue streams.

2.2 Core Features

ChainSafe

• Token Streaming Integration: Real-time token streaming capability within Unity games.
• Broker Fee Implementation: Monetization via broker fees to generate revenue for developers.
• Blockchain Interaction: Secure API integration to interact with Sablier's protocol.

Sablier

• Compatibility with B3 Chains: Sablier to add support for B3 chains to ensure broad blockchain compatibility.

2.3 Comparable Projects

As far as our research goes, there are no existing Unity-compatible SDKs specifically integrating Sablier Streams. However, this project provides a unique solution by focusing on token streaming for game monetization, unlike traditional in-app purchases or ads, and integrates with Unity via a modular, dependency-injection approach.

2.4 Supporting Documentation

We are working on a technical design document.

3. Team Information

3.1 Team Members

• Nikola, Lead Developer: Extensive experience in Unity SDK development and blockchain technology. Previously led the development of modular SDK solutions for game developers.
• Martin, Project Manager: Experience in managing blockchain integration projects, ensuring timely delivery and effective collaboration between partners.
• Rob, Engineer: Unity and Blockchain Developer
• Sneakz, Engineer: Unity and Blockchain Developer
• Oleksandr, Engineer: Unity and Blockchain Developer

3.2 Relevant Experience

Previously, the team developed web3.unity, an open-source tool allowing Unity game developers to easily integrate blockchain features such as wallet connections and asset management.

3.3 Technical Expertise

The team has extensive experience with Unity development, modular SDK design, blockchain integration, and protocols such as Ethereum. We have also worked with broker fee implementations for similar monetization models and created a prototype game including token streaming for Unity prior to filing this request.

4. Project Development

4.1 Development Status

Currently in the planning phase. Technical requirements are being defined, and initial communication has been established with Sablier.

4.2 Milestones & Timeline

• Milestone 1: Project Kick-off and Planning
  • Review Sablier documentation, establish communication channels, define technical requirements.
• Milestone 2: SDK Module Development
  • Develop and integrate the Sablier token streaming module within "web3.unity."
• Milestone 3: Testing and Quality Assurance
  • Functional, security, and cross-platform testing.
• Milestone 4: Documentation and Release
  • Finalize documentation and prepare for launch.

4.3 Funding Requirements

Yes, we require funding to cover development costs, testing, and documentation. Estimated amount: $60,000 - $120.000.

5. Detailed Development Roadmap

Milestone 1 — Initial Development

• Estimated Duration: 0.5 - 1 month
• Key Deliverables:
  • 0a. Documentation: Provide an overview of the code and project functionality.
  • 0b. Initial Project Kick-off: Review Sablier's SDK and define the integration approach.

Milestone 2 — Module Development

• Estimated Duration: 1-2 months
• Key Deliverables:
  • 1a. Module Integration: Develop a Unity module for token streaming using the "web3.unity" SDK.
  • 1b. Broker Fee Implementation: Integrate broker fee monetization features.

Milestone 3 — Testing and QA

• Estimated Duration: 0.5 -1 month
• Key Deliverables:
  • 2a. Functional Testing: Validate token streaming features.
  • 2b. Security Testing: Ensure secure API handling and compliance.
  • 2c. Cross-Platform Testing: Verify functionality across most popular Unity platforms.

Milestone 4 — Documentation and Release

• Estimated Duration: 1 month
• Key Deliverables:
  • 3a. Developer Documentation: Create setup guides, API references, and tutorials.
  • 3b. Release Preparation: Prepare the module for public release and initiate joint promotional activities.

6. Future Plans

6.1 Long-term Vision

After completion, we plan to maintain the module as part of web3.unity, making it open-source and continuously improving it based on community feedback. Furthermore we plan to incorporate it into upcoming games delivered to the B3 gaming platform.

7. Additional Information

7.1 Questions & Concerns

• B3 Chain Support: Sablier's team needs to add B3 chains to the list of supported chains in their protocol to ensure compatibility with this module.

[boorich]

Hi there,

since our team is exploring the possibility of associating Sablier's ERC-721 token streams with game assets that can be imported into the Unity Game Engine, we're considering:

Linking Sablier Streams to Game Assets:

• Modifying the tokenURI function in the FlowNFTDescriptor contract to include additional metadata fields.
  • This metadata would point to game assets (e.g., URIs for 3D models, textures) that Unity can import.

Integrating with Unity Game Clients:

• Allowing players who own a Sablier stream to access the corresponding game assets within Unity games.
  • The game client would fetch the token metadata, retrieve the asset URIs, and load the assets dynamically.

Modifying Sablier Contracts:
We understand that changing the FlowNFTDescriptor contract would require updates across all networks where Sablier is deployed. Altering core contracts could lead to significant maintenance challenges and might not align with Sablier's roadmap.

Questions for the team:

Is the Sablier team open to supporting modifications to the FlowNFTDescriptor contract to include additional metadata for use cases like ours? If so, what would likely be the most elegant way to proceed with these changes?

Alternative Approaches:

If modifying the FlowNFTDescriptor isn't feasible, would you recommend one of the following approaches, or do you have other suggestions?

Deploying a Proxy or Wrapper Contract:
Creating our own ERC-721 contract representing game assets, linking each token to a Sablier stream via the streamId. This method increases complexity.

Using Off-Chain Mapping:
Maintaining an off-chain database that maps Sablier streamId to game assets. This method introduces centralization concerns.

Best Practices and Guidance:
Are there established best practices for linking existing ERC-721 tokens to additional metadata without modifying the original contracts?
Has anyone already tackled similar challenges, and could share insights or recommendations?

Our Goal:
We believe that integrating game assets with real-time token streams can unlock exciting possibilities in the gaming and blockchain space. Our aim is to find a solution that aligns with Sablier's vision and maintains the integrity of the platform while enabling innovative use cases.

[PaulRBerg]

Hi @boorich and ChainSafe team,

Thank you for submitting such a detailed proposal for the Sablier integration module for the web3.unity SDK. We appreciate your enthusiasm for incorporating Sablier Streams into Unity.

That said, after reviewing the requested funding amount, we regret to inform you that it is beyond our current budget. Additionally, with our team fully committed to developing Sablier Flow (our upcoming open-ended streaming protocol), we don’t have the bandwidth to effectively collaborate on this project at the moment.

We also believe your project would be a more natural fit for Sablier Flow, which aligns better with the use case you're targeting than our existing Sablier Lockup protocol. I imagine streaming in a gaming context would be mostly focused on subscriptions, which could benefit from the functionalities we are building with Flow.

We encourage you to revisit this proposal once Sablier Flow is fully launched, as it may provide the support and compatibility necessary to achieve your objectives.

Thank you for your understanding, and we hope to explore opportunities to collaborate in the future.

[boorich]

Understood. We'll keep an eye on Sablier Flow in the meantime.