Loading...
Supporting developers, startups, and full-fledged companies building on Stellar and Soroban
© 2025 Stellar Development Foundation
Subscribe to the Newsletter
By Stellar Razor and Blazor Suite
Open-Source Razor components for seamless SDEX integration in .NET apps, for Visual Studio and Visual Studio Code.
The SDEX Razor Tools project rounds out the existing features and user-interface components provided by the Stellar Razor Tools and the Stellar Identity Platform by adding full trading capabilities, robust portfolio management, and optional secure integration with identity management.
This combination allows developers to build complete Stellar applications, from basic account management to secure trading and DeFi interactions, all within a unified .NET environment.
SDEX Razor Tools - Product List with Stellar Usage
1. Real-time Order Book Component
- Feature: Displays live buy/sell orders for specific asset pairs on the SDEX with real-time updates.
- Stellar Usage: Uses the Stellar Horizon API to fetch live order book data from the SDEX.
2. Open Orders Component
- Feature: Shows active buy/sell orders for the user’s account, with options to modify or cancel orders.
- Stellar Usage: Interacts with Horizon’s offer management endpoints to manage open offers on the SDEX.
3. Submit Buy/Sell Offer Component
- Feature: Enables users to submit new buy/sell offers on the SDEX.
- Stellar Usage: Leverages Stellar transactions to create and submit offers through Horizon.
4. Completed Orders Component
- Feature: Displays completed buy/sell orders with filtering options.
- Stellar Usage: Retrieves user transaction history from the Horizon API, focusing on completed trades.
5. Portfolio Tracker Component
- Feature: Tracks account balances, asset values, and historical performance.
- Stellar Usage: Fetches account balances and asset values using the Horizon Account API.
6. Market Depth & Order Book Visualization
- Feature: Offers a visual representation of market depth, showing liquidity levels for asset pairs.
- Stellar Usage: Uses data from the order book API to visualize liquidity depth and trading walls.
7. Transaction History Component
- Feature: Displays transaction history with filtering, sorting, and detailed views.
- Stellar Usage: Pulls transaction data from the Horizon transactions endpoint, showing all account operations.
8. Fee Calculator Component
- Feature: Estimates transaction fees for various operations.
- Stellar Usage: Uses Stellar network fee data to estimate the cost of transactions based on network congestion.
9. Multi-Account & Multi-Signature Manager
- Feature: Manages multiple Stellar accounts and configures multi-signature settings.
- Stellar Usage: Uses Stellar’s multisig operations to manage additional signers and set thresholds.
10. Trading Pairs Component
- Feature: Lists available trading pairs on the SDEX, helping users discover tradable markets.
- Stellar Usage: Uses Stellar’s order book API to identify and list active trading pairs.
11. Optional Soroban Integration (Advanced)
- Feature: Allows interaction with Soroban smart contracts, enabling complex DeFi operations.
- Stellar Usage: Uses the Soroban SDK to deploy and manage smart contracts, enabling automated strategies.
12. NuGet Package Distribution
- Feature: Packages all components into a single, installable library.
- Stellar Usage: Makes it easy for developers to integrate Stellar features into .NET applications.
Maybe in the future, but not in this submission
$60.0K
Community adoption of the tools by developers to integrate Stellar blockchain operations into their applications.
Go-To-Market Plan for SDEX Razor Tools
1. Market Overview
- The SDEX Razor Tools are designed for .NET developers to integrate Stellar Decentralized Exchange (SDEX) features into their applications.
- The toolkit will enable the creation of trading and portfolio management apps on Stellar, leveraging reusable Razor components that are familiar to .NET developers.
2. Target Audience
- .NET Developers: Primary users who build financial, trading, and portfolio management applications.
- Stellar Developers: Developers already working within the Stellar ecosystem who want to add trading features to their apps.
- FinTech Startups: FinTech companies interested in exploring Stellar as a blockchain network for trading applications.
- DeFi Builders: DeFi developers looking to integrate Soroban smart contracts alongside SDEX functionality.
3. Key Value Propositions
- Easy .NET Integration: Simplifies Stellar trading integration using familiar Razor components.
- Complete Trading Suite: Covers the entire trading workflow, from submitting offers to managing portfolios.
- Security & DeFi-Ready: Optimized for secure integration with the Stellar DotNet Identity Framework and optional support for Soroban contracts.
4. Positioning & Messaging
- Positioning Statement:
- "SDEX Razor Tools: Simplifying Stellar Trading for .NET Developers – Build secure, scalable trading apps with ready-to-use Razor components."
- Core Messaging:
- For Developers: "Quickly integrate Stellar’s SDEX into your .NET applications with plug-and-play Razor components."
- For FinTech Startups: "Expand your trading capabilities with secure Stellar-based solutions built for .NET."
- For Stellar Community: "Enhance your Stellar projects with powerful trading tools that are optimized for .NET development."
5. Launch Strategy & Phases
Phase 1: Pre-Launch Preparation (Weeks 1-8)
- Goals: Generate awareness, set up initial user base, and prepare materials for launch.
- Key Actions:
- Beta Testing:
- Launch a closed beta to selected .NET developers and Stellar developers via GitHub.
- Collect feedback using GitHub Issues and Discussions.
- Documentation & Tutorials:
- Create complete documentation, tutorials, and a demo project that showcases how to build trading apps using SDEX Razor Tools.
- Marketing Collaterals:
- Develop marketing materials, including a landing page on PakanaComponents.com, blog posts, and a product video demo.
- Microsoft Marketplace Preparation:
- Prepare and submit the components for the Microsoft Marketplace, ensuring compliance with publishing requirements.
- Primary Channels:
- GitHub, PakanaComponents.com, and Microsoft Marketplace.
Phase 2: Initial Launch & TestNet Campaign (Weeks 9-16)
- Goals: Increase awareness, collect user feedback, and drive TestNet adoption.
- Key Actions:
- Public GitHub Release:
- Release the open-source GitHub repository for SDEX Razor Tools, making it available for public testing and feedback.
- Microsoft Marketplace Launch:
- Launch the NuGet package and Razor components on the Microsoft Marketplace for .NET developers.
- Content Marketing:
- Publish tutorials, blogs, and case studies on PakanaComponents.com, showing how to use the tools in real-world scenarios.
- Developer Outreach:
- Focus outreach efforts on .NET developer communities, including forums like Reddit (.NET), Stack Overflow, and .NET-specific blogs.
- Organize a webinar or virtual event to introduce the toolkit and guide developers through its integration.
- Primary Channels:
- GitHub, PakanaComponents.com, Microsoft Marketplace, Reddit (.NET), Stack Overflow, and .NET Blogs.
Phase 3: MainNet Launch & Growth (Weeks 17-22)
- Goals: Successfully launch the toolkit on MainNet, increase adoption, and demonstrate real-world use cases.
- Key Actions:
- MainNet Announcement:
- Announce the MainNet launch on PakanaComponents.com, GitHub, and .NET development forums.
- Showcase Integrations:
- Collaborate with early adopters to create case studies or success stories that can be published on PakanaComponents.com and featured on the GitHub repo.
- Continued Content Marketing:
- Publish success stories, advanced use cases, and tips for optimizing the toolkit for DeFi or secure trading applications.
- Microsoft Marketplace Promotion:
- Promote the NuGet package through the Microsoft Marketplace, and feature it in .NET development newsletters and communities.
- Primary Channels:
- GitHub, PakanaComponents.com, Microsoft Marketplace, and .NET developer newsletters.
6. Marketing Channels & Tactics
- GitHub (Primary Channel):
- Use GitHub Discussions, Issues, and Releases to communicate updates, collect feedback, and support users.
- Serve as the landing page, offering tutorials, documentation, blog posts, and case studies to support developers.
- Microsoft Marketplace:
- Highlight the components as part of the Microsoft ecosystem, reaching .NET developers directly where they search for tools and components.
- .NET Developer Forums & Blogs:
- Engage with Reddit (.NET), Stack Overflow discussions, and popular .NET developer blogs to increase awareness.
- Email Newsletters:
- Utilize .NET-specific newsletters and community mailing lists to reach target users.
7. Success Metrics & KPIs (Adjusted)
- MVP Phase:
- 10 downloads of the NuGet package.
- 2 developers actively using the components in TestNet.
- 5 GitHub stars and at least 5 issues/suggestions logged.
- TestNet Phase:
- 20 downloads of the NuGet package.
- 5 developers using the components, with positive feedback.
- 1 partnership integration with a FinTech or Stellar-based project.
- MainNet Phase:
- 50 downloads of the NuGet package.
- 5 developers using the components on MainNet.
- 2 successful case studies or integrations showing real-world use of the SDEX Razor Tools.
8. Budget Allocation for GTM Activities
- Pre-Launch Preparation: $2,500
- Documentation, tutorials, and initial marketing materials.
- TestNet Campaign: $4,000
- Webinar costs, promotional materials, and community outreach.
- MainNet Launch & Growth: $6,000
- Case studies, marketplace promotion, and continued content marketing.
Travel $5,000
Promotional materials and incidentals
Airfare, travel, and tickets to one conference for two people.
9. Post-Launch Strategy
- Ongoing Support:
- Use GitHub Issues as the primary support channel, with continuous documentation updates on PakanaComponents.com.
- Iterative Development:
- Collect and prioritize user feedback via GitHub, focusing on adding new features and improving integration.
- Developer Evangelism:
- Engage in .NET conferences, meetups, and relevant online communities to promote use cases and drive adoption.
The previously released Razor Component Library receives steady traffic and cloning of its Github Repository and NuGet package.
Here is the current NuGet Trends chart for that library, which was released on April 20, 2024 NuGet Trends
We released the Microsoft Identity Platform for Stellar on 10/20/2024 and are in the process of promoting the release and collecting adoption data.
Real-time Order Book Component
Description: Displays live buy/sell orders for specific asset pairs with real-time updates.
How to Measure Completion: Correct fetching and display of real-time order book data from the SDEX using the Stellar Horizon API.
Estimated Date of Completion: Week 4
Budget: $4,000
Open Orders Component
Description: Shows active buy/sell orders, with options to modify or cancel orders.
How to Measure Completion: Successful display and management of user-specific open orders.
Estimated Date of Completion: Week 5
Budget: $4,000
Submit Buy/Sell Offer Component
Description: Allows users to submit buy or sell offers on the SDEX.
How to Measure Completion: Successful transaction creation and offer submission to the SDEX.
Estimated Date of Completion: Week 6
Budget: $4,000
Portfolio Tracker Component
Description: Tracks account balances and asset values, displaying a user’s overall portfolio.
How to Measure Completion: Accurate display of asset balances and values based on user accounts.
Estimated Date of Completion: Week 7
Budget: $4,000
Transaction History Component
Description: Displays user transaction history with filtering and sorting capabilities.
How to Measure Completion: Successful display of user transactions from the Stellar TestNet.
Estimated Date of Completion: Week 8
Budget: $4,000
Market Depth & Order Book Visualization
Description: Adds a depth chart visualization to the order book component, showing market liquidity.
How to Measure Completion: Accurate visualization of market depth using real-time TestNet data.
Estimated Date of Completion: Week 9
Budget: $4,000
Fee Calculator Component
Description: Estimates transaction fees for various operations.
How to Measure Completion: Correct fee estimation based on current network fees on the TestNet.
Estimated Date of Completion: Week 10
Budget: $4,000
Multi-Account & Multi-Signature Manager
Description: Manages multiple accounts and configures multi-signature settings (may be implemented as update to the Stellar Component Toolkit).
How to Measure Completion: Successful multi-account management and multisig configuration on the TestNet.
Estimated Date of Completion: Week 11
Budget: $4,000
NuGet Package Distribution
Description: Package all components into a single NuGet library for easy installation.
How to Measure Completion: Successful publication to NuGet.org with installation instructions.
Estimated Date of Completion: Week 12
Budget: $4,000
Total Budget for tranche: $36,000
Security & Integration Testing
Description: Conduct thorough security audits and integration tests across all components.
How to Measure Completion: Pass security and integration tests, ensuring components are secure and ready for MainNet.
Estimated Date of Completion: Week 16
Budget: Use of Stellar LaunchKit credits for third-party audits
Real-time Order Book Component (MainNet)
Description: Deploy and optimize the real-time order book component for MainNet usage.
How to Measure Completion: Live, accurate, and consistent order book display on MainNet.
Estimated Date of Completion: Week 17
Budget: $2,000
Open Orders & Submit Offer Components (MainNet)
Description: Ensure both components operate seamlessly on the MainNet.
How to Measure Completion: Successful modification, cancellation, and submission of offers on MainNet.
Estimated Date of Completion: Week 18
Budget: $2,000
Portfolio Tracker & Transaction History (MainNet)
Description: Finalize integration with MainNet to track balances and display transaction history.
How to Measure Completion: Accurate balance display and transaction history retrieval on MainNet.
Estimated Date of Completion: Week 19
Budget: $2,000
Integration with Stellar DotNet Identity Framework
Description: Optimize components for seamless integration with the Identity Framework, ensuring secure transaction handling.
How to Measure Completion: Components support secure transaction signing and user management on MainNet.
Estimated Date of Completion: Week 20
Budget: $4,000
Tutorial and Reference Project
Description: Sample Razor application demonstrating how to use the components to perform real-world operations on-chain in a Visual Studio project with walk-through video.
How to Measure Completion: Publication of working source code on GitHub for a Visual Studio project that demonstrates how to get started with the toolkit and use it on Mainnet to retrieve the order book, submit, modify, and cancel an offer using a Stellar account.
Estimated Date of Completion: Week 22
Budget: $6,000
Final Testing, Documentation & Launch
Description: Perform final MainNet testing, complete documentation, and launch the full NuGet package.
How to Measure Completion: Successful MainNet deployment, complete user-ready documentation, and public launch announcement.
Estimated Date of Completion: Week 23
Budget: $8,000
Total Budget for tranche: $24,000
Steven Tomlinson is the founder and architect for Pakana. He brings more than 30 years of software development and entrepreneurial expertise to the team.
Josh Kassabian is co-founder and brings extensive experience in blockchain, UI/UX, and marketing expertise to the team.
Steven Bret Tomlinson
Joshua Kassabian
By Stellar Razor and Blazor Suite
Stellar DotNet Identity Tools
By Stellar Razor and Blazor Suite
Stellar Razor and Blazor Suite