It has been very disappointing for me to see people not supporting development of best-in-class tooling. And not appreciate development tooling in general.

Development tools were almost always a groundwork for projects being built on Polkadot.

Just to remind you, there have been multiple instances of tooling being developed first and then products being built on it. Here is a list of toolings that come to my mind:

1) Acala Chopsticks:

Frankly, I would not want to develop a solution for forking blockchains on my own but thanks to the developers who worked on chopsticks and made them open-sourced, we are not only able to test XCM and functions on existing blockchains, but we can also for example simulate transactions and analyze their outcome. The creative use-cases for Chopsticks are just coming and it was developed just to help developers test XCM messages. It had far larger impact than envisioned.

2) Paraspell:

I was just checking the Turtle app which also would not exist if Dušan and his team would not have developed Paraspell and other-spell tools :D. Also, initially developed without any use-case. But it was pulled of so elegantly that developers are now using it - because why would not they if it saves them hundreds of hours :)

3) Indexers (Subsquid):

I remember working back in the day at Calamar explorer which was powered by Subsquid indexers. If I am not mistaken, it was also not being used for pretty much anything long after completion. Look at it now, people are using it willingly because it is useful to them. And probably nobody sane wants to design their own indexers from scratch.

4) Apillon:

Frankly, I do not have much experience with apillon. From what I have heard, they have attracted thousands of developers to try building something related to Polkadot. I am 100% sure that without Apillon and their tools, they would have probably gave up right away and they would not even have considered trying building something on Polkadot. Once again, the impact has been quite big in my opinion!

5) Substrate framework:

Substrate was originally developed for Polkadot with the vision of parachains, but parachains came second. Without Substrate, it would not exist.

The point I want to make is that all of the things made in Polkadot ecosystem have been made thanks to incredible developer tools.

I understand that it seems that we already have all of the tooling needed, but that is only a misconceptions in my opinion. If we want to make even better apps and games than what we have now, we still need to improve it!

The list could maybe be even longer... These are just projects that I know of from the top of my head.

I have made my decision. I want to develop apps with the best tooling available and with the best people around me. I do not care about anything else more.

Dear Proposer

Thank you for submitting the proposal

Trustless Core has voted NAY.

Team experience: The team behind the project has a strong track record and deep ties in the Polkadot community.

Budget: The budget requested is significant and could raise doubts as to its cost-effectiveness.

Transparency: The proposal looks transparent and auditable, however, there are potential risks and limitations.

Alignment with ecosystem objectives: The project looks very aligned with the ecosystem objectives. However, the reasons for this proposal not being submitted to DOT Play remain unclear, despite the internal voting process emphasizing and recognizing the value of such a pallet. The majority of the group ultimately voted against it. In addition to that, although the creation and implementation of a game pallet is beneficial to have a faster execution time within the game, it is considered that the implementation to be developed covers a need that can be solved with the current ecosystem developments.

Best regards,

Trustless Core Team.

The main idea of the Games bounty which was later overridden by the Dot Play bounty was to have an all encompassing framework for Polkadot to work with and within the gaming industry and to develop titles, tools, etc. with it. Fragmenting the gaming effort into small pieces without much certainty of what happens next is possibly the main reason why these gaming referenda have been declined for the time being. In short, there is not much certainty of a continuation or a path moving forward. We would like to see a better and more structured way for all gaming efforts within Polkadot to move forward in order for us to vote positively on all these Gaming development referenda.

Many thanks for your proposal, Rosta!

We have carefully reviewed your application and are pleased to share our assessment below, prepared using our standardized evaluation methodology.

Summary of our analysis

■ Impact on the Ecosystem

The SAGE proposal enhances Polkadot’s long-term development by simplifying game development for junior developers, potentially increasing adoption and network activity through diversified gaming projects. Its open-source tools address the structural weakness of complex blockchain integration, fostering inclusivity, though measurable impact is limited by undefined KPIs. It promotes user retention and indirect parachain development but relies on Polkadot’s inherent interoperability.

■ Governance Compatibility

The SAGE proposal aligns fully with the MediumSpender origin, requesting 80,000 USDT (18,957 DOT), well within the 100,000 DOT limit, and supports treasury goals. A prior rejected proposal (#1509) indicates responsiveness to feedback, though limited comparables slightly obscure historical context. It meaningfully engages the governance system with a low funding request, minimizing burden.

■ Cost-Benefit Ratio

The 80,000 USDT request is proportionate to potential ecosystem growth, supported by the team’s expertise, but lacks quantified benefits and long-term cost clarity. The budget is reasonable compared to similar proposals, though missing cost breakdowns and unconsidered cheaper alternatives reduce efficiency. The Treasury gains valuable tools for game development, driving network activity, yet unquantified returns limit value clarity.

■ Transparency and Traceability

SAGE clearly outlines fund usage (60,000 USDT for core framework, 20,000 USDT for demo games) with four detailed milestones, but lacks specific quantitative KPIs. Comprehensive budgets, timelines, and work packages are specified, supported by GitHub links, while documentation via repositories and community channels is robust, though a formal reporting schedule is absent.

■ Record and Credibility

Ajuna Network and Rostislav Litovkin have delivered verifiable contributions like Substrate.Net.API and Hexalem, though claims of Xcavate usage lack confirmation. Successful projects and hackathon wins, backed by public GitHub repositories, support credibility, but risks from missing audits and key person reliance temper delivery confidence.

Conclusion

🔹🔷🔹 vonFlandern 🔹🔷🔹 has therefore voted with: ** AYE **

Our methodology aims to analyze and evaluate OpenGov proposals objectively, effectively, and transparently, establishing clear decision-making foundations for our votes while making our process visible to the community.

I am happy to see that community members are standing up for a good product. I don't understand why this was nayed before. The proposal fulfills all the good practices that were defined once:

• Retroactive
• Clear Milestones for future work
• Solid ecosystem history
• Something that is supposed to be useful for builders

What do we want more?

@CedricAtAjuna 

its makes sence. Please, put a lot effort in documentation.. this element is key to help with adoption and improvement for new softwares.

In this case my vote is AYE and i hope you can execute without problems. From developer to developer, good vibes in your deployments =)

OG Tracker Rating 3/3

Clear display of deliverables✅

• Milestone 1 – Reference Implementation & Developer Playground
• Milestone 2 – Rust Implementation & Game Framework Development
• Milestone 3 – UI, JavaScript SDK, Unity Integration
• Milestone 4 – Playground Games

Clear display of a valid direct point of contact✅

• Email: cedric@ajuna.io
• Tg: https://t.me/darkfriend77

Clear display of proposal’s duration ✅

• The duration of this proposal is 7 months.

OGT Rating aims to help voters make better informed decisions and direct proposers towards certain common-good practices. We are providing feedback based on 3 simple yet crucial criteria which we believe should be included in every OpenGov referenda.

Ajuna has consistently contributed to the Substrate-based ecosystem and if one of the very few which remain loyal and faithful to our eco. A big AYE for me and a big hope that this SAGE will come to life.

@TheMvp07

Here’s an overview of the pending deliverables per milestone and the responsible team members:

M1 Pending, Who: Cedric (engine, docs), Niklas (UI)

• Improve test coverage of the C# engine transition logic
• Polish CLI functionality in the playground
• Finalize documentation and tutorials

M2 Pending, Who: Christian (Rust core), Didac (API integration)

• Test & review completion of pallet-sage integration
• Test & review storage schema
• Finalize test suite
• Improve documentation

M3 Pending, Who: Cedric (Unity, SDK), Niklas (JS tools)

• JS SDK review and finalize PAPI integration & tests
• Advanced CLI features
• C#/Unity SDK backend integration
• Improve documentation

M4 Pending, Who**:** Cedric (Unity game), Niklas (terminal game, wrappers)

• Finalize gameplay, add features, publish Full House Fury
• Create additional app logic and finalize Casino Jam terminal UI
• Game Dev focused Documentation / On Boarding
• Hackathon documentation (how to create challenges)

GitHub Profiles:

• Cedric: darkfriend77
• Christian: clangenb
• Didac: DidacSF
• Niklas: niklasp

Hello,

In the previous proposal, you mention that all stages are already advanced. Could you please mention which deliverables are pending and who is responsible for those tasks on the team?

@Xcavateofficial great to hear the work Ajuna does benefits the broader eco!

I would like to support this proposal as our project mobile app development using .net has been hugely supported by this team.

As I already recused here because of my connection to Ajuna, I would like to add my opinion. First of all, the whole DotPlay Discussion is a pain in the Ass! We all speak about decentralization, but one of the most mentioned reasons people Vote for Nay is why Ajuna doesn't go with DotPlay, a centralized entity for Web3 Gaming, which is more a Web2 institution than Web3 ... not gonna say anything more about this!

Another thing many mentioned is the Unity SDK, which "failed". It did not fail. The SDK is actively used in some projects, and you can even use it for Unreal, just not in the Unity Asset Store for obvious reasons.

The SDK is the fully-fledged Interface between Gaming and any Substrate chain. Ajuna developed it to open it to every possible project on Polkadot/Kusama.

My Personal Opinion as a Beginner Game Developer and Technical Person: As already said, the SDK did not fail but did not address the right audience. With the SDK, you can develop ANY Web3 Game on Polkadot, but you need a lot of knowledge in game development and blockchain and all the traps that come with it. Finding skilled Gamedevelopers alone is a huge challenge, so if you combine it with Blockchain Skills, it's impossible.

Indie game developers are often purely on the creative side (design, storytelling, art) or on the visual scripting side (graphic coding with drag & drop), and very few are on the coding side and those who Code are often below-average coders.

The Blockchain part requires a lot of understanding of the Code! There is no drag-and-drop or Creative stuff in general if you speak of Blockchains.

We missed 99% of the Indie game developers with the Unity SDK.

SAGE aims for those 99% now! Making it as easy as possible for all Indie Game Developers to use.

Remember the times of Polkadot, when we only had polkadot.js ? It needed several iterations to come to where Polkadot is now.

In this new environment, we need to learn and improve. No one hit a home run the first time!

The Unity SDK was only the first step for Ajuna, but SAGE could be close to a Homerun.